View NCP-MCI-6.10 Exam Questions

Q: 11

A consultant is configuring syslog monitoring and wants to receive CRITICAL logs from the Audit module. Which severity level setting should be configured to get the desired output?

Options

Q: 12

An administrator has been tasked with developing a Prism Central Recovery Plan for 50 workloads that will be assigned new IP addresses and will need to utilize a new DNS server upon instantiation of workloads in the Disaster Recovery (DR) location. What is the best way to accomplish this?

Options

Discussion

Sam G. Mar 30, 2026 12:25 pm

Option B scripting is built for this and C is just a common trap since manual edits don't scale.

Ben L. Mar 17, 2026 6:44 am

A is wrong, B. Nutanix Guest Tools doesn't always set the DNS so scripting is safer here.

Luke B. Mar 29, 2026 4:13 am

Had something like this in a mock, pretty sure it's B. Scripting in the Recovery Sequence is what you use to automate all the network and DNS changes for bulk workloads. Manual updates just wouldn't scale here. Agree?

RileyS Mar 21, 2026 10:06 pm

My vote is B, pretty sure scripting is expected here for automation-C is a trap since it's not scalable for 50 VMs.

Casey Q. Mar 30, 2026 3:11 am

B is definitely the most practical since scripting within the Recovery Sequence automates IP and DNS changes for all VMs. No way you'd want to do C or D with 50 workloads, it's just not scalable. I think Nutanix Guest Tools (A) can help with re-IP but doesn't always handle DNS reliably. Pretty sure B's the way, but open if I'm missing something!

Sara T. Mar 29, 2026 8:42 pm

Its A because Nutanix Guest Tools can handle re-IP for workloads, just not sure if DNS always updates with it.

Chris Q. Mar 19, 2026 6:40 am

Yeah, nutanix scripting in the recovery sequence (B) is made for automating stuff like re-IP and DNS changes at DR. Doing this manually for 50 workloads just isn't practical. Pretty confident it's B, but I suppose A could work in some rare setups.

Sara Mar 20, 2026 2:52 am

I'd say B makes sense since custom scripts in the Recovery Plan automate IP and DNS changes for all VMs. Honestly, official guides and hands-on labs both mention this approach, but I'm not 100% sure if A could maybe work too. Agree?

Piya Apr 1, 2026 12:20 am

Pretty sure B is what Nutanix wants here since scripting in the Recovery Sequence lets you update IP and DNS for all VMs at once. No way you'd want to do C (manual updates) for 50 workloads, that's just not realistic. Open to being proven wrong but automation is key for DR scenarios!

Avery T. Mar 18, 2026 1:23 am

Scripting in the recovery sequence is really the way to go here. B

Be respectful. No spam.

Q: 13

An administrator receives complaints about VM performance.

After reviewing the VM’s CPU Ready Time data shown in the exhibit, which step should the administrator take to diagnose the issue further?

Options

Correct Answer:

Explanation

Understanding the Issue

The administrator is investigating VM performance complaints and is analyzing CPU Ready Time

data.

CPU Ready Time is a crucial metric in Nutanix and virtualization environments (AHV, ESXi, or Hyper-

V).

It measures the amount of time a VM is waiting for CPU scheduling due to resource contention.

High CPU Ready Time indicates that VMs are ready to run but are waiting because the host lacks

available CPU resources.

Analysis of the Exhibit

The graph shows CPU Ready Time spikes for multiple VMs.

Some VMs have CPU Ready Time exceeding 18% to 21.5%, which is very high.

A healthy CPU Ready Time should be below 5%.

Values above 10% indicate CPU contention, and anything above 20% is critical and requires

immediate troubleshooting.

Evaluating the Answer Choices

❌ (A) Check the number of vCPUs assigned to each CVM. (Incorrect)

CVMs (Controller VMs) have fixed CPU allocation, and modifying their vCPU count is not

recommended unless advised by Nutanix Support.

The issue is related to VM CPU contention, not CVM configuration.

✅ (B) Review host CPU utilization. (Correct Answer)

High CPU Ready Time suggests CPU overcommitment or host saturation.

The administrator should check host CPU usage in Prism Central to determine if the cluster is

overloaded.

If host CPU usage is consistently above 85–90%, VMs are competing for CPU resources, leading to

high CPU Ready Time.

❌ (C) Assess cluster SSD capacity. (Incorrect)

SSD capacity impacts storage performance (latency, read/write speeds) but does not affect CPU

Ready Time.

High CPU Ready Time is a CPU scheduling issue, not a storage bottleneck.

❌ (D) Enable VM memory oversubscription. (Incorrect)

Memory oversubscription does not impact CPU scheduling.

Enabling memory oversubscription affects RAM allocation, but CPU Ready Time is strictly related to

CPU contention.

Next Steps to Diagnose & Resolve the Issue

Review Host CPU Utilization:

Navigate to Prism Central → Analysis → CPU Usage per Host.

Identify hosts experiencing high CPU load.

Check VM vCPU Allocation:

Ensure that VMs do not have excessive vCPUs assigned, which can lead to scheduling inefficiencies.

Overprovisioning vCPUs can cause unnecessary contention.

Balance Workload Across Hosts:

Use Nutanix AHV DRS (Dynamic Scheduling) or VMware DRS to redistribute VMs across hosts.

Check if certain hosts are overloaded while others have spare CPU capacity.

Consider Scaling Out the Cluster:

If CPU usage is consistently high, adding more nodes may be required to reduce CPU contention.

Multicloud Infrastructure

References

& Best Practices

CPU Ready Time Best Practices:

Keep CPU Ready Time below 5%.

Avoid overcommitting vCPUs on heavily loaded hosts.

Monitor Prism Central Runway Metrics to predict future CPU resource needs.

Nutanix AHV CPU Scheduling Optimization:

Ensure proper VM sizing (avoid excessive vCPU allocation).

Balance workloads using Nutanix AHV DRS.

References:

Nutanix Prism Central: Performance Analysis and CPU Metrics

Nutanix Bible: VM Performance and Resource Management

Nutanix KB: Troubleshooting High CPU Ready Time in AHV

Q: 14

An administrator wants to ensure that VMs can be migrated and restarted on another node in the event of a single-host failure. What action should be taken in Prism Element to meet this requirement?

Options

Q: 15

An administrator is managing a 4-node cluster with different hardware generations: Two G5 Nodes → 2 CPUs (12 cores), 1 SSD (1.92 TB), 2 HDDs (4 TB). Two G7 Nodes → 2 CPUs (16 cores), 2 SSDs (1.92 TB), 4 HDDs (4 TB). The cluster will be decommissioned from production and used for Disaster Recovery (DR) purposes with an RPO of 1 hour. What is the best approach when replacing G5 nodes without impacting performance?

Options

Discussion

Zoe Mar 28, 2026 9:57 am

I don’t think it’s C. A lines up better since Nutanix clusters push for balanced SSD resources per node to avoid performance issues, especially in DR with a low RPO. Matching the G7's 2 SSDs ensures you’re not creating a bottleneck. Pretty sure from exam reports this is what they're looking for.

Riley K. Apr 1, 2026 2:48 am

I get why people are picking D, but I'd say A makes more sense for DR. Matching SSD count is key so you don't end up with storage bottlenecks on those new nodes. D is a trap option because hybrid type alone isn't enough to guarantee balanced performance.

QuickLead8043 Apr 2, 2026 5:54 am

C or A? I get why people say D because the cluster's already hybrid, but for DR with a tight RPO, having at least 2 SSDs (like A) would really help match G7 node performance. Pretty sure storage speed matters more here than just the type. Open to hearing if anyone has real-world experience proving otherwise.

Cameron C. Mar 22, 2026 1:23 pm

Probably A, not D. D feels like a distractor since hybrid alone doesn't guarantee enough SSDs for performance.

Neha T. Mar 22, 2026 11:23 pm

A , matching the SSD count is the big thing here for DR. If your new node has at least 2 SSDs, it lines up with the G7s and helps avoid performance hits, especially with that tight RPO. Chime in if anyone's made this swap and seen different results.

Amelia M. Mar 21, 2026 1:05 am

Its A, but if all nodes were upgraded to all-flash this flips, so watch the node type.

Mason Apr 3, 2026 5:04 pm

A makes the most sense. Matching at least 2 SSDs aligns storage performance with your G7 nodes and keeps DR reliable, especially for a tight 1-hour RPO. Going hybrid only (D) doesn't guarantee the same SSD resources. Pretty sure A is right, but let me know if there's a catch.

Reese B. Mar 26, 2026 6:31 am

D . The cluster already uses hybrid nodes so I'd think keeping the replacement as hybrid is what matters most, especially for DR where you want similar storage types across nodes. Am I missing something?

Luke M. Mar 19, 2026 2:50 am

Option D seems right to me, since the existing nodes are hybrid, so keeping the new node hybrid should maintain cluster consistency. But if the "best" means matching just storage speed and not type, would you still pick D? If DR required all-flash for some reason instead of hybrid that could change my answer.

Be respectful. No spam.

Q: 16

An administrator wants to ensure that user VMs on AHV hosts can take advantage of bandwidth beyond a single adapter in a bond. Which uplink Bond Type should the administrator configure to accomplish this?

Options

Q: 17

An administrator attempted to enable Data-in-Transit Encryption on a Scale-Out Prism Central cluster to encrypt service-level traffic between nodes. However, the feature did not work correctly due to a firewall restriction. Which CVM-specific port should be allowed through the firewall for Data-in-Transit Encryption?

Options

Discussion

Jason G. Mar 17, 2026 6:20 am

Option A

Luna Mar 27, 2026 2:27 pm

A tbh

Jamie Apr 5, 2026 1:46 am

C , I'd go with 2020 since that's sometimes used for secure comms in other contexts, though I might be mixing it up. Anyone else seen this port referenced for DiTE on Prism Central?

Nina V. Apr 1, 2026 10:39 pm

I don’t think C fits here, A is the port for Prism Central KMS cluster traffic when enabling Data-in-Transit Encryption. The other ports have different roles. Pretty sure from Nutanix docs, but open to correction if I missed something.

ThoughtfulReviewer3417 Mar 20, 2026 1:13 am

Official Nutanix guide and exam practice both show A for this, so I'd stick with that unless there's a newer doc out.

Ishaan Mar 27, 2026 8:04 am

Nah, not D-9440 is only for Prism UI/API. For Data-in-Transit Encryption on Scale-Out Prism Central, it's A since port 2009 is used by KMS communication between CVMs. Easy to get tricked by the others because they look familiar, but only 2009 fits here. Pretty sure that's spot on, but let me know if you see otherwise.

Sara S. Mar 21, 2026 7:33 pm

Chris E. Mar 29, 2026 1:44 am

A here. Port 2009 is what Prism Central uses for the KMS cluster traffic needed for Data-in-Transit Encryption. Other ports don’t relate directly to DiTE in this context. Pretty sure unless Nutanix updates change it, let me know if I missed something.

Jamie Mar 28, 2026 2:07 pm

D , but think it's a trap. Port 9440 is for Prism UI/API, not for Data-in-Transit Encryption specifically. A is correct for Scale-Out Prism Central based on what I've seen, but double-check your environment docs if unsure.

Cameron Apr 2, 2026 2:51 am

Seen exactly similar question in my exam, it's A.

Be respectful. No spam.

Q: 18

A user created a report in the Intelligent Operations Analysis Dashboard but forgot to download it. However, after logging back into Prism Central, the administrator finds that the report is no longer available. What is the most likely cause?

Options

Q: 19

Per organizational requirements, an administrator has uploaded a signed SSL certificate to Prism for Common Access Card (CAC) authentication. Once the certificate has been uploaded successfully, the certificate appears to be valid but CAC authentication is not functional. What is a potential cause of this problem?

Options

Q: 20

An administrator would like to plan for new project-related growth. New project workload requirements have been included for a cluster named ClusterXYZ: · 2 Medium Sized SQL Servers · 10 VMs with 16Gb RAM, 4 vCPU, 100GB Storage Which two additional information items should be added to the capacity planning scenario to provide a proper capacity runway expectation? (Choose two.)

Options

Discussion

QuinnK Mar 18, 2026 4:25 am

A and B make sense here. You need storage compression ratios to estimate actual usable capacity, and the dates for workload rollout are key to runway planning. C's a common trap since cluster specs are already factored in as baseline. If I'm off let me know.

Liam Y. Mar 28, 2026 5:39 pm

C , since knowing the current cluster hardware specs helps predict real capacity runway. Official guide and practice exams push that kind of detail too. Maybe I’m missing something, but option A feels less immediate here. Agree?

Mia P. Mar 20, 2026 7:10 pm

C/D? Both could be relevant, because cluster hardware specs and change in demand seem important for forecasting capacity.

Sean C. Mar 18, 2026 6:56 pm

Not sure about C or D honestly. For capacity runway, the traps are thinking you need cluster specs (C), but that's usually baseline info. It's A and B here since compression and workload timing actually change future estimates. Lots of similar trick wording on these Nutanix questions.

Sam T. Mar 26, 2026 7:52 am

Not seeing it for C or D here. For true capacity runway on Nutanix clusters, you really need to know both the storage compression ratio (A) and when the workloads hit the cluster (B). Hardware specs are already known for ClusterXYZ, and demand percentage is less precise. Trap seems to be C since it isn't 'additional' info in this context.

Adam Mar 23, 2026 12:25 am

Option A and B. If the timing of when workloads get added changes, would that influence the best picks here?

Be respectful. No spam.

Question 11 of 20 · Page 2 / 2

Premium Access Includes

✓ Quiz Simulator
✓ Exam Mode
✓ Progress Tracking
✓ Question Saving
✓ Flash Cards
✓ Drag & Drops
✓ 3 Months Access
✓ PDF Downloads

Get Premium Access

Premium Access Includes

FLASH OFFER

avail 10% DISCOUNT on YOUR PURCHASE