Nutanix Certified Services Core Infrastructure Professional Free Sample Questions

While all options are potential issues, the scenario provides key clues. Direct IPMI web access (TCP) works, but Foundation discovery relies on IPMItool, which uses UDP port 623 for SOL (Serial over LAN) and other functions. A common oversight is a firewall rule that allows TCP traffic for web access but blocks the necessary UDP ports for automated management tools like Foundation. Incorrect credentials would cause an authentication error, not a discovery failure. STP issues usually resolve after a delay, they don't typically cause a node to be completely undiscoverable. If the Foundation VM had no route, it likely wouldn't discover any nodes.

To achieve consistent permissions across SMB (Windows) and NFS (Linux), Nutanix Files needs a way to map Windows SIDs to Linux UID/GIDs. This is accomplished by joining an AD domain and configuring an LDAP provider (often AD itself) that includes RFC2307 attributes (like uidNumber and gidNumber) for the users and groups.

After setting up the user mapping source (AD/LDAP), you must explicitly enable multi-protocol access at the share or export level. This tells Nutanix Files to perform the SID-to-UID/GID translation and enforce permissions consistently for users accessing the same data from different protocols.

This is true. The cluster expansion process is designed to be seamless with DaRE. When new nodes are added, the cluster's Key Management Server (KMS) distributes the necessary encryption keys to the new CVMs. The nodes then perform a background process to encrypt their drives and integrate into the storage pool, inheriting the cluster's security posture automatically.

The scenario describes a read-intensive workload on hybrid nodes experiencing high read latency. This strongly suggests that the application's hot data is not being consistently served from the SSD tier. Flash Mode (SSD pinning) is the feature designed specifically for this use case. It forces the selected vDisks' data to remain in the SSD tier, guaranteeing low-latency reads and providing the most direct solution to the described problem. Increasing CVM memory helps metadata, not necessarily data reads. EC-X improves capacity but can add latency, making it unsuitable here. Adding more nodes is a valid but much more costly and less targeted solution.

NearSync replication schedules (1-15 minutes RPO) and the underlying lightweight snapshot (LWS) mechanism are managed and orchestrated by Prism Central. Therefore, both the source and destination clusters must be registered to and managed by the same Prism Central instance for NearSync to be configured and to function correctly. While network latency and hypervisor compatibility are important operational factors, the management dependency on a single Prism Central is a fundamental prerequisite.

To support tagged VLANs for CVM and hypervisor traffic, the physical switch ports must be configured as trunk ports (or the equivalent terminology for the switch vendor). A best practice is to set the native (untagged) VLAN to a dedicated, unused VLAN ID. This ensures that no untagged traffic inadvertently ends up on a production VLAN and forces all traffic, including management, to be explicitly tagged. The management VLAN ID will then be specified during the Foundation process or node configuration.

The NCC output provides detailed information for each check, including the reason for failure and the thresholds used. Before taking any corrective action, the first and most logical step is to analyze this output. It will clarify if memory usage is slightly above a warning threshold or critically high, and it often provides links to relevant knowledge base articles. This information is crucial for determining the correct next action, which might range from adjusting CVM memory (if supported for the enabled features) to identifying a specific memory-consuming process.

Firmware upgrades for certain hardware components, like SATADOMs, cannot be performed while the main AOS is running. The automated LCM process handles this by rebooting the CVM into a special maintenance environment called Phoenix. From Phoenix, it can safely apply the low-level firmware update. The LCM process orchestrates this one node at a time to maintain cluster availability.

The balance-tcp mode in AHV networking uses LACP (Link Aggregation Control Protocol) and load balances traffic based on a hash of Layer 4 information (source/destination IP and TCP/UDP port). This provides a more granular and effective distribution of traffic from multiple VMs and sessions across all active uplinks in the bond, making it the ideal choice for maximizing throughput in a high-traffic environment. balance-slb balances based on source MAC address, which can lead to uneven link utilization. active-backup only provides redundancy, not load balancing.

This solution correctly addresses all constraints. An Asynchronous Protection Domain with a 60-minute schedule meets the 1-hour RPO. In-transit encryption can be enabled on the remote site configuration to satisfy the security requirement. Critically, a remote site throttling policy allows the consultant to limit the bandwidth used by replication during business hours (9-5) to avoid impacting other critical traffic, while allowing it to use more bandwidth overnight. Metro Availability is not feasible due to the 25ms latency. NearSync is unnecessary as the RPO is 60 minutes. Cloud Connect requires a cloud subscription, which was not mentioned.