NCP-MCI v7.5 Premium File
- 83 Questions & Answers
- Last Update: Nov 16, 2026
An operations engineer needs evidence of a completed fix: A team protects Nutanix-hosted VMs but assumes the same VM policy automatically captures persistent Kubernetes application data and orchestration definitions. Which observation would most directly verify that this specific issue is resolved?
A controlled recovery test restores the application definitions, durable data and connectivity in the supported destination environment. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. Container data recovery requires protection of persistent storage and application control-plane context, which may differ from VM snapshot coverage.
A restoration drill can select an older unaffected recovery point and restore the expected inventory and policy metadata without selecting the corrupt newest copy. This is evidence for point-in-time backup retention. The required evidence is: A controlled recovery test restores the application definitions, durable data and connectivity in the supported destination environment.
An isolated-link DR test shows the approved arbitration result and a single writable active site, with expected storage and VM service continuity. This is evidence for metro witness and esxi failure domains. The required evidence is: A controlled recovery test restores the application definitions, durable data and connectivity in the supported destination environment.
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 controlled recovery test restores the application definitions, durable data and connectivity in the supported destination environment.
A multicloud infrastructure team is explaining a recurring issue: A team protects Nutanix-hosted VMs but assumes the same VM policy automatically captures persistent Kubernetes application data and orchestration definitions. Which technical principle best explains this behavior?
Container data recovery requires protection of persistent storage and application control-plane context, which may differ from VM snapshot coverage. This is the explanation consistent with the stated symptoms. The focused resolution is: Identify and configure the supported container application and persistent-data protection path for the platform and workload, separate from ordinary VM-only recovery policies.
An unreachable source is not necessarily powered off; uncoordinated recovery promotion can create split-brain application writes. This explains unplanned failover and split-brain control rather than the observed container workload recovery coverage symptoms. Here the dependency is: Container data recovery requires protection of persistent storage and application control-plane context, which may differ from VM snapshot coverage.
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 explains continuous prism central backup coverage rather than the observed container workload recovery coverage symptoms. Here the dependency is: Container data recovery requires protection of persistent storage and application control-plane context, which may differ from VM snapshot coverage.
A management-plane relocation is a coordinated instance-state migration with dependency and endpoint checks, not an unvalidated VM disk copy. This explains prism central instance migration preparation rather than the observed container workload recovery coverage symptoms. Here the dependency is: Container data recovery requires protection of persistent storage and application control-plane context, which may differ from VM snapshot coverage.
A change-risk reviewer evaluates this Nutanix condition: A service combines container workloads and externally managed persistent volumes, yet the proposed DR test checks only AHV virtual-machine snapshots. What is the most direct avoidable risk if the issue remains unresolved?
The team can recover infrastructure hosts but lose container application state or the durable data needed to restart the service. This is the immediate exposure in the named scenario. Container data recovery requires protection of persistent storage and application control-plane context, which may differ from VM snapshot coverage. A targeted mitigation is: Identify and configure the supported container application and persistent-data protection path for the platform and workload, separate from ordinary VM-only recovery policies.
The operator may believe that a local snapshot is equivalent to a recoverable offsite copy when WAN replication is actually blocked. That exposure applies to prism element remote-site trust and connectivity; the direct risk here is: The team can recover infrastructure hosts but lose container application state or the durable data needed to restart the service.
An unsupported restore attempt may fail or leave management services and integrations inconsistent during the recovery window. That exposure applies to prism central restoration version prerequisites; the direct risk here is: The team can recover infrastructure hosts but lose container application state or the durable data needed to restart the service.
An older clean Prism Central state may no longer exist, preventing controlled recovery from a latent management-plane configuration error. That exposure applies to point-in-time backup retention; the direct risk here is: The team can recover infrastructure hosts but lose container application state or the durable data needed to restart the service.
A support engineer must isolate the first implicated dependency: A service combines container workloads and externally managed persistent volumes, yet the proposed DR test checks only AHV virtual-machine snapshots. Which focused check would best test the suspected cause before a broader change?
Inventory the container platform, persistent-volume dependencies and backup/protection integration currently configured, then map each to a supported recovery method. It tests the specific suspected dependency before wider changes. If confirmed, the relevant action is: Identify and configure the supported container application and persistent-data protection path for the platform and workload, separate from ordinary VM-only recovery policies.
Compare the application dependency inventory against the protection-domain membership and its most recent replication point. This check investigates prism element protection domain membership. For the current symptoms, inspect: Inventory the container platform, persistent-volume dependencies and backup/protection integration currently configured, then map each to a supported recovery method.
Compare current Prism Element observations with Prism Central connection status, timestamps and authentication errors for the missing cluster. This check investigates post-restore cluster registration validation. For the current symptoms, inspect: Inventory the container platform, persistent-volume dependencies and backup/protection integration currently configured, then map each to a supported recovery method.
Investigate source isolation and last known write authority, and confirm the approved fencing path before promoting the destination copy. This check investigates unplanned failover and split-brain control. For the current symptoms, inspect: Inventory the container platform, persistent-volume dependencies and backup/protection integration currently configured, then map each to a supported recovery method.
An infrastructure owner seeks a repeatable preventive control: A service combines container workloads and externally managed persistent volumes, yet the proposed DR test checks only AHV virtual-machine snapshots. Which continuing control would most directly reduce recurrence of this problem?
Maintain a documented restore test for both Kubernetes application manifests and persistent data rather than treating VM snapshots as complete container DR. It directly addresses how this condition recurs. Operational acceptance evidence should include: A controlled recovery test restores the application definitions, durable data and connectivity in the supported destination environment.
Test planned partition scenarios and monitor witness connectivity as a separate dependency of Metro recovery readiness. This safeguard is aimed at metro witness and esxi failure domains, whereas recurring container workload recovery coverage failures need: Maintain a documented restore test for both Kubernetes application manifests and persistent data rather than treating VM snapshots as complete container DR.
Maintain a tested, version-matched recovery procedure and archive compatible installation media alongside encrypted backup metadata. This safeguard is aimed at prism central restoration version prerequisites, whereas recurring container workload recovery coverage failures need: Maintain a documented restore test for both Kubernetes application manifests and persistent data rather than treating VM snapshots as complete container DR.
Include network-map validation and client connectivity probes in every Prism Element DR acceptance exercise. This safeguard is aimed at prism element failover network mapping, whereas recurring container workload recovery coverage failures need: Maintain a documented restore test for both Kubernetes application manifests and persistent data rather than treating VM snapshots as complete container DR.
A Nutanix administrator must choose an operational response: A Prism Element protection domain includes only the database VM, while the application depends on another VM outside its consistency group. Which action most directly addresses the stated Nutanix infrastructure issue?
Update the Prism Element protection domain and appropriate consistency-group scope to include every required VM, with an approved replication schedule. The causal mechanism is: Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points. Confirmation should include: The protected entity list contains all required components and an offsite recovery rehearsal restores a consistent set of VMs.
Restore the approved Prism Central backup target's reachability and authentication, then rerun the supported backup workflow and verify a new recovery point. This addresses prism central backup destination access, not the cause described in the prism element protection domain membership scenario. First examine: Compare the application dependency inventory against the protection-domain membership and its most recent replication point.
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 prism element protection domain membership scenario. First examine: Compare the application dependency inventory against the protection-domain membership and its most recent replication point.
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 prism element protection domain membership scenario. First examine: Compare the application dependency inventory against the protection-domain membership and its most recent replication point.
An operations engineer needs evidence of a completed fix: A Prism Element protection domain includes only the database VM, while the application depends on another VM outside its consistency group. Which observation would most directly verify that this specific issue is resolved?
The protected entity list contains all required components and an offsite recovery rehearsal restores a consistent set of VMs. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points.
During an isolated DR drill the database and dependent tiers start in order, obtain valid recovery-site addresses and pass end-to-end application health tests. This is evidence for recovery-plan boot sequencing and network mapping. The required evidence is: The protected entity list contains all required components and an offsite recovery rehearsal restores a consistent set of VMs.
A new backup reports successful completion at the intended destination, and the destination inventory shows a newly readable management-plane recovery point. This is evidence for prism central backup destination access. The required evidence is: The protected entity list contains all required components and an offsite recovery rehearsal restores a consistent set of VMs.
Destination recovery-point frequency and completion evidence demonstrate the defined low-RPO target under normal and peak network load. This is evidence for near-sync protection compatibility. The required evidence is: The protected entity list contains all required components and an offsite recovery rehearsal restores a consistent set of VMs.
A multicloud infrastructure team is explaining a recurring issue: A Prism Element protection domain includes only the database VM, while the application depends on another VM outside its consistency group. Which technical principle best explains this behavior?
Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points. This is the explanation consistent with the stated symptoms. The focused resolution is: Update the Prism Element protection domain and appropriate consistency-group scope to include every required VM, with an approved replication schedule.
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 prism element protection domain membership symptoms. Here the dependency is: Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points.
Multiple retained point-in-time management-plane backups provide recovery selection when a configuration defect existed before the latest backup. This explains point-in-time backup retention rather than the observed prism element protection domain membership symptoms. Here the dependency is: Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points.
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 prism element protection domain membership symptoms. Here the dependency is: Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points.
A change-risk reviewer evaluates this Nutanix condition: An older application was expanded with an additional service VM, but its legacy Prism Element protection domain membership was never revised. What is the most direct avoidable risk if the issue remains unresolved?
The recovered application may contain only part of its dependent service and fail consistency checks after a site incident. This is the immediate exposure in the named scenario. Prism Element protection domains define the protected VM set, while consistency-group choices influence coordinated recovery points. A targeted mitigation is: Update the Prism Element protection domain and appropriate consistency-group scope to include every required VM, with an approved replication schedule.
An older clean Prism Central state may no longer exist, preventing controlled recovery from a latent management-plane configuration error. That exposure applies to point-in-time backup retention; the direct risk here is: The recovered application may contain only part of its dependent service and fail consistency checks after a site incident.
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: The recovered application may contain only part of its dependent service and fail consistency checks after a site incident.
The move can fail mid-operation or leave a running VM with unusable destination network connectivity and no acceptable rollback. That exposure applies to cross-cluster live migration dependencies; the direct risk here is: The recovered application may contain only part of its dependent service and fail consistency checks after a site incident.
A support engineer must isolate the first implicated dependency: An older application was expanded with an additional service VM, but its legacy Prism Element protection domain membership was never revised. Which focused check would best test the suspected cause before a broader change?
Compare the application dependency inventory against the protection-domain membership and its most recent replication point. It tests the specific suspected dependency before wider changes. If confirmed, the relevant action is: Update the Prism Element protection domain and appropriate consistency-group scope to include every required VM, with an approved replication schedule.
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 the application dependency inventory against the protection-domain membership and its most recent replication point.
Trace Prism Central backup-job error details, target DNS and routing, permitted ports, authorization and backup destination availability. This check investigates prism central backup destination access. For the current symptoms, inspect: Compare the application dependency inventory against the protection-domain membership and its most recent replication point.
Review Nutanix cross-cluster live migration eligibility messages, target capacity and destination virtual-network mappings. This check investigates cross-cluster live migration dependencies. For the current symptoms, inspect: Compare the application dependency inventory against the protection-domain membership and its most recent replication point.
An infrastructure owner seeks a repeatable preventive control: An older application was expanded with an additional service VM, but its legacy Prism Element protection domain membership was never revised. Which continuing control would most directly reduce recurrence of this problem?
Require protection-domain membership review whenever application topology or VM ownership changes. It directly addresses how this condition recurs. Operational acceptance evidence should include: The protected entity list contains all required components and an offsite recovery rehearsal restores a consistent set of VMs.
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 prism element protection domain membership failures need: Require protection-domain membership review whenever application topology or VM ownership changes.
Schedule periodic isolated Prism Central recoverability tests and retain measured RTO and configuration-validation evidence. This safeguard is aimed at prism central restoration recovery exercise, whereas recurring prism element protection domain membership failures need: Require protection-domain membership review whenever application topology or VM ownership changes.
Maintain monitored intersite latency budgets and periodic controlled Metro failover validation after network changes. This safeguard is aimed at synchronous protection latency design, whereas recurring prism element protection domain membership failures need: Require protection-domain membership review whenever application topology or VM ownership changes.
Please check your mailbox for a message from support@examlabs.com and follow the directions.