NCP-MCI v7.5 Premium File
- 83 Questions & Answers
- Last Update: Nov 16, 2026
An infrastructure owner seeks a repeatable preventive control: A secure site disables broad SSH access but discovers that its break-glass maintenance workflow has not been tested. Which continuing control would most directly reduce recurrence of this problem?
Test and audit a least-privilege break-glass process whenever management access is tightened. It directly addresses how this condition recurs. Operational acceptance evidence should include: Unauthorized SSH access is blocked while designated emergency operators can still perform their documented recovery actions.
Include CVM sizing approval and growth-triggered resource reviews in the cluster deployment standard. This safeguard is aimed at cvm capacity sizing for new services, whereas recurring cluster lockdown and emergency access failures need: Test and audit a least-privilege break-glass process whenever management access is tightened.
Review Prism Central sizing at each onboarding wave and treat resource limits as a planned capacity dependency. This safeguard is aimed at prism central sizing for multi-cluster scale, whereas recurring cluster lockdown and emergency access failures need: Test and audit a least-privilege break-glass process whenever management access is tightened.
Document the DHCP/IPAM owner and reserve consistent address pools for each Nutanix guest network. This safeguard is aimed at ahv subnet dhcp behavior, whereas recurring cluster lockdown and emergency access failures need: Test and audit a least-privilege break-glass process whenever management access is tightened.
A Nutanix administrator must choose an operational response: A new corporate CA-signed certificate is installed on Prism Central, but browsers still flag an incomplete trust chain. Which action most directly addresses the stated Nutanix infrastructure issue?
Install a valid certificate and complete supported trust chain whose names match the Prism Central endpoint used by administrators. The causal mechanism is: TLS endpoint validation requires trusted issuer certificates and matching DNS names, independent of whether TCP connectivity succeeds. Confirmation should include: Management clients validate the full certificate chain and the Prism Central DNS name without bypassing TLS warnings.
Select compression or deduplication settings based on data characteristics, supported storage-container behavior and measured savings. This addresses compression versus deduplication workload fit, not the cause described in the prism central tls certificate chain scenario. First examine: Inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname.
Configure narrowly scoped traffic mirroring from the intended VM or virtual network to the reachable approved analysis destination. This addresses traffic mirroring scope for packet capture, not the cause described in the prism central tls certificate chain scenario. First examine: Inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname.
Evaluate documented scale-out and size requirements and select the supported Prism Central expansion or resource adjustment procedure. This addresses prism central scale-out decision, not the cause described in the prism central tls certificate chain scenario. First examine: Inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname.
An operations engineer needs evidence of a completed fix: A new corporate CA-signed certificate is installed on Prism Central, but browsers still flag an incomplete trust chain. Which observation would most directly verify that this specific issue is resolved?
Management clients validate the full certificate chain and the Prism Central DNS name without bypassing TLS warnings. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. TLS endpoint validation requires trusted issuer certificates and matching DNS names, independent of whether TCP connectivity succeeds.
Prism Central inventory, health and policy tasks complete within expected windows without sustained capacity alerts after the supported resize. This is evidence for prism central sizing for multi-cluster scale. The required evidence is: Management clients validate the full certificate chain and the Prism Central DNS name without bypassing TLS warnings.
DNS names resolve as planned, time sources remain synchronized and a test platform alert reaches the authorized recipient. This is evidence for post-imaging essential cluster services. The required evidence is: Management clients validate the full certificate chain and the Prism Central DNS name without bypassing TLS warnings.
Resiliency capacity alerts clear without removing failure headroom and simulated loss planning leaves adequate storage for rebuilding copies. This is evidence for resilient capacity reservation. The required evidence is: Management clients validate the full certificate chain and the Prism Central DNS name without bypassing TLS warnings.
A multicloud infrastructure team is explaining a recurring issue: A new corporate CA-signed certificate is installed on Prism Central, but browsers still flag an incomplete trust chain. Which technical principle best explains this behavior?
TLS endpoint validation requires trusted issuer certificates and matching DNS names, independent of whether TCP connectivity succeeds. This is the explanation consistent with the stated symptoms. The focused resolution is: Install a valid certificate and complete supported trust chain whose names match the Prism Central endpoint used by administrators.
VPC connectivity depends on explicit private address ranges and gateway/routing definitions; identical prefixes can make path selection ambiguous. This explains vpc routing and address planning rather than the observed prism central tls certificate chain symptoms. Here the dependency is: TLS endpoint validation requires trusted issuer certificates and matching DNS names, independent of whether TCP connectivity succeeds.
Management dependencies such as DNS, time and notification transport are separate from the mere ability to start cluster services. This explains post-imaging essential cluster services rather than the observed prism central tls certificate chain symptoms. Here the dependency is: TLS endpoint validation requires trusted issuer certificates and matching DNS names, independent of whether TCP connectivity succeeds.
Prism Central policies match defined entities and conditions; broad predicates can capture unrelated workloads. This explains policy engine scope and category targeting rather than the observed prism central tls certificate chain symptoms. Here the dependency is: TLS endpoint validation requires trusted issuer certificates and matching DNS names, independent of whether TCP connectivity succeeds.
A change-risk reviewer evaluates this Nutanix condition: A certificate renewal changes the Prism Central hostname while the renewed certificate lacks the management DNS name in its SAN extension. What is the most direct avoidable risk if the issue remains unresolved?
Ignoring certificate identity errors can normalize man-in-the-middle exposure in privileged management sessions. This is the immediate exposure in the named scenario. TLS endpoint validation requires trusted issuer certificates and matching DNS names, independent of whether TCP connectivity succeeds. A targeted mitigation is: Install a valid certificate and complete supported trust chain whose names match the Prism Central endpoint used by administrators.
Assuming universal savings can overcommit capacity plans or introduce performance overhead with little practical benefit. That exposure applies to compression versus deduplication workload fit; the direct risk here is: Ignoring certificate identity errors can normalize man-in-the-middle exposure in privileged management sessions.
Assuming a network-dependent deployment path can block the rollout and cause ad hoc, undocumented imaging workarounds. That exposure applies to deployment method selection for isolated sites; the direct risk here is: Ignoring certificate identity errors can normalize man-in-the-middle exposure in privileged management sessions.
Running under the supported management-plane size can delay policy evaluations and produce unreliable visibility of managed workloads. That exposure applies to prism central sizing for multi-cluster scale; the direct risk here is: Ignoring certificate identity errors can normalize man-in-the-middle exposure in privileged management sessions.
A support engineer must isolate the first implicated dependency: A certificate renewal changes the Prism Central hostname while the renewed certificate lacks the management DNS name in its SAN extension. Which focused check would best test the suspected cause before a broader change?
Inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname. It tests the specific suspected dependency before wider changes. If confirmed, the relevant action is: Install a valid certificate and complete supported trust chain whose names match the Prism Central endpoint used by administrators.
Review Prism cluster service configuration and execute DNS, time and test-notification checks from the management network. This check investigates post-imaging essential cluster services. For the current symptoms, inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname.
Inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related. This check investigates prism central role-based management. For the current symptoms, inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname.
Validate source filters, mirror destination path and a known traffic sample before collecting sensitive captures. This check investigates traffic mirroring scope for packet capture. For the current symptoms, inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname.
An infrastructure owner seeks a repeatable preventive control: A certificate renewal changes the Prism Central hostname while the renewed certificate lacks the management DNS name in its SAN extension. Which continuing control would most directly reduce recurrence of this problem?
Track certificate expiry and hostname changes through approved management endpoint certificate lifecycle procedures. It directly addresses how this condition recurs. Operational acceptance evidence should include: Management clients validate the full certificate chain and the Prism Central DNS name without bypassing TLS warnings.
Keep rack inventory and fault-domain metadata accurate and test resilience claims as topology changes. This safeguard is aimed at storage health and fault-domain awareness, whereas recurring prism central tls certificate chain failures need: Track certificate expiry and hostname changes through approved management endpoint certificate lifecycle procedures.
Make management dependency validation a signed handover criterion, not an optional post-installation task. This safeguard is aimed at post-imaging essential cluster services, whereas recurring prism central tls certificate chain failures need: Track certificate expiry and hostname changes through approved management endpoint certificate lifecycle procedures.
Use the supported PC sizing and expansion workflow with a change plan and rollback checks. This safeguard is aimed at prism central scale-out decision, whereas recurring prism central tls certificate chain failures need: Track certificate expiry and hostname changes through approved management endpoint certificate lifecycle procedures.
A Nutanix administrator must choose an operational response: A monitoring integration requests a global administrator password to read inventory when only bounded API access is required. Which action most directly addresses the stated Nutanix infrastructure issue?
Create a dedicated supported Prism Central service account with narrowly scoped API rights and auditable credential rotation. The causal mechanism is: Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials. Confirmation should include: The integration can read only the required resources and its actions remain attributable to a managed service identity.
Reconcile the node inventory, network addresses, imaging target and BMC credentials before using the supported Foundation imaging workflow. This addresses foundation discovery and node imaging, not the cause described in the prism central service account permissions scenario. First examine: Inspect API scopes, assigned roles and identity ownership before replacing the service credentials.
Grant an appropriate Prism Central role and resource/project scope rather than expanding to a global administrator permission set. This addresses prism central role-based management, not the cause described in the prism central service account permissions scenario. First examine: Inspect API scopes, assigned roles and identity ownership before replacing the service credentials.
Inspect actual used, reclaimable and reserved capacity and choose supported cleanup or growth actions before creating more workload storage. This addresses container storage shortage triage, not the cause described in the prism central service account permissions scenario. First examine: Inspect API scopes, assigned roles and identity ownership before replacing the service credentials.
An operations engineer needs evidence of a completed fix: A monitoring integration requests a global administrator password to read inventory when only bounded API access is required. Which observation would most directly verify that this specific issue is resolved?
The integration can read only the required resources and its actions remain attributable to a managed service identity. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials.
The application sees the intended LUN through a supported attachment while cluster metadata and managed vDisks remain intact. This is evidence for external storage integration requirement. The required evidence is: The integration can read only the required resources and its actions remain attributable to a managed service identity.
Each intended node completes imaging with the selected supported AHV image and its CVM and hypervisor management addresses match the approved inventory. This is evidence for foundation discovery and node imaging. The required evidence is: The integration can read only the required resources and its actions remain attributable to a managed service identity.
The engineer performs required authorized operations in the assigned project and cannot edit unrelated projects or global settings. This is evidence for prism central role-based management. The required evidence is: The integration can read only the required resources and its actions remain attributable to a managed service identity.
A multicloud infrastructure team is explaining a recurring issue: A monitoring integration requests a global administrator password to read inventory when only bounded API access is required. Which technical principle best explains this behavior?
Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials. This is the explanation consistent with the stated symptoms. The focused resolution is: Create a dedicated supported Prism Central service account with narrowly scoped API rights and auditable credential rotation.
Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement. This explains prism central features and prerequisites rather than the observed prism central service account permissions symptoms. Here the dependency is: Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials.
Replication factors determine how many protected copies are maintained and have topology prerequisites; RF3 needs more nodes than RF2. This explains rf2 and rf3 resiliency prerequisites rather than the observed prism central service account permissions symptoms. Here the dependency is: Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials.
Management dependencies such as DNS, time and notification transport are separate from the mere ability to start cluster services. This explains post-imaging essential cluster services rather than the observed prism central service account permissions symptoms. Here the dependency is: Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials.
A change-risk reviewer evaluates this Nutanix condition: An automation bot uses a departed employee's personal credentials and fails when that identity is disabled by HR. What is the most direct avoidable risk if the issue remains unresolved?
A personal or global credential can expose the entire management environment and lose audit continuity when staff change. This is the immediate exposure in the named scenario. Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials. A targeted mitigation is: Create a dedicated supported Prism Central service account with narrowly scoped API rights and auditable credential rotation.
Over-broad management privileges can expose other projects or permit unintended platform-wide changes. That exposure applies to prism central role-based management; the direct risk here is: A personal or global credential can expose the entire management environment and lose audit continuity when staff change.
Unconfigured shared management services can conceal a failure or interrupt administrative integrations after handover. That exposure applies to post-imaging essential cluster services; the direct risk here is: A personal or global credential can expose the entire management environment and lose audit continuity when staff change.
Conflicting address authorities can create duplicate IP assignments and unpredictable guest connectivity. That exposure applies to ahv subnet dhcp behavior; the direct risk here is: A personal or global credential can expose the entire management environment and lose audit continuity when staff change.
Please check your mailbox for a message from support@examlabs.com and follow the directions.