An administrator has configured AHV Metro Availability with Witness and is testing failover scenarios.
During testing, the administrator disconnects the primary and recovery clusters but Prism Central remains connected to the recovery site.
What are two expected system behaviors? (Choose two.)
When connectivity between Metro clusters is lost, Nutanix Metro Availability ensures data integrity using Witness for automatic failover.
Option A (Guest VM I/O operations pause until connectivity is restored) is correct:
Metro Availability enforces data consistency, so I/O operations pause until failover is confirmed.
Option C (Guest VMs failover automatically to the recovery cluster) is correct:
The Witness VM detects the failure and initiates an automatic failover to the secondary cluster.
Option B is incorrect:
Prism Central does not control VM failover in Metro Availability.
Option D is incorrect:
The primary cluster is unreachable, so VMs cannot continue running there.
Nutanix Metro Availability Guide How Witness Handles Failover Scenarios
Nutanix KB I/O Freezing and Failover Behavior in Metro Clusters
What guest customization options are available when creating a VM template?
Guest customization options allow administrators to automate OS configuration during VM deployment from a template.
Option A (Sysprep, Cloud-init, Custom Script, Guided Script) is correct:
Sysprep (for Windows) and Cloud-init (for Linux) enable custom OS configurations.
Custom Scripts can be used for advanced automation.
Options B and C are incorrect:
Bash, Powershell, Python, and YAML can be used in automation, but they are not guest customization options in VM templates.
Option D is incorrect:
Guest customization is fully supported in Nutanix templates.
Nutanix VM Deployment Guide Using Cloud-Init and Sysprep for Guest Customization
Nutanix KB Automating VM Deployments with Guest Customization
An administrator notices high CPU usage on a VM and wants to determine whether adding more vCPUs would improve performance.
Which two metrics should be analyzed to make this decision? (Choose two.)
When diagnosing CPU performance issues, CPU Ready Time and CPU Usage are the key indicators of whether more vCPUs are needed.
Option A (VM CPU Ready Time) is correct:
High CPU Ready Time means the VM is waiting for CPU resources, indicating CPU contention.
Option B (VM CPU Usage) is correct:
If CPU usage is consistently high, adding more vCPUs may improve performance.
Option C (Host CPU Usage) is incorrect:
Host-wide CPU usage does not indicate whether a specific VM needs more vCPUs.
Option D (Host Memory Swap Out Rate) is incorrect:
Memory swapping affects RAM performance, not CPU allocation.
Nutanix Prism Central Guide Analyzing VM CPU Performance
Nutanix KB Understanding CPU Ready Time and VM Performance
An administrator is protecting an application and its data stored on Volume Groups using Protection Domains.
During failover tests, all application VMs restore successfully, but the application data is completely missing.
How can the Protection Domain configuration be adjusted to avoid this issue in the future? (Choose two.)
Protection Domains (PDs) in Nutanix ensure that entire applications and their associated data are protected during failover. However, Volume Groups (VGs) are not automatically included unless explicitly configured.
Option A (Select 'Auto protect related entities') is correct:
This setting ensures that associated Volume Groups, networks, and other dependencies are included in the Protection Domain automatically.
Without enabling this, only the VM itself would be protected, leading to missing application data upon failover.
Option B (Manually add Volume Groups to Protected Entities) is correct:
If 'Auto protect related entities' is not enabled, the administrator must manually add Volume Groups to the Protection Domain.
This ensures that both VMs and their attached Volume Groups are replicated and recovered together.
Option C (Place Volume Groups in a separate Protection Domain) is incorrect:
Separating Volume Groups into a different PD does not guarantee they failover together with VMs.
It is best practice to keep related VMs and Volume Groups in the same PD.
Option D (Use application-consistent snapshots) is incorrect:
While application-consistent snapshots improve data integrity, they do not fix missing Volume Groups in failover scenarios.
Nutanix Disaster Recovery Guide Protection Domain Configuration and Volume Groups
Nutanix KB Ensuring Volume Groups Are Included in Disaster Recovery Failovers
An administrator needs to enable Windows Defender Credential Guard to comply with company policy.
The new VM configurations include:
Legacy BIOS
4 vCPUs
8 GB RAM
Windows Server 2019
What must be changed in order to properly enable Windows Defender Credential Guard?
Windows Defender Credential Guard requires UEFI firmware and Secure Boot to function properly.
Option B (Enable UEFI with Secure Boot) is correct:
Credential Guard requires a UEFI-based boot mode rather than Legacy BIOS.
Secure Boot ensures only trusted OS components load, reducing attack surface for credential theft.
Option A (Update vCPU to 8) is incorrect:
Increasing vCPUs does not impact Credential Guard compatibility.
Option C (Use Windows Server 2022) is incorrect:
Windows Server 2019 supports Credential Guard; upgrading to 2022 is not required.
Option D (Update Memory to 16GB) is incorrect:
Credential Guard has no minimum RAM requirement beyond general OS needs.
Microsoft Docs Requirements for Windows Defender Credential Guard
Nutanix AHV VM Management Guide Enabling Secure Boot & UEFI for Windows VMs
Dulce
3 days agoAntonio
4 days ago