Nutanix Updated NCA-6.10 Exam Questions and Answers by zackary

The OpLog (Operational Log) in Nutanix serves as apersistent write bufferfor incoming I/O operations. It temporarily stores write requests to ensure fast acknowledgment to clients and better performance. The data is later coalesced and written to the Extent Store for long-term storage.

A. Persistent write buffer:Correct, as the OpLog optimizes write performance by buffering writes temporarily.

B. Persistent data storage:Incorrect, as this describes the Extent Store, not the OpLog.

C. Global metadata:Incorrect, as metadata operations are handled by the Metadata Store.

D. Dynamic read cache:Incorrect, as read caching is managed separately, often involving SSD-based caches.

Nutanix Support case priority levels are defined as follows:

P1 (Critical):The system is down or severely impacted, requiring immediate attention.

P2 (High):The system is available but experiencing issues that directly impact productivity or operations.

P3 (Medium):The system is functioning, but there are non-critical issues or questions.

P4 (Low):General questions or requests that do not impact system performance.

The scenario described matchesP2, where the system is available but productivity is directly affected by the issue.

The correct answer isA. br0.

InAHV (Acropolis Hypervisor),br0is thedefault native Linux bridgecreated on each hypervisor host. It is used for VM traffic and external communication. AHV leveragesOpen vSwitch (OVS)to manage virtual networking, but the bridge is exposed as br0 in the host's network configuration.

Key points:

br0connects VM virtual NICs (vNICs) to the physical network via the host's uplinks.

It is pre-configured during Foundation or cluster deployment.

virbr0is typical in KVM environments but isnot usedin AHV.

Official Reference:

Nutanix AHV Networking Guide

Nutanix KB #2027 – AHV Host Networking

Excerpt: “AHV uses br0 as the default bridge on the host, configured by Open vSwitch for guest VM networking.”

Answer: A

Nutanix AHV (Acropolis Hypervisor) supports integrated IP address management (IPAM) as a built-in feature. IPAM allows administrators to dynamically allocate and manage IP addresses for VMs within a network segment. This functionality simplifies network management by automating the assignment of IPs without relying on external DHCP servers.

A. ESXi:Incorrect, as ESXi does not include built-in IPAM.

B. Hyper-V:Incorrect, as Hyper-V lacks integrated IPAM functionality.

C. AHV:Correct, as AHV has built-in IPAM for automated IP address allocation.

D. XenServer:Incorrect, as XenServer does not support integrated IPAM.