Nutanix NCP-US-6.5 Exam With Confidence Using Practice Dumps

Nutanix Files provides a built-in ransomware prevention feature that allows administrators to block malicious file signatures from being written to the file system. However, this feature has a limit of 300 signatures per share or export. If the list of malicious file signatures to block is greater than 300, a third-party solution is recommended2

Neither File Analytics nor Data Lens supports signature-based ransomware prevention with a large list of malicious file signatures (300+). Signature-based blocking requires a dedicated security solution with a robust signature database, which third-party tools are designed to handle. Nutanix Files supports integration with such tools, making a third-party solution the best choice for this requirement.

Exact Extract from Nutanix Documentation:

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“For advanced ransomware prevention requiring signature-based blocking, such as when the list of malicious file signatures exceeds 300, Nutanix Files supports integration with third-party security solutions. These solutions can handle large signature databases and perform file scanning/blocking at scale, complementing the behavioral detection capabilities of File Analytics and Data Lens.”

The Marketing department needs to recover files in a Nutanix Files share with a recovery window of 14 days. Nutanix Files, part of Nutanix Unified Storage (NUS), supports file recovery through Self-Service Restore (SSR) for SMB shares, which relies on snapshots to provide previous versions of files.

Analysis of Options:

Option A (Change default settings in the Protection Configuration window): Incorrect. The “Protection Configuration window” is not a specific feature in Nutanix Files. This may be a vague reference to snapshot policies, but the correct terminology is Protection Domain or snapshot schedules, as in option B.

Option B (Change the Protection Domain settings to keep at least 14 days of snapshots): Correct. Nutanix Files uses snapshots to enable file recovery via SSR. These snapshots are managed through Protection Domains (or snapshot schedules in newer terminology) in Prism Element or Prism Central. To ensure files can be restored within a 14-day timeframe, the snapshot retention policy must be configured to retain snapshots for at least 14 days.

Option C (Install Nutanix Guest Tools on clients who need to perform Self-Service Restore): Incorrect. Nutanix Guest Tools (NGT) is used for VM management features (e.g., VSS snapshots for backups, VM mobility), but it is not required for Self-Service Restore in Nutanix Files. SSR is a client-side feature for SMB shares that works natively with Windows clients (via the Previous Versions tab) and does not require NGT.

Option D (Enable Self-Service Restore at the share level): Correct. Self-Service Restore (SSR) must be enabled at the share level in Nutanix Files to allow users to recover files without administrator intervention. This feature enables the Marketing department to restore files directly from their Windows clients using the Previous Versions feature, provided snapshots are available (as configured in option B).

Selected Configurations:

B: Configuring the snapshot retention to at least 14 days ensures that previous versions of files are available for recovery within the required timeframe.

D: Enabling SSR at the share level allows the Marketing department to perform the recovery themselves, meeting the requirement for user-driven file recovery.

Exact Extract from Nutanix Documentation:

From the Nutanix Files Administration Guide (available on the Nutanix Portal):

“Self-Service Restore (SSR) allows users to recover previous versions of files in SMB shares. To enable SSR, it must be activated at the share level in the Files Console. SSR relies on snapshots to provide previous versions; ensure that snapshot schedules (via Protection Domains or snapshot policies) are configured to retain snapshots for the desired recovery period, such as 14 days.”

The two minimum resources that are required for deploying Files instances are 8 GiB of memory per host and 4 vCPUs per host. Memory and vCPUs are resources that are allocated to VMs (Virtual Machines) to run applications and processes. Files instances are file server instances (FSIs) that run on FSVMs (File Server VMs) on a Nutanix cluster. FSVMs require at least 8 GiB of memory and 4 vCPUs per host to function properly and provide SMB and NFS access to file shares and exports. The administrator should ensure that there are enough memory and vCPUs available on each host before deploying Files instances. References: Nutanix Files Administration Guide, page 27; Nutanix Files Solution Guide, page 6