Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10) 온라인 연습
최종 업데이트 시간: 2026년02월14일
당신은 온라인 연습 문제를 통해 Nutanix NCP-MCI-6.10 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 NCP-MCI-6.10 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 76개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Nutanix NearSync replication provides the lowest RPO (as low as 1 minute) and is the best option for minimizing data loss in DR scenarios.
Option D (Configure a schedule for 1 minute up to 15 minutes) is correct:
NearSync allows an RPO as low as 1 minute, providing near-continuous data protection.
This is ideal for mission-critical applications where minimal data loss is required.
Option A (Configure NearSync) is incorrect:
While NearSync is the best choice, just enabling it is not enough―the schedule must be set to 1-15 minutes.
Option B (16 to 59 minutes) is incorrect:
NearSync operates within a 1-15 minute range. If set above 15 minutes, it defaults to Async replication.
Option C (Async replication) is incorrect:
Async replication typically has an RPO of 1 hour or more, which does not meet the lowest RPO requirement.
Reference: Nutanix Protection Policies Guide → NearSync vs. Async Replication Nutanix Bible → RPO and RTO in Disaster Recovery
Nutanix KB → Configuring NearSync Replication for Single-Node Clusters
정답:
Explanation:
Nutanix Prism Central requires at least 21 days of usage data to generate accurate Capacity Runway projections.
Option B (21 days) is correct:
Until 21 days of data is collected, no runway analysis is available.
Option A (30 days) is incorrect:
30 days is recommended for long-term accuracy, but not required for initial projections.
Option C (3 months) and Option D (6 months) are incorrect:
Extended data collection helps trend accuracy, but runway calculations begin after 21 days.
Reference: Nutanix Prism Central Guide → Understanding Capacity Runway Calculations
Nutanix KB → Why No Capacity Runway Data is Displayed for New Clusters
정답:
Explanation:
Active-Active bonding allows multiple network interfaces to be used simultaneously, improving bandwidth and redundancy.
Option B (Active-Active) is correct:
This mode enables load balancing across all available adapters, providing higher throughput and fault tolerance.
Option A (No Uplink Bond) is incorrect:
Without a bond, VMs cannot benefit from multiple adapters.
Option C (Active-Active with MAC pinning) is incorrect:
MAC pinning binds traffic to a single NIC, limiting bandwidth distribution.
Option D (Active-Backup) is incorrect:
This mode only provides failover, not increased bandwidth.
Reference: Nutanix AHV Networking Guide → Bonding Modes and Load Balancing Nutanix KB → Optimizing Network Throughput in AHV
정답:
Explanation:
By default, Nutanix Prism Central retains the last 10 instances of a report if no retention policy is configured.
Option B (10) is correct:
Nutanix stores up to 10 reports, after which older reports are automatically deleted.
Options A (5), C (15), and D (20) are incorrect:
While retention policies can be customized, the default setting is 10 reports.
Reference: Nutanix Prism Central Guide → Report Generation and Retention Policies Nutanix KB → How Reports Are Stored and Managed in Prism Central
정답:
Explanation:
vGPU-enabled VMs can only be migrated if the destination host has a compatible GPU and sufficient resources.
Option A (Target host must have sufficient resources) is correct:
The target host must have the same GPU model and enough available resources to support the VM.
vGPU cannot be live-migrated across incompatible hardware.
Option B (vGPU profile change) is incorrect:
The profile does not need to be changed as long as the target host has the same configuration.
Option C (Agent VM required) is incorrect:
Agent VMs are not necessary for vGPU migration.
Option D (Host affinity) is incorrect:
Host affinity limits movement, but is not a prerequisite for migration.
Reference: Nutanix AHV Best Practices → Migrating vGPU-Enabled VMs Nutanix KB → Requirements for Live-Migrating vGPU VMs
정답:
Explanation:
Replication Factor (RF2) means that each piece of data is stored twice across different nodes to ensure availability.
Option B (3 nodes) is correct:
In an RF2 cluster, data redundancy requires at least three nodes to ensure data protection when one node is removed.
If a node is removed from a 3-node cluster, Nutanix automatically redistributes data across the remaining nodes.
Option A (2 nodes) is incorrect:
RF2 requires at least three nodes to maintain fault tolerance.
A 2-node cluster cannot provide full redundancy without a Witness node.
Option C (4 nodes) and Option D (5 nodes) are incorrect:
While larger clusters provide more redundancy, the minimum requirement is 3 nodes.
Reference: Nutanix Bible → Replication Factor (RF) and Fault Tolerance
Nutanix Prism Element Guide → Managing Node Failures and Removals
정답:
Explanation:
Offset-based IP mapping in Nutanix Recovery Plans allows automatic subnet changes during DR failover.
Option D (Utilize Recovery Plan Offset-based IP mapping) is correct:
This method automatically adjusts the IP range while keeping the same last octet.
It eliminates the need for manual intervention after failover.
Option A (Custom script) is incorrect:
Scripting is an option, but Recovery Plan IP mapping is simpler and native to Nutanix.
Option B (Use IPAM) is incorrect:
IP Address Management (IPAM) is useful, but offset-based mapping provides more control.
Option C (Manually update IPs) is incorrect:
This would be time-consuming and error-prone.
Reference: Nutanix Disaster Recovery Guide → Using Offset-Based IP Mapping Nutanix KB → Best Practices for Managing IP Addresses in DR
정답:
Explanation:
Nutanix Categories allow administrators to group related VMs, making Disaster Recovery (DR) planning easier.
Option B (Utilize Categories to organize VMs in Recovery Plans) is correct:
Categories help group VMs based on application tiers (e.g., database, middleware, web servers).
This ensures orderly failover while maintaining application dependencies.
Option A (Naming schema) is incorrect:
Naming conventions help, but they do not provide functional organization in recovery plans.
Option C (1:10 Recovery Plan to VMs) is incorrect:
The ratio depends on business requirements, not a fixed number.
Option D (RESTful APIs) is incorrect:
Automation is useful, but it does not replace proper VM grouping via categories.
Reference: Nutanix Disaster Recovery Guide → Using Categories for DR Management Nutanix KB → Organizing VMs for Disaster Recovery Planning
정답:
Explanation:
Application discovery in Prism Central requires sufficient Prism Central resources and an active internet connection to retrieve application signatures.
Option A (Sufficient Prism Central VM resources) is correct:
Prism Central needs adequate CPU and memory to process application signatures and discovery data.
Option B (Internet connection) is correct:
Application discovery depends on Nutanix’s cloud database to recognize application patterns.
Option C (API key and key ID) is incorrect:
API keys are not required for automatic application discovery.
Option D (Network controller enabled) is incorrect:
Application discovery does not depend on a network controller feature.
Reference: Nutanix Prism Central Guide → Enabling and Using Application Discovery Nutanix KB → Requirements for Application Discovery in Prism Central
정답:
Explanation:
Categories in Nutanix are used to group resources and require only a name and a value for definition.
Option A (A name and a value) is correct:
Categories require a name (e.g., "Production VMs") and a value (e.g., "Tier 1").
These are then applied to VMs, storage, and other resources for policy-based management.
Option B (Policy and Entity) is incorrect:
Policies use categories but are not required to define a category.
Option C (Service and Scope) is incorrect:
Categories do not require services or a defined scope.
Option D (Catalog and Template) is incorrect:
These apply to self-service provisioning, not categories.
Reference: Nutanix Prism Central Guide → Creating and Managing Categories Nutanix KB → Using Categories for RBAC and VM Grouping
정답:
Explanation:
Port mirroring requires the source and target VMs to be on the same host to efficiently copy network
traffic without additional routing overhead.
Option B (Source VM and Target VM are on the same host) is correct:
AHV’s port mirroring only works within a single host because network packets are intercepted before leaving the hypervisor.
If the VMs are on different hosts, mirroring cannot be configured without additional network tools.
Option A (Same VLAN) is incorrect:
VLAN membership is not a requirement for port mirroring.
Option C (Same subnet) is incorrect:
Port mirroring happens at the virtual switch level, which does not require VMs to be in the same subnet.
Option D (Same VPC) is incorrect:
While VPCs provide network isolation, they do not control port mirroring availability.
Reference: Nutanix AHV Networking Guide → Configuring Port Mirroring in AHV Nutanix KB → Port Mirroring Best Practices

정답:
Explanation:
Understanding the Exhibit & the Alert
The alert states:
"The cluster is using password-based SSH access for the CVM."
"Password-based remote login is enabled on the cluster."
"It is recommended to use key-based SSH access instead of password-based SSH access for better security."
This means that the nutanix user can log in to Controller VMs (CVMs) using a password, which is a security risk.
Corrective Action: Enabling Cluster Lockdown
✅ (C) Enable Cluster Lockdown. (Correct Answer)
Cluster Lockdown Mode restricts password-based SSH access and forces key-based authentication.
This prevents users from logging into CVMs using passwords, enhancing cluster security.
To enable Cluster Lockdown:
Go to Prism Central or Prism Element.
Navigate to Settings → Security → Cluster Lockdown.
Enable Cluster Lockdown Mode.
Evaluating the Other Answer Choices
❌ (A) Rename the nutanix user. (Incorrect)
The nutanix user is a built-in system account required for cluster operations.
Renaming the user will not prevent SSH access via password.
❌ (B) Block port 22 on the CVM firewall. (Incorrect)
Blocking port 22 (SSH) will completely disable SSH access, including key-based authentication.
This may break cluster management and troubleshooting operations.
❌ (D) Delete the nutanix user. (Incorrect)
The nutanix user is a critical system account required for cluster functionality. Deleting the account will cause serious issues with cluster management. Multicloud Infrastructure Reference & Best Practices Nutanix Security Best Practices:
Always use key-based SSH authentication instead of password-based logins.
Enable Cluster Lockdown Mode to enforce security policies.
Regularly audit user access to ensure security compliance.
Cluster Lockdown Benefits:
Prevents unauthorized SSH access via passwords.
Enforces public key authentication, reducing brute-force attack risks.
Strengthens CVM security against potential exploits.
Reference: Nutanix Security Guide → Enabling Cluster Lockdown for SSH Security Nutanix KB → Securing SSH Access on Nutanix Clusters
정답:
Explanation:
Data-in-Transit Encryption ensures that replication traffic is encrypted while being sent over the internet.
Option D (Enable Data-in-Transit Encryption) is correct:
This encrypts replicated data between clusters, ensuring security against man-in-the-middle attacks.
Option A (Self-encrypting drive) is incorrect:
This protects data at rest, not during transmission.
Option B (UEFI Secure Boot) is incorrect:
Secure Boot prevents unauthorized OS modifications, but does not encrypt network traffic.
Option C (Data-at-Rest Encryption) is incorrect:
This encrypts stored data but does not secure replication traffic.
Reference: Nutanix Security Guide → Configuring Data-in-Transit Encryption
Nutanix KB → Protecting Replication Traffic Over Public Networks
정답:
Explanation:
A cluster runway below 365 days does not necessarily indicate an issue if Intelligent Operations determines that workloads are sustainable.
Option B (Because new workloads are sustainable) is correct:
Nutanix analyzes resource trends and marks clusters as healthy if new workloads are within projected capacity.
Option A (Storage Runway is still good) is incorrect:
Storage is one component, but CPU and memory also affect runway calculations.
Option C (Recommended resources) is incorrect:
Recommendations help optimize capacity, but do not define cluster health.
Option D (Target is 1 month) is incorrect:
The scenario’s target window does not impact the actual runway calculation.
Reference: Nutanix Prism Central Guide → Capacity Planning & Runway Analysis Nutanix KB → Understanding Capacity Runway and Workload Sustainability
정답:
Explanation:
Receive Side Scaling (RSS) VirtIO-Net Multi-Queue improves network performance by distributing network processing across multiple CPU cores.
Option C (Enable RSS VirtIO-Net Multi-Queue) is correct:
This setting reduces CPU bottlenecks by allowing multiple queues to handle network packets.
It is essential for high-throughput network applications.
Option A (Add more vCPUs) is incorrect:
CPU resources are important, but without enabling RSS, additional vCPUs will not optimize network traffic distribution.
Option B (Enable AHV Turbo Technology) is incorrect:
AHV Turbo improves disk I/O, not network I/O.
Option D (Add more RAM) is incorrect:
RAM does not directly impact network performance.
Reference: Nutanix AHV Best Practices Guide → Optimizing Network Performance with RSS Multi-Queue Nutanix KB → Enabling Multi-Queue for High-Performance Applications