NCP-MCI v7.5 Premium File
- 83 Questions & Answers
- Last Update: Nov 16, 2026
An infrastructure owner seeks a repeatable preventive control: A lab owner wants a Prism Central policy to apply only to backup-tagged workloads, while an existing wildcard rule targets every entity. Which continuing control would most directly reduce recurrence of this problem?
Require category-scoped policy reviews and small pilot validation for new central automations. It directly addresses how this condition recurs. Operational acceptance evidence should include: Only the intended categorized VMs match the policy and test actions show no changes to the excluded tenant.
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 policy engine scope and category targeting failures need: Require category-scoped policy reviews and small pilot validation for new central automations.
Require a documented support and protection model for external storage attached to workloads. This safeguard is aimed at external storage integration requirement, whereas recurring policy engine scope and category targeting failures need: Require category-scoped policy reviews and small pilot validation for new central automations.
Review and rotate integration service identities with explicit ownership and limited authorization. This safeguard is aimed at prism central service account permissions, whereas recurring policy engine scope and category targeting failures need: Require category-scoped policy reviews and small pilot validation for new central automations.
A Nutanix administrator must choose an operational response: An infrastructure engineer can view Prism Central inventory but receives access-denied errors when trying to modify a single project. Which action most directly addresses the stated Nutanix infrastructure issue?
Grant an appropriate Prism Central role and resource/project scope rather than expanding to a global administrator permission set. The causal mechanism is: Prism Central IAM roles and assigned scope combine to determine resource-level authorization for management actions. Confirmation should include: The engineer performs required authorized operations in the assigned project and cannot edit unrelated projects or global settings.
Check supported external storage and guest attachment methods and use the documented path appropriate for the workload. This addresses external storage integration requirement, not the cause described in the prism central role-based management scenario. First examine: Inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related.
Correct the Nutanix virtual subnet VLAN ID and upstream trunk allowance as appropriate, then validate the intended IPAM pool. This addresses guest vlan and ipam subnet mismatch, not the cause described in the prism central role-based management scenario. First examine: Inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related.
Recalculate controller VM resources using Nutanix feature-specific sizing guidance and allocate supported CVM memory and CPU before enabling dependent services. This addresses cvm capacity sizing for new services, not the cause described in the prism central role-based management scenario. First examine: Inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related.
An operations engineer needs evidence of a completed fix: An infrastructure engineer can view Prism Central inventory but receives access-denied errors when trying to modify a single project. Which observation would most directly verify that this specific issue is resolved?
The engineer performs required authorized operations in the assigned project and cannot edit unrelated projects or global settings. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. Prism Central IAM roles and assigned scope combine to determine resource-level authorization for management actions.
The integration can read only the required resources and its actions remain attributable to a managed service identity. This is evidence for prism central service account permissions. The required evidence is: The engineer performs required authorized operations in the assigned project and cannot edit unrelated projects or global settings.
The host uplink reports operational status, guest traffic passes on the intended networks and loss of one link behaves as designed. This is evidence for ahv virtual switch uplink selection. The required evidence is: The engineer performs required authorized operations in the assigned project and cannot edit unrelated projects or global settings.
Host and CVM offsets converge within supported operational tolerance and timestamped cluster alerts show consistent event ordering. This is evidence for ntp consistency during cluster formation. The required evidence is: The engineer performs required authorized operations in the assigned project and cannot edit unrelated projects or global settings.
A multicloud infrastructure team is explaining a recurring issue: An infrastructure engineer can view Prism Central inventory but receives access-denied errors when trying to modify a single project. Which technical principle best explains this behavior?
Prism Central IAM roles and assigned scope combine to determine resource-level authorization for management actions. This is the explanation consistent with the stated symptoms. The focused resolution is: Grant an appropriate Prism Central role and resource/project scope rather than expanding to a global administrator permission set.
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 role-based management symptoms. Here the dependency is: Prism Central IAM roles and assigned scope combine to determine resource-level authorization for management actions.
Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials. This explains prism central service account permissions rather than the observed prism central role-based management symptoms. Here the dependency is: Prism Central IAM roles and assigned scope combine to determine resource-level authorization for management actions.
Traffic mirroring copies selected traffic for out-of-band observation; wrong selection or destination reachability can hide evidence or expose extra data. This explains traffic mirroring scope for packet capture rather than the observed prism central role-based management symptoms. Here the dependency is: Prism Central IAM roles and assigned scope combine to determine resource-level authorization for management actions.
A change-risk reviewer evaluates this Nutanix condition: A tenant team must operate only its own project, yet the proposed solution is a globally privileged Prism Central administrator account. What is the most direct avoidable risk if the issue remains unresolved?
Over-broad management privileges can expose other projects or permit unintended platform-wide changes. This is the immediate exposure in the named scenario. Prism Central IAM roles and assigned scope combine to determine resource-level authorization for management actions. A targeted mitigation is: Grant an appropriate Prism Central role and resource/project scope rather than expanding to a global administrator permission set.
Unrestricted management reachability increases attack surface and reduces accountability for privileged operations. That exposure applies to security hardening and change verification; the direct risk here is: Over-broad management privileges can expose other projects or permit unintended platform-wide changes.
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: Over-broad management privileges can expose other projects or permit unintended platform-wide changes.
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: Over-broad management privileges can expose other projects or permit unintended platform-wide changes.
A support engineer must isolate the first implicated dependency: A tenant team must operate only its own project, yet the proposed solution is a globally privileged Prism Central administrator account. Which focused check would best test the suspected cause before a broader change?
Inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related. It tests the specific suspected dependency before wider changes. If confirmed, the relevant action is: Grant an appropriate Prism Central role and resource/project scope rather than expanding to a global administrator permission set.
Inspect certificate SAN entries, issuer/intermediate certificates and the browser validation result for the intended hostname. This check investigates prism central tls certificate chain. For the current symptoms, inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related.
Compare AHV uplink assignment, physical NIC link state and adjacent switch trunk configuration on both paths. This check investigates ahv virtual switch uplink selection. For the current symptoms, inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related.
Compare selected NTP sources, network reachability and reported host/CVM offsets across each proposed member. This check investigates ntp consistency during cluster formation. For the current symptoms, inspect the identity's role, directory membership and project/resource assignments before deciding whether the issue is functional or authorization-related.
An infrastructure owner seeks a repeatable preventive control: A tenant team must operate only its own project, yet the proposed solution is a globally privileged Prism Central administrator account. Which continuing control would most directly reduce recurrence of this problem?
Audit least-privilege role mappings as part of project onboarding and periodic access reviews. It directly addresses how this condition recurs. Operational acceptance evidence should include: The engineer performs required authorized operations in the assigned project and cannot edit unrelated projects or global settings.
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 role-based management failures need: Audit least-privilege role mappings as part of project onboarding and periodic access reviews.
Record a supported isolated-site provisioning procedure and pre-stage verified image versions before deployment windows. This safeguard is aimed at deployment method selection for isolated sites, whereas recurring prism central role-based management failures need: Audit least-privilege role mappings as part of project onboarding and periodic access reviews.
Run cross-environment IP address conflict checks during every new VPC approval. This safeguard is aimed at vpc routing and address planning, whereas recurring prism central role-based management failures need: Audit least-privilege role mappings as part of project onboarding and periodic access reviews.
A Nutanix administrator must choose an operational response: An operator enables a centralized feature but the Prism Central UI reports unmet feature prerequisites related to appliance size and required services. Which action most directly addresses the stated Nutanix infrastructure issue?
Review documented licensing, supported versions and feature prerequisites before activating the dependent Prism Central service. The causal mechanism is: Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement. Confirmation should include: The feature passes prerequisite checks and becomes operational without consuming unsupported or unlicensed capabilities.
Verify supported node count and failure-domain requirements before changing the cluster replication factor or fault tolerance setting. This addresses rf2 and rf3 resiliency prerequisites, not the cause described in the prism central features and prerequisites scenario. First examine: Compare the selected feature's prerequisite matrix with PC version, available resources and license state.
Install a valid certificate and complete supported trust chain whose names match the Prism Central endpoint used by administrators. This addresses prism central tls certificate chain, not the cause described in the prism central features and prerequisites scenario. First examine: Compare the selected feature's prerequisite matrix with PC version, available resources and license state.
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 features and prerequisites scenario. First examine: Compare the selected feature's prerequisite matrix with PC version, available resources and license state.
An operations engineer needs evidence of a completed fix: An operator enables a centralized feature but the Prism Central UI reports unmet feature prerequisites related to appliance size and required services. Which observation would most directly verify that this specific issue is resolved?
The feature passes prerequisite checks and becomes operational without consuming unsupported or unlicensed capabilities. It demonstrates the intended operational outcome rather than simply showing that a setting was entered. Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement.
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 feature passes prerequisite checks and becomes operational without consuming unsupported or unlicensed capabilities.
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 feature passes prerequisite checks and becomes operational without consuming unsupported or unlicensed capabilities.
The integration can read only the required resources and its actions remain attributable to a managed service identity. This is evidence for prism central service account permissions. The required evidence is: The feature passes prerequisite checks and becomes operational without consuming unsupported or unlicensed capabilities.
A multicloud infrastructure team is explaining a recurring issue: An operator enables a centralized feature but the Prism Central UI reports unmet feature prerequisites related to appliance size and required services. Which technical principle best explains this behavior?
Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement. This is the explanation consistent with the stated symptoms. The focused resolution is: Review documented licensing, supported versions and feature prerequisites before activating the dependent Prism Central service.
Machine integrations should use supported nonhuman identities and least privilege rather than shared personal administrator credentials. This explains prism central service account permissions rather than the observed prism central features and prerequisites symptoms. Here the dependency is: Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement.
Distributed storage must reserve capacity to restore expected redundancy after a failed component; raw free capacity is not all spendable. This explains resilient capacity reservation rather than the observed prism central features and prerequisites symptoms. Here the dependency is: Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement.
Traffic mirroring copies selected traffic for out-of-band observation; wrong selection or destination reachability can hide evidence or expose extra data. This explains traffic mirroring scope for packet capture rather than the observed prism central features and prerequisites symptoms. Here the dependency is: Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement.
A change-risk reviewer evaluates this Nutanix condition: A newly installed Prism Central appliance exposes the configuration menu for an optional product, yet no supported license or prerequisite resources are in place. What is the most direct avoidable risk if the issue remains unresolved?
Enabling dependencies out of order can leave partially configured central services and unreliable alerts. This is the immediate exposure in the named scenario. Visible management menus do not guarantee a feature can be safely activated without supporting services, sizing and entitlement. A targeted mitigation is: Review documented licensing, supported versions and feature prerequisites before activating the dependent Prism Central service.
Proceeding with incorrect per-node identity or address mappings can strand a host or place its management services on an unintended network. That exposure applies to foundation discovery and node imaging; the direct risk here is: Enabling dependencies out of order can leave partially configured central services and unreliable alerts.
Broad mirroring can disclose other tenants' traffic while also generating unsustainable packet volumes at the receiver. That exposure applies to traffic mirroring scope for packet capture; the direct risk here is: Enabling dependencies out of order can leave partially configured central services and unreliable alerts.
Correlated power or rack failures may remove multiple copies despite superficially healthy storage capacity. That exposure applies to storage health and fault-domain awareness; the direct risk here is: Enabling dependencies out of order can leave partially configured central services and unreliable alerts.
Please check your mailbox for a message from support@examlabs.com and follow the directions.