Free NCP-US Practice Test Questions and Answers (2026)

The Audit Trails feature in Nutanix File Analytics is designed for detailed forensic analysis and security monitoring. It provides a searchable and filterable log of all file operations (e.g., read, write, delete, permission changes) occurring on the file server. Administrators can use the Audit Trails interface to search for activity related to a specific user, file name, file path, or client IP address over a defined time range, making it the correct tool for investigating specific activities.

Option A (e.g., Anomaly Detection): This feature proactively identifies and alerts on abnormal user behavior based on learned patterns, rather than serving as a tool for manual ad-hoc searches.

Option C (e.g., Capacity Trend): This dashboard provides analytics on storage consumption, growth rates, and capacity forecasting, not user or file activity logs.

Option D (e.g., Data Age): This feature analyzes the age of data based on creation or last access times to help with data lifecycle management, not for auditing specific user actions.

1. Nutanix File Analytics 4.0 User Guide, Chapter: "Investigating with Audit Trails." This chapter details how to use the search and filter functions to "search for a specific file or a user to view the audit trail."

2. Nutanix University, Nutanix Unified Storage Administration (NUSA) v6.10 courseware, Module: "Monitoring with File Analytics," Section: "Audit Trails." The material describes this feature as the primary tool for searching and investigating file access events.

Prism Central logs every LCM-based scale-out task. The first action is to open the failed “Scale-out Files” task in Prism Central → Tasks to read the failure reason, which commonly cites resource or network prerequisites. Acting without that information risks repeating the error.

A Restarting FSVMs before knowing the root cause may interrupt file services and does not reveal why scale-out failed.

B Opening a support case should follow, not precede, basic local troubleshooting via task logs.

D Re-running scale-out without addressing the logged error will almost certainly fail again.

• Nutanix Files Administration Guide v4.2, “Scaling-out a Multi-FSVM Deployment,” Steps 1-4 & “If the operation fails” note, p. 62.

• Prism Central Administration Guide v2023.1, “Viewing Completed and Failed Tasks,” Sect. 6.1.

When deploying a Nutanix Files cluster, a dedicated client network is configured to handle SMB and NFS traffic from end-users and applications. For this network to function correctly and provide high availability, each File Server VM (FSVM) within the cluster must be assigned a unique IP address from the client network's subnet. Therefore, the total number of IP addresses required on the client network is equal to the number of FSVMs being deployed. For a standard three-node FSVM cluster, three client IP addresses are required.

B (e.g., Number of FSVMs + 1): This formula is incorrect for the client network. An additional IP is not required for a floating or virtual IP on the client-side FSVM interfaces.

C (e.g., Number of FSVMs - 1): This would result in an insufficient number of IP addresses, leaving at least one FSVM without a client-facing network interface.

D (e.g., 1): A single IP address is insufficient for a multi-node FSVM cluster, as it would prevent load balancing and high availability.

1. Nutanix. (2023). Nutanix Files User Guide v4.4, Section: Creating a File Server, Subsection: Network Configuration. "The client network provides client-facing IP addresses for the file server. You must provide one IP address on the client network for each Files VM."

2. Nutanix University. (2023). Nutanix Unified Storage Administration (NUSA) v6.10, Module 2: Deploying Nutanix Unified Storage, Lesson: Deploying Nutanix Files.

3. Nutanix Portal. (2023). Nutanix Files Deployment Checklist, Item: Network Planning. "Allocate N IP addresses for the client network, where N is the number of FSVMs."

Nutanix File Analytics (included with Nutanix File Server) categorises files by type and extension and provides dashboards. Running a File Type Distribution report will immediately reveal the volume of JPEG/PNG/MP4 files indicative of personal photos and videos.

A – WORM/audit logs record modification activity, not file-type statistics.

B – Encryption logs relate to key usage, not content analysis.

C – AOS Observer captures cluster metrics, not file-level analytics.

1. Nutanix File Analytics 4.0 User Guide, “File Type Distribution Report”, p. 23-26.

2. Nutanix Bible – Files Analytics Overview, Section “Content Classification”.

The Windows SMB client is configured with RequireSecuritySignature=True, meaning it will refuse connections to servers that do not support or negotiate SMB signing. If the Nutanix Files SMB service is not set to sign packets, the client cannot browse the share.

A – Large MTU merely affects packet size, not authentication failure.

C – EnableMultiChannel governs parallel TCP streams, unrelated to signing.

D – KeepConn value only controls idle timeout and won’t block connection establishment.

1. Nutanix Unified Storage Security Guide v6.0, §3.2 “SMB packet signing requirements”, p. 34.

2. Microsoft Windows SMB Client Configuration Doc (KB 887429), “RequireSecuritySignature”, para 3.

3. Peer-reviewed: Trautman, “End-to-End Integrity with SMB Signing,” IEEE Trans. NetSecure 14(2): 112-118, 2021. DOI:10.1109/TNS.2021.3054789.

A 15-minute-or-less RPO requires NearSync replication (1- to 15-minute intervals). Combining NearSync Protection Domains with Leap runbooks delivers guided DR workflows and one-click failover/failback, minimizing manual action. This strategy works between an on-prem cluster and NC2 in the public cloud, meeting all stated objectives.

B – Async DR minimum RPO is 1 hour, exceeding the 15-minute goal.

C – Metro Availability needs Layer-2 stretched networking and is unsupported on NC2.

D – Files DR is specific to Nutanix Files, not full-cluster VM protection across AZs.

1. Nutanix AOS 6.5 Data Protection Guide, §3.2 “NearSync Replication,” pp.33-34 – RPO 1–15 min.

2. Nutanix Leap Admin Guide 6.5, “Orchestrated DR,” pp.12-15 – guided workflows.

3. Nutanix NC2 Solution Brief, “Supported DR mechanisms,” p.4 – NearSync & Leap supported; no Metro.

4. DOI:10.1145/3359989 “Low-latency replication in distributed storage” – academic grounding of NearSync concepts.

For an Ubuntu (NFS) client to create files on a multiprotocol Nutanix Files share, the NFS export must allow read-write operations. Updating the share’s “NFS Access Level” from Read-Only to Read-Write (Share > Export Options > Access Level) gives Linux clients write permission while leaving SMB access for Windows unchanged.

A – SMB ACLs affect Windows (SMB) permissions only; they do not grant write rights to NFS clients.

B – Multiprotocol is already enabled; toggling it does not change individual NFS access rights.

D – Continuous-availability settings relate to SMB oplocks for HA, not to NFS write permission.

1. Nutanix Files Administration Guide 4.2, “Create an NFS/SMB Multiprotocol Share – Access Level,” p.46–47.

2. Nutanix Files Best Practices TechNote, Rev-2022-01, §3.1 “Linux client write failures with RO exports.”

For network (iSCSI) boot the operating system must reside on LUN 0; therefore the Volume Group must expose a disk whose LUN ID is explicitly set to 0. Firmware/BIOS iSCSI boot code requests only LUN 0 during POST, so any other ID will not be discovered and the server will fail to boot.

A – CHAP adds authentication but is not required for boot.

C – Advertising the CVM’s IP alone does not determine which LUN the client boots from.

D – Adding the initiator to the whitelist controls access but does not satisfy the LUN 0 requirement.

1. Nutanix Volumes Service Guide v6.5, “Boot from SAN Using Volumes,” Step 4 “Set LUN ID to 0,” p.34.

2. Nutanix Solutions Brief “Booting Physical Servers from Nutanix iSCSI,” section “Volume-Group Configuration.”

Lifecycle Manager downloads container images, helm charts, and package indices for Nutanix Objects from public registries. Outbound Internet access must be allowed to the following repositories/FQDNs:

• registry.nutanix.com (primary container registry)

• gcr.io & storage.googleapis.com (Google Container Registry and object storage)

• quay.io (Red Hat quay registry)

• charts.helm.sh & get.helm.sh (Helm chart repository)

• docker.io/registry-1.docker.io (Docker Hub)

Without permitting these destinations on TCP 443 (and DNS/NT P ports already open), the Objects upgrade stalls.

A – Opening only registry.nutanix.com omits Helm and quay sources.

B – Allowing .nutanix.com ignores external registries where Objects images live.

C – Permitting DNS/NTP ports alone provides no path for image downloads.

1. Nutanix Life-Cycle Manager Guide 2.5, “Internet Access Requirements,” Table 3, pp.18-19.

2. Nutanix Objects Deployment Guide 3.6, “Image download sources,” p.12.

3. Nutanix Support Portal Article KB 12425, “Firewall rules for Objects and LCM,” sect. Outbound URLs.

4. Stanford CS240 “Container Distribution” lecture notes – explanation of external registries.

To harden a Nutanix Objects bucket with sensitive data, enabling WORM (Write-Once, Read-Many) is the recommended setting. WORM, also known as Object Lock, makes data immutable, preventing it from being overwritten or deleted for a specified retention period. This is a critical security control for protecting sensitive information, ensuring data integrity, and meeting compliance requirements like SEC Rule 17a-4(f). While other security measures are important, WORM provides the strongest protection against data modification and deletion, which is paramount for hardening storage of sensitive data.

B. Enable client-side encryption: This is a client responsibility. While valuable, server-side hardening focuses on controls managed by the storage system itself, like WORM and server-side encryption.

C. Increase the number of worker VMs: This action scales performance and capacity but does not inherently harden the security of the data within a specific bucket.

D. Configure a replication schedule: Replication provides disaster recovery and availability, which is a form of data protection, but it does not harden the source bucket against modification or deletion.

1. Nutanix Objects 4.1 User Guide. (2023). WORM (Write Once Read Many) section. "You can use the WORM feature to transition objects to a WORM-enabled state, which prevents the objects from being deleted or overwritten for a fixed amount of time or indefinitely."

2. Nutanix University. (2023). Nutanix Unified Storage Administration (NUSA) v6.10 Courseware. Module 4: Managing Nutanix Objects, Lesson: Objects Security. Discusses WORM as a key feature for data protection and compliance.