NCP-MCI v7.5 Premium File
- 83 Questions & Answers
- Last Update: Nov 16, 2026
An infrastructure owner seeks a repeatable preventive control: A compliance reviewer notices that a newly cloned workload bypassed the intended category-based segmentation policy after its metadata changed. Which continuing control would most directly reduce recurrence of this problem?
Require category assignment validation and post-clone exposure review for protected workloads. It directly addresses how this condition recurs. Operational acceptance evidence should include: The workload shows the intended effective security policy and the unexpected connection is blocked or explicitly approved.
Alert on both logical quota and actual usable capacity, including projected expansion demand. This safeguard is aimed at storage container quota and reservation semantics, whereas recurring security central workload exposure review failures need: Require category assignment validation and post-clone exposure review for protected workloads.
Define bandwidth budgets and phased migration waves before multi-site consolidation. This safeguard is aimed at migration performance and bandwidth limits, whereas recurring security central workload exposure review failures need: Require category assignment validation and post-clone exposure review for protected workloads.
Maintain application-aware storage placement criteria and post-migration performance validation. This safeguard is aimed at ahv vdisk performance tier migration, whereas recurring security central workload exposure review failures need: Require category assignment validation and post-clone exposure review for protected workloads.
A Nutanix administrator must choose an operational response: A financial-services Prism Central instance uses scheduled point-in-time backups only, but the recovery architect now requires protection against short intervals of administrative changes between those backups. Which action most directly addresses the stated Nutanix infrastructure issue?
Evaluate Prism Central Backup and Restore continuous-backup eligibility, supported destination and version requirements, then configure the supported continuous protection option for the required recovery objective. The causal mechanism is: Continuous Prism Central backup captures management-state changes more frequently than occasional point-in-time protection when the required architecture and backup destination support it. Confirmation should include: A controlled restore validation recovers recently changed policies and configuration state at a recovery point within the agreed management-plane data-loss window.
Apply the approved unplanned failover and fencing procedure to establish a single authoritative active copy before directing production writes to the recovery site. This addresses unplanned failover and split-brain control, not the cause described in the continuous prism central backup coverage scenario. First examine: Compare recorded backup recovery points and retention with recent Prism Central changes and verify whether the chosen deployment supports continuous protection.
Adjust the supported asynchronous replication schedule and retention to meet the business RPO after checking link throughput and destination capacity. This addresses asynchronous replication schedule and rpo, not the cause described in the continuous prism central backup coverage scenario. First examine: Compare recorded backup recovery points and retention with recent Prism Central changes and verify whether the chosen deployment supports continuous protection.
Complete the supported cross-cluster live migration prerequisite checks, including target compatibility, networks, storage and policy constraints, before requesting the move. This addresses cross-cluster live migration dependencies, not the cause described in the continuous prism central backup coverage scenario. First examine: Compare recorded backup recovery points and retention with recent Prism Central changes and verify whether the chosen deployment supports continuous protection.
An operations engineer needs evidence of a completed fix: A financial-services Prism Central instance uses scheduled point-in-time backups only, but the recovery architect now requires protection against short intervals of administrative changes between those backups. Which observation would most directly verify that this specific issue is resolved?
A controlled restore validation recovers recently changed policies and configuration state at a recovery point within the agreed management-plane data-loss window. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. Continuous Prism Central backup captures management-state changes more frequently than occasional point-in-time protection when the required architecture and backup destination support it.
The destination contains regularly completed recoverable points whose measured age remains within the approved RPO, including after a network interruption. This is evidence for asynchronous replication schedule and rpo. The required evidence is: A controlled restore validation recovers recently changed policies and configuration state at a recovery point within the agreed management-plane data-loss window.
The DR copy can boot and be validated in an isolated test segment without clients seeing two active copies of the same production service. This is evidence for planned failover rehearsal isolation. The required evidence is: A controlled restore validation recovers recently changed policies and configuration state at a recovery point within the agreed management-plane data-loss window.
The recovered guest is attached to the mapped destination network and passes routed gateway, DNS and application endpoint checks. This is evidence for prism element failover network mapping. The required evidence is: A controlled restore validation recovers recently changed policies and configuration state at a recovery point within the agreed management-plane data-loss window.
A multicloud infrastructure team is explaining a recurring issue: A financial-services Prism Central instance uses scheduled point-in-time backups only, but the recovery architect now requires protection against short intervals of administrative changes between those backups. Which technical principle best explains this behavior?
Continuous Prism Central backup captures management-state changes more frequently than occasional point-in-time protection when the required architecture and backup destination support it. This is the explanation consistent with the stated symptoms. The focused resolution is: Evaluate Prism Central Backup and Restore continuous-backup eligibility, supported destination and version requirements, then configure the supported continuous protection option for the required recovery objective.
Prism Central policies can select protected resources by category, so inconsistent metadata changes actual data-protection coverage. This explains category-based vm protection coverage rather than the observed continuous prism central backup coverage symptoms. Here the dependency is: Continuous Prism Central backup captures management-state changes more frequently than occasional point-in-time protection when the required architecture and backup destination support it.
Running a recovery copy in the same production network while the original remains active can create identity conflicts and inconsistent writes. This explains planned failover rehearsal isolation rather than the observed continuous prism central backup coverage symptoms. Here the dependency is: Continuous Prism Central backup captures management-state changes more frequently than occasional point-in-time protection when the required architecture and backup destination support it.
The offsite recovery-point age is constrained by completed replication intervals and transfer completion, not merely snapshot creation on the source. This explains asynchronous replication schedule and rpo rather than the observed continuous prism central backup coverage symptoms. Here the dependency is: Continuous Prism Central backup captures management-state changes more frequently than occasional point-in-time protection when the required architecture and backup destination support it.
A change-risk reviewer evaluates this Nutanix condition: After a regional Prism Central outage, an operator finds that the available point-in-time copy predates several critical policy changes made during the workday. What is the most direct avoidable risk if the issue remains unresolved?
Recent Prism Central configuration and category-policy changes may be lost after an outage even though older point-in-time copies remain available. This is the immediate exposure in the named scenario. Continuous Prism Central backup captures management-state changes more frequently than occasional point-in-time protection when the required architecture and backup destination support it. A targeted mitigation is: Evaluate Prism Central Backup and Restore continuous-backup eligibility, supported destination and version requirements, then configure the supported continuous protection option for the required recovery objective.
The apparent low-RPO policy may produce delayed or failed offsite recovery points under unsupported settings or oversubscribed connectivity. That exposure applies to near-sync protection compatibility; the direct risk here is: Recent Prism Central configuration and category-policy changes may be lost after an outage even though older point-in-time copies remain available.
The failover may produce healthy guest power states while the service remains unreachable to its clients. That exposure applies to prism element failover network mapping; the direct risk here is: Recent Prism Central configuration and category-policy changes may be lost after an outage even though older point-in-time copies remain available.
A business-critical VM may have no usable recovery point despite a policy showing healthy protection for other tagged workloads. That exposure applies to category-based vm protection coverage; the direct risk here is: Recent Prism Central configuration and category-policy changes may be lost after an outage even though older point-in-time copies remain available.
A support engineer must isolate the first implicated dependency: After a regional Prism Central outage, an operator finds that the available point-in-time copy predates several critical policy changes made during the workday. Which focused check would best test the suspected cause before a broader change?
Compare recorded backup recovery points and retention with recent Prism Central changes and verify whether the chosen deployment supports continuous protection. It tests the specific suspected dependency before wider changes. If confirmed, the relevant action is: Evaluate Prism Central Backup and Restore continuous-backup eligibility, supported destination and version requirements, then configure the supported continuous protection option for the required recovery objective.
Inspect remote-site connection state, replication errors, firewall path and most recent target recovery point. This check investigates prism element remote-site trust and connectivity. For the current symptoms, inspect: Compare recorded backup recovery points and retention with recent Prism Central changes and verify whether the chosen deployment supports continuous protection.
Compare measured intersite RTT, bandwidth stability and design topology to the current product-version synchronous and Metro requirements. This check investigates synchronous protection latency design. For the current symptoms, inspect: Compare recorded backup recovery points and retention with recent Prism Central changes and verify whether the chosen deployment supports continuous protection.
Inventory the container platform, persistent-volume dependencies and backup/protection integration currently configured, then map each to a supported recovery method. This check investigates container workload recovery coverage. For the current symptoms, inspect: Compare recorded backup recovery points and retention with recent Prism Central changes and verify whether the chosen deployment supports continuous protection.
An infrastructure owner seeks a repeatable preventive control: After a regional Prism Central outage, an operator finds that the available point-in-time copy predates several critical policy changes made during the workday. Which continuing control would most directly reduce recurrence of this problem?
Monitor backup freshness and periodic management-state restoration evidence rather than relying solely on a successful scheduling message. It directly addresses how this condition recurs. Operational acceptance evidence should include: A controlled restore validation recovers recently changed policies and configuration state at a recovery point within the agreed management-plane data-loss window.
Enforce controlled category assignment in VM provisioning and alert when production assets have no matching recovery policy. This safeguard is aimed at category-based vm protection coverage, whereas recurring continuous prism central backup coverage failures need: Monitor backup freshness and periodic management-state restoration evidence rather than relying solely on a successful scheduling message.
Require protection-domain membership review whenever application topology or VM ownership changes. This safeguard is aimed at prism element protection domain membership, whereas recurring continuous prism central backup coverage failures need: Monitor backup freshness and periodic management-state restoration evidence rather than relying solely on a successful scheduling message.
Revalidate NearSync prerequisites and RPO telemetry whenever workloads, software versions or WAN characteristics change. This safeguard is aimed at near-sync protection compatibility, whereas recurring continuous prism central backup coverage failures need: Monitor backup freshness and periodic management-state restoration evidence rather than relying solely on a successful scheduling message.
A Nutanix administrator must choose an operational response: An infrastructure team retained only the newest Prism Central recovery point and discovers an unnoticed configuration defect was already present in that backup. Which action most directly addresses the stated Nutanix infrastructure issue?
Configure supported point-in-time Prism Central backups to a validated location with a retention schedule that preserves multiple recoverable historical points. The causal mechanism is: Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup. Confirmation should include: A restoration drill can select an older unaffected recovery point and restore the expected inventory and policy metadata without selecting the corrupt newest copy.
Correct the Prism Central recovery plan's network mapping, dependent VM ordering and application readiness checks according to the approved service runbook. This addresses recovery-plan boot sequencing and network mapping, not the cause described in the point-in-time backup retention scenario. First examine: Inspect available Prism Central recovery points, their creation times and retention expiration before deleting or overwriting a known-good historical copy.
Apply the approved unplanned failover and fencing procedure to establish a single authoritative active copy before directing production writes to the recovery site. This addresses unplanned failover and split-brain control, not the cause described in the point-in-time backup retention scenario. First examine: Inspect available Prism Central recovery points, their creation times and retention expiration before deleting or overwriting a known-good historical copy.
Correct and verify the VM category assignment and Prism Central protection-policy membership so the intended workload joins the managed protection scope. This addresses category-based vm protection coverage, not the cause described in the point-in-time backup retention scenario. First examine: Inspect available Prism Central recovery points, their creation times and retention expiration before deleting or overwriting a known-good historical copy.
An operations engineer needs evidence of a completed fix: An infrastructure team retained only the newest Prism Central recovery point and discovers an unnoticed configuration defect was already present in that backup. Which observation would most directly verify that this specific issue is resolved?
A restoration drill can select an older unaffected recovery point and restore the expected inventory and policy metadata without selecting the corrupt newest copy. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup.
Prism Central reports that the affected VM is covered by the intended protection policy and a valid recovery point is available at the planned site. This is evidence for category-based vm protection coverage. The required evidence is: A restoration drill can select an older unaffected recovery point and restore the expected inventory and policy metadata without selecting the corrupt newest copy.
Operators have evidence that only the recovered workload accepts new writes and can safely reverse or reconcile replication once the original site returns. This is evidence for unplanned failover and split-brain control. The required evidence is: A restoration drill can select an older unaffected recovery point and restore the expected inventory and policy metadata without selecting the corrupt newest copy.
A controlled failover test demonstrates the supported synchronous protection state and application consistency without breaching the agreed latency objectives. This is evidence for synchronous protection latency design. The required evidence is: A restoration drill can select an older unaffected recovery point and restore the expected inventory and policy metadata without selecting the corrupt newest copy.
A multicloud infrastructure team is explaining a recurring issue: An infrastructure team retained only the newest Prism Central recovery point and discovers an unnoticed configuration defect was already present in that backup. Which technical principle best explains this behavior?
Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup. This is the explanation consistent with the stated symptoms. The focused resolution is: Configure supported point-in-time Prism Central backups to a validated location with a retention schedule that preserves multiple recoverable historical points.
Cross-cluster live migration requires compatible source and target resources and an explicitly validated supported path. This explains cross-cluster live migration dependencies rather than the observed point-in-time backup retention symptoms. Here the dependency is: Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup.
Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points. This explains prism element protection domain membership rather than the observed point-in-time backup retention symptoms. Here the dependency is: Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup.
Container data recovery requires protection of persistent storage and application control-plane context, which may differ from VM snapshot coverage. This explains container workload recovery coverage rather than the observed point-in-time backup retention symptoms. Here the dependency is: Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup.
A change-risk reviewer evaluates this Nutanix condition: An insurer proposes a single daily Prism Central snapshot even though audit investigations sometimes require restoring the management state from an earlier approved change window. What is the most direct avoidable risk if the issue remains unresolved?
An older clean Prism Central state may no longer exist, preventing controlled recovery from a latent management-plane configuration error. This is the immediate exposure in the named scenario. Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup. A targeted mitigation is: Configure supported point-in-time Prism Central backups to a validated location with a retention schedule that preserves multiple recoverable historical points.
High or unstable intersite latency can create unacceptable application delay or loss of protection guarantees during network faults. That exposure applies to synchronous protection latency design; the direct risk here is: An older clean Prism Central state may no longer exist, preventing controlled recovery from a latent management-plane configuration error.
Intersite network partitions may lead to unsafe or prolonged service decisions without tested arbitration and site ownership rules. That exposure applies to metro witness and esxi failure domains; the direct risk here is: An older clean Prism Central state may no longer exist, preventing controlled recovery from a latent management-plane configuration error.
The failover may produce healthy guest power states while the service remains unreachable to its clients. That exposure applies to prism element failover network mapping; the direct risk here is: An older clean Prism Central state may no longer exist, preventing controlled recovery from a latent management-plane configuration error.
Please check your mailbox for a message from support@examlabs.com and follow the directions.