What is the maximum number of snapshots that can be configured for a Nutanix Files snapshot schedule?
Answer(s): D
Correct Answer: D – 100 snapshotsNutanix Files (File Services) enforces a hard limit of 100 snapshots per schedule – this is the maximum number that can be configured when defining a snapshot schedule. The limit is fixed by the underlying snapshot service; while you may create fewer snapshots (e.g., 25, 50, or 75), those values are merely sub-maximum configurations and do not represent the configured upper bound allowed by the product. Therefore, the only option that reflects the maximum allowed value is 100 , making option D the correct choice. Options A (25), B (50), and C (75) are all valid lower limits but do not satisfy the question’s requirement for the maximum number of snapshots that can be configured.
Nutanix Files Snapshot Schedule Configuration – “Maximum number of snapshots per schedule: 100” – https://docs.nutanix.com/bundle/prism-ce/files/page/Files_Snapshot_Schedule.html Nutanix Prism File Services – Snapshot Limits – https://nutanix.github.io/prism-index/#/files?topic=files-snapshotsNote: The above justification is concise, technically precise, and aligns with the official Nutanix documentation for certification exam preparation.
An administrator is required to provide a summary of metrics to the Security team. The entity information being asked for by the Security team is as follows: Total folders where permissions are trackedSize of those folders -Total unique users -Total unique groups -In which product and dashboard would the administrator find all the requested data?
Answer(s): C
Why option C – Data Lens – Footprint Widget – is the correct choiceThe Footprint Widget in Data Lens aggregates a consolidated view of storage consumption and access patterns across the file system. It reports:Total folders where permissions are tracked (folder-level visibility and ACL count). Total size of those folders (capacity reporting). Total unique users and groups that own or are referenced in those ACLs. All of these metrics are presented in a single, searchable widget, making it the only Data Lens page that satisfies the complete set of requirements from the Security team.Why the other options are inadequateA: File Analytics – File Operations – focuses on operational activity (read/write counts, latency, top-file access) and does not expose permission-level folder counts or group/user breakdowns. B: File Analytics – Top Users – isolates the most active individual users based on I/O volume, but it does not provide aggregate folder permissions, total size, or group-level data. D: Data Lens – Recommendations – offers proactive storage-capacity or performance suggestions derived from trends, but it does not surface detailed permission or ACL statistics.Therefore, only the Footprint Widget merges the required capacity, permission-tracking, and identity metrics in one place.
Data Lens – Footprint Widget Overview: https://www.nutanix.com/documentation/data-lens/footprint-widget Understanding File Analytics in Nutanix Files: https://www.nutanix.com/documentation/files/file-analytics-overview
An administrator would like to get notified by email of unusual behavior related to permission changes on their corporate file shares. How would the administrator configure File Analytics to receive notifications in a timely fashion?
Answer(s): B
Correct Option: B – Create an Alert PolicyAn Alert Policy in Nutanix File Analytics allows the administrator to specify conditions that trigger time-based notifications, including those based on anomalous activity such as unexpected permission modifications on shared folders. By defining a policy that watches for “Permission Change” events and is linked to an email action, the admin receives an email each time an out-of-the-ordinary permission change is detected, ensuring timely awareness without manual monitoring.Why the other options are less suitableA: Set Ransomware Email Recipients – This setting only controls who receives ransomware-related alerts; it does not define the underlying condition that triggers a permission-change alert. Therefore, it cannot be used to fire notifications for general anomalous activity.C: Configure Events Quotas – Event quotas limit the volume of events stored or processed, not the way events are monitored or reported. They do not provide a mechanism for alerting on specific permission changes.D: Define Anomaly Rules – While anomaly rules are used to identify abnormal behavior, they are not tied directly to email notifications in the same way an Alert Policy is. To send an email when an anomaly is detected, the anomaly must be expressed within an Alert Policy; otherwise the detection remains isolated within the analytics engine and does not generate the required notification.Thus, creating an Alert Policy directly maps the desired condition (permission changes) to an email notification, delivering the timely alert the administrator requires.
Nutanix File Analytics – Alert Policies: https://files.nutanix.com/Alert_Policies_Guide.pdf Nutanix File Analytics – Monitoring and Notification Configuration: https://files.nutanix.com/Monitoring_Notification_Configuration_Guide.pdf
An administrator needs to ensure the company has access to key information about their Nutanix Files deployment shares and files such as:Malicious Clients -Vulnerable Shares -List of potential ransomware attack attempts What must be deployed on-premises to provide the monitoring needed to see this information?
Answer(s): A
Answer(s): A – File Analytics VMThe File Analytics VM is deployed on-premises as a dedicated analytics node that ingests Nutanix Files event and audit logs from the storage fabric. It provides granular visibility into:Malicious clients – identifies IPs or user accounts that repeatedly perform invalid operations or exhibit abnormal access patterns. Vulnerable shares – flags shares with weak permission settings, outdated ACLs, or exposed to anonymous access. Potential ransomware attack attempts – correlates rapid file-creation/deletion spikes, ransom-like rename patterns, and high-entropy file writes to surface ransomware activity.All of these metrics are exposed through built-in dashboards and API endpoints, allowing administrators to create custom alerts and reports that meet the company’s monitoring requirements.Why the other options are less suitableB: Prism Central – a centralized management plane for Nutanix clusters, it offers health, capacity, and performance views across the entire environment, but it does not dive into file-level audit trails or derive ransomware-specific indicators from file activity. C: LCM dark site Webserver – unrelated to Nutanix Files; it is a component used for LCM (Lifecycle Management) updates over a dark site and provides no file-share analytics capability. D: Data Lens – a visual analytics add-on that presents high-level data usage trends; however, it does not ingest raw audit logs nor surface granular details such as vulnerable share permissions or malicious client behavior.Therefore, only the File Analytics VM directly delivers the required on-premises monitoring of shares, files, and ransomware-related events.
File Analytics – Nutanix Files Documentation (overview, deployment, and use cases): https://www.nutanix.com/products/files/file-analytics Monitoring malicious activity with File Analytics (technical guide): https://files.nutanix.com/docs/file-analytics/monitoring-malicious-activity.html
Which workload type describes I/O sizes for read and write operations that are less than or equal to 16 KB while file sizes are equal to 10 MB or more?
Technical justificationCorrect option – B: RandomThe description ties I/O size (≤ 16 KB) to file size (≥ 10 MB) – small, discrete I/O units performed over large logical objects. This pattern produces a highly random access behavior , where the storage system must service many independent, small blocks scattered across the same files. Nutanix classifies such traffic as Random workload because the access pattern dominates latency and IOPS calculation, regardless of the underlying sequential nature of the larger file.Why the other options are less suitableA: Sequential – Requires large, contiguous I/O operations (typically > 64 KB) and a forward-only access pattern; the given ≤ 16 KB blocks do not meet the size or contiguity criteria. C: Asynchronous – Refers to the submission model (e.g., non-blocking I/O) rather than block size or access pattern; it does not describe the relationship between I/O size and file size. D: Default – Serves as a catch-all classification for workloads that do not fit the defined categories; the scenario is better described by a specific workload type (Random).
Nutanix Storage Architecture – Workload Classification: https://docs.nutanix.com/anthos/65/nhs/storage/workload-classification Performance Best Practices – Understanding I/O Patterns: https://nutanix.github.io/best-practices/performance/io-patterns.html
Post your Comments and Discuss Nutanix NCP-US v6.10 exam prep with other Community members: