Nutanix Certified Professional - Unified Storage v6.10 (NCP-US_V6.10)

If an Objects Service upgrade previously failed, the service likely remains unstable or inconsistent. Objects Manager disables further upgrade options to prevent compounding issues until the underlying service's health is restored, as it's a critical dependency.
* Option A is incorrect: Access keys are for S3 client authentication, not for managing or upgrading the Objects Manager software. Incorrect keys do not disable upgrade functionality.
* Option B is incorrect: The Objects browser is a GUI component for data access. Its availability does not directly control the core Objects Manager service's upgrade capability.
* Option C is incorrect: A previously failed Prism Element upgrade is not the most direct reason to disable the Objects Manager upgrade option. Objects Service health is a more immediate dependency.

When enabling Nutanix Volumes for iSCSI block storage, a dedicated IP address is required for the iSCSI data services. This IP, labeled as 'iSCSI Data Service IP' in the exhibit, serves as the target for iSCSI initiators from client hosts, allowing them to connect to the Nutanix cluster for storage access. Without this IP, the iSCSI service cannot be configured or become functional.
The Virtual IP is for cluster management, not iSCSI data. Virtual IPv6 is optional unless specifically required. FQDN is for name resolution but not fundamentally required for the iSCSI service to operate.

✅ Option B (Correct)

Reasoning: When Data Lens analytics stops collecting data on an object store, the most direct and effective troubleshooting step is to disable and then re-enable the analytics feature for that specific object store. This action re-initializes the Data Lens service's connection and data collection processes, resolving potential stalls or configuration glitches. This is a standard operational procedure to refresh a service's state.

❌ Why the other choices are incorrect:

• Option A is incorrect: IAM permissions primarily control access to the object store and its data. While necessary, simply removing and re-adding them is unlikely to resolve a Data Lens collection issue, especially if data access itself isn't the problem.
• Option C is incorrect: Versioning manages object revisions within a bucket. It is not directly related to Data Lens's ability to collect and process analytics data about the object store's usage and metadata.
• Option D is incorrect: Renaming a bucket is a disruptive operation that would break existing configurations and access paths. It would not resume analytics functionality and would likely cause more issues.

Option D (Correct)

Reasoning: Nutanix Files snapshot schedules permit configuring a retention policy. Each schedule can retain a maximum of 100 snapshots, offering flexibility for recovery points while efficiently managing storage.

Why the other choices are incorrect:

• Option A is incorrect: 25 is below the documented maximum limit.
• Option B is incorrect: 50 is below the documented maximum limit.
• Option C is incorrect: 75 is below the documented maximum limit.

✅

Option C (Correct)

Reasoning: Nutanix Data Lens, specifically its Footprint widget, provides a comprehensive overview of unstructured data across registered file servers. This dashboard directly presents metrics such as total folders (where permissions are implicitly tracked for managed shares), their size, total unique users, and total unique groups, precisely matching the Security team's requested entity information.

❌ Why the other choices are incorrect:

• Option A is incorrect: File Analytics - File Operations focuses on real-time and historical file access events and activities, not aggregated summaries of total folders, users, or groups.
• Option B is incorrect: File Analytics - Top Users provides insights into user activity patterns and data consumption, not a summary of overall folder count, size, or unique groups.
• Option D is incorrect: Data Lens - Recommendations offers actionable insights and suggestions based on data analysis (e.g., stale data, open shares), rather than presenting a consolidated summary of current data footprint metrics.

✅ Option B (Correct) Reasoning: In Nutanix File Analytics, an administrator configures Alert Policies to monitor for specific events, including unusual behavior like permission changes. These policies define conditions and actions, such as sending email notifications, ensuring timely communication about security-relevant activities.
❌ Why the other choices are incorrect:

• Option A is incorrect: Ransomware Email Recipients are specifically for notifications related to ransomware detection, not general permission change anomalies.
• Option C is incorrect: Configure Events Quotas manage the number of events processed or stored, not the mechanism for sending notifications about unusual behavior.
• Option D is incorrect: Defining Anomaly Rules identifies unusual patterns, but an Alert Policy is then required to trigger notifications when these anomalies are detected.

• Option B is incorrect: Prism Central is a management plane for Nutanix clusters; it does not inherently provide file-level analytics for security threats like ransomware or vulnerable shares. It manages components like File Analytics but doesn't perform the analysis itself.
• Option C is incorrect: LCM dark site Webserver is used for managing software updates in air-gapped environments. It has no function related to file security monitoring or analytics.
• Option D is incorrect: Nutanix Data Lens is a cloud-based SaaS offering that provides global visibility and analytics for Nutanix Files. The question specifically asks what must be deployed on-premises.

✅ Option B (Correct)

Reasoning: Workloads with I/O sizes less than or equal to 16 KB are characteristic of small-block I/O. These small I/O operations, even when performed on large files (10 MB or more), typically access non-contiguous data blocks, defining a random access pattern. Common examples include OLTP databases and VDI environments.

❌ Why the other choices are incorrect:

• Option A is incorrect: Sequential workloads typically involve large block I/O (e.g., 64 KB or more) to read or write contiguous data for high throughput, which contradicts the specified small I/O size.
• Option C is incorrect: Asynchronous describes an I/O method (non-blocking) rather than the data access pattern (sequential or random). It's not a workload type in this context.
• Option D is incorrect: "Default" is not a specific workload type characterized by I/O patterns. Workloads are categorized by their observed I/O behaviors.