Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10) 온라인 연습
최종 업데이트 시간: 2025년06월05일
당신은 온라인 연습 문제를 통해 Nutanix NCP-MCI-6.10 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 NCP-MCI-6.10 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 76개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Multicast traffic can generate unnecessary overhead if it is not properly managed. IGMP Snooping (Option C) ensures that multicast packets are only sent to VMs that have requested them, rather than broadcasting to all VMs.
Option C (IGMP Snooping) is correct:
It reduces unnecessary multicast traffic by ensuring that only subscribed VMs receive the packets.
It is supported natively in AHV networking.
Option A (LACP) is incorrect:
Link Aggregation Control Protocol (LACP) improves bandwidth and redundancy but does not control multicast traffic.
Option B (UDP) is incorrect:
UDP (User Datagram Protocol) is a transport protocol, not a network optimization feature.
Option D (Network Segmentation) is incorrect:
Segmentation (VLANs, VPCs) isolates networks but does not optimize multicast traffic specifically.
Reference: Nutanix AHV Networking Guide → Enabling IGMP Snooping Nutanix Bible → Network Traffic Optimization in AHV Nutanix KB → Best Practices for Multicast Traffic in AHV
정답:
Explanation:
CPU Ready Time indicates how long a VM waits for CPU resources due to contention.
Option B (Review host CPU utilization) is correct:
If CPU utilization is high, there may be excessive CPU overcommitment, leading to high CPU Ready Time.
Adding more hosts or reducing vCPU allocations may resolve the issue.
Option A (Check CVM vCPUs) is incorrect:
The Controller VM (CVM) does not directly impact application VM performance in this case.
Option C (Assess SSD capacity) is incorrect:
CPU Ready Time is unrelated to storage performance.
Option D (Enable VM memory oversubscription) is incorrect: Memory oversubscription does not affect CPU contention.
Reference: Nutanix Prism Central Guide → Troubleshooting VM Performance Nutanix KB → Identifying High CPU Ready Time and Solutions
정답:
Explanation:
he Prism Central Memory Cluster Runway Diagram provides insights into memory usage trends, predicting how long the cluster can sustain workloads before exhausting resources. The solid blue area represents the actual memory consumption over time.
The dotted red line represents the effective memory capacity limit based on the cluster's current configuration.
Analyzing the Dotted Red Line
The dotted red line is labeled "Effective Capacity: 503.22 GiB", which means:
It is the total usable memory capacity in the cluster after considering hypervisor overhead, redundancy settings, and failover capacity.
This value is not a hard limit but an indication of the available memory before potential performance issues occur.
Evaluating the Answer Choices
❌ (A) It is the default trend analysis static threshold that can be manually set. (Incorrect) The dotted red line is not a static threshold that an administrator can manually configure. Trend analysis in Prism is dynamic and based on workload history and projections.
❌ (B) It is the maximum memory the administrator can assign to VMs. (Incorrect)
Administrators can oversubscribe memory beyond the dotted red line if memory overcommitment is enabled.
However, oversubscribing memory beyond effective capacity may impact performance.
❌ (C) It is the calculated memory oversubscription limit for currently running VMs. (Incorrect) The dotted red line does not represent oversubscription limits.
Memory oversubscription depends on hypervisor memory ballooning, compression, and swapping mechanisms, which are not directly shown here.
✅ (D) It is the usable capacity based on cluster configuration options. (Correct Answer)
The dotted red line (503.22 GiB) represents the actual usable memory available in the cluster after
factoring in system overhead.
This value is determined by:
Total physical memory (256 GB per host × 3 hosts = 768 GB) Memory reserved for hypervisor and system processes Cluster failover and redundancy settings Intelligent Operations capacity analysis
Multicloud Infrastructure Reference & Best Practices
Prism Central’s "Runway" feature provides AI-driven trend analysis for memory, CPU, and storage capacity.
The effective capacity limit helps administrators make proactive scaling decisions before resources become critical.
To increase the memory runway, administrators can:
Optimize VM memory allocation.
Add more hosts to the cluster.
Enable memory deduplication and compression (if available).
정답:
Explanation:
Metro Availability in Nutanix requires that the primary and secondary storage containers be configured identically to ensure data replication consistency.
Option C (The destination storage container is not empty) is correct:
The remote storage container must be empty before Metro Availability can be enabled.
Existing data can cause conflicts and prevent it from appearing in the "Compatible Remote Sites" list.
Option D (Both storage containers must have the same name) is correct:
Metro Availability requires that storage containers have identical names across clusters.
If names do not match, the storage container will not be listed as compatible.
Option A is incorrect: Metro Availability works regardless of hardware vendor differences.
Option B is incorrect: Compression does not affect compatibility but may impact performance.
Reference: Nutanix Metro Availability Deployment Guide
Nutanix Best Practices for Configuring Remote Sites for Metro Availability Nutanix KB → Troubleshooting Storage Container Issues in Metro Availability
정답:
Explanation:
In Nutanix Prism Central, user-generated reports in Intelligent Operations are stored for a limited time and then deleted automatically.
Option C (Reports are automatically deleted after 24 hours) is correct:
Reports do not persist indefinitely unless they are scheduled reports.
One-time reports expire after 24 hours.
Option A (Cluster Viewer deleted the report) is incorrect:
Cluster Viewer does not have permissions to delete reports.
Option B (Report was archived) is incorrect:
Nutanix does not automatically archive reports.
Option D (Report stored in Prism Element) is incorrect:
Reports are generated and stored only in Prism Central, not Prism Element.
Reference: Nutanix Prism Central Guide → Intelligent Operations & Report Retention Policies Nutanix KB → Why Reports in Prism Central Are Not Persisting
정답:
Explanation:
The Update Guest OS feature (Option D) in Nutanix allows administrators to apply patches and updates to a VM template by creating a temporary VM instance for modification.
How It Works:
A temporary VM is deployed from the template.
Administrators apply updates to the OS.
Once complete, the changes are saved back to the template.
Option A (Create VM from Template) is incorrect:
This feature creates a new VM from an existing template but does not update the template itself.
Option B (Complete Guest OS Update) is incorrect:
There is no specific Nutanix feature named "Complete Guest OS Update."
Option C (Update Configuration) is incorrect:
Updates VM hardware and policies but not the OS.
Reference: Nutanix Prism Central → Managing VM Templates and Guest OS Updates Nutanix Bible → OS Management and Updates in Nutanix Environments Nutanix KB → How to Patch OS in a Nutanix VM Template
정답:
Explanation:
The Bully VMs List (Option C) in Prism Central’s Intelligent Operations identifies VMs consuming excessive CPU, memory, or storage, which negatively affects other VMs.
Option A (Inactive VMs List) is used for identifying unused VMs but does not detect performance issues.
Option B (Overprovisioned VMs List) helps identify VMs with excessive allocated resources, but it does not focus on live performance impact.
Option D (Constrained VMs List) highlights VMs suffering from resource contention, not those
causing it.
Reference: Nutanix Prism Central → Intelligent Operations and Performance Tuning Nutanix KB → Identifying and Managing Resource-Hogging VMs
정답:
Explanation:
When creating a storage container in Nutanix, the administrator must configure the correct capacity settings:
Option A (Prism Element with Advertised Capacity of 100 GiB) is correct:
Advertised Capacity defines logical limits for the container (i.e., how much space it reports as available).
Inline Compression can be enabled directly in Prism Element.
Option B (Create in Prism Element without Advertised Capacity) is incorrect:
Without specifying Advertised Capacity, the container may consume unlimited storage.
Option C (Create in Prism Central with Reserved Capacity) is incorrect:
Reserved Capacity applies to Quality of Service (QoS) policies, not storage limits.
Option D (Create in Prism Central without capacity limits) is incorrect:
Prism Central can manage storage but does not directly enforce RF1 and compression policies.
Reference: Nutanix Storage Management Guide → Creating and Managing Storage Containers Nutanix Bible → Replication Factor (RF) and Data Optimization Nutanix KB → Inline Compression Best Practices in Nutanix AOS
정답:
Explanation:
During failover in Nutanix Disaster Recovery, VMs retain their static IPs but may lose DNS settings if the network configuration at the DR site is different from the primary site.
Option B (Create custom in-guest scripts) is correct:
Custom scripts allow Windows or Linux VMs to restore DNS settings automatically after failover.
These scripts can be executed using post-failover automation in Nutanix DR policies.
Option A (Self-Service Restore) is incorrect:
Self-Service Restore is used for end-user recovery of deleted files, not for network settings.
Option C (nncli tool) is incorrect:
The nncli tool is used for network troubleshooting, but it does not automatically restore DNS settings.
Option D (Configure a Protection Domain) is incorrect:
Protection Domains define replication policies, but they do not fix DNS settings after failover.
Reference: Nutanix Disaster Recovery Guide → Failover Automation and Network Configuration Nutanix Bible → VM Recovery and IP Management in DR Scenarios Nutanix KB → Preserving DNS Settings in Disaster Recovery
정답:
Explanation:
If a VM is unable to migrate, the most likely cause is that it is an Agent VM (such as a Nutanix Witness VM or a VM with special dependencies).
Option C (Disable Agent VM) is correct:
Some Agent VMs are configured to prevent migration due to critical roles (e.g., a Witness VM for Metro Availability).
Disabling Agent VM restrictions allows it to migrate before a host enters maintenance mode.
Option A (Enable ADS) is incorrect:
Acropolis Dynamic Scheduling (ADS) helps with VM placement after migration, but it does not force
an unmigratable VM to move.
Option B (Update LLDP) is incorrect:
LLDP is used for network discovery, but it does not impact VM migration behavior.
Option D (Configure backplane port groups) is incorrect:
Backplane settings impact CVM communication, not VM migration.
Reference: Nutanix Prism Element Guide → Managing Agent VM Settings Nutanix Bible → Host Maintenance and VM Live Migration Nutanix KB → Troubleshooting VM Migration Failures in AHV
정답:
Explanation:
High Availability (HA) in Nutanix provides priority-based VM restart capabilities to ensure that certain
VMs are powered on before others in the event of a host reboot or failure.
Option C (High Availability) is correct:
Nutanix HA policies allow administrators to prioritize VM startup order to ensure that critical services (such as database VMs or management VMs) are available before others.
Option A (Recovery Plan) is incorrect:
Recovery Plans are used in Disaster Recovery (DR) scenarios and do not control boot order during normal host restarts.
Option B (Host Affinity) is incorrect:
Host Affinity is used to keep a VM pinned to a specific host, but it does not control boot sequencing.
Option D (Agent VM) is incorrect:
Agent VMs (such as Witness VMs) are specialized virtual machines used for Metro Availability, not
general boot priority settings.
Reference: Nutanix Prism Element Guide → Configuring HA Reservation and VM Priority Nutanix Bible → High Availability (HA) and VM Failover
Nutanix KB → VM Restart Priority in High Availability Configurations
정답:
Explanation:
When Life Cycle Manager (LCM) reports that a newer framework version is available, the correct action is to perform an inventory scan (Option C).
Performing an inventory scan updates the available firmware/software versions and allows LCM to download required updates.
Option A (Run an AOS upgrade) is unrelated to the LCM framework update process.
Option B (Run an AHV upgrade) is a separate component update and does not affect the LCM framework.
Option D (Download manually from a CVM) is not necessary because LCM updates are automatically pulled after an inventory scan.
Reference: Nutanix LCM User Guide → Updating LCM Framework and Performing Inventory Scans Nutanix KB → Best Practices for LCM Updates Nutanix Prism Central → LCM Update Workflow
정답:
Explanation:
Storage Policies in Nutanix allow administrators to configure data protection and performance settings at the storage container level.
Replication Factor (RF) defines the number of copies of data stored across nodes for fault tolerance.
Encryption ensures that data at rest is protected via Nutanix-native encryption methods.
Option A (Storage Containers and Volume Groups) refers to storage organization, not policies.
Option C (Shares and Object Stores) applies to file and object storage services, not VM storage policies.
Option D (Data Protection and Security) is a broad term but does not define specific policy attributes.
Reference: Nutanix Prism Element → Storage Policies and Replication Factor (RF)
Nutanix Bible → Storage Fabric and Data Resiliency
Nutanix KB → Enabling Encryption in Storage Policies
정답:
Explanation:
Nutanix Intelligent Operations Reports (Option D) provide weekly summaries of cluster health, performance, and resource consumption.
These reports include recommendations for optimization, alerts, and forecasted resource usage trends.
Option A (Admin Center LCM) manages firmware and software upgrades but does not generate weekly performance reports.
Option B (Prism Central Syslog) is used for logging and event tracking, not performance summaries.
Option C (Infrastructure VMs List) provides a static list of VMs but does not generate periodic reports.
Reference: Nutanix Prism Central → Intelligent Operations and Reports Nutanix Bible → Automated Insights for Cluster Health Monitoring Nutanix KB → Using Intelligent Operations Reports for Capacity Planning
정답:
Explanation:
In Nutanix Prism Central, categories allow administrators to group and organize entities for management, automation, and policy enforcement.
Alerts (Option B) can be categorized to group similar system events and create filtering rules. Virtual Machines (Option C) can be categorized to apply security policies, automation tasks, and resource allocation rules.
Option A (Storage Containers) cannot be categorized in Prism Central. Storage policies apply at the container level but are not managed via categories.
Option D (ISO Images) cannot be categorized because ISOs are static objects, not active entities.
Reference: Nutanix Prism Central Guide → Working with Categories
Nutanix Bible → Category-Based Management and Security Policies Nutanix KB → Using Categories for VM Management in Prism Central