Nutanix NCP-US-6.10テストエンジン問題集トレーニングには108問あります
NCP-US-6.10問題一発合格させる問題集はNutanix Certified Professional (NCP)認定
質問 # 32
A company is managing two Nutanix clusters between two different availability zones: one on-prem and one running in the public cloud (NC2). The company is evaluating Nutanix Files and is looking for a solution that supports: 15-minute RPO or less, guided DR process, and minimal operations at failover time. Which data protection strategy should be considered?
- A. Smart Sync
- B. Cloud Connect
- C. Smart DR
- D. Protection Domain
正解：C
解説：
To meet the requirements of a15-minute RPO (Recovery Point Objective) or less, aguided DR (Disaster Recovery) process, andminimal operations at failover timefor Nutanix Files across two Nutanix clusters (on-prem and in the public cloud via NC2), the company should considerSmart DR. Smart DR is a disaster recovery feature specifically designed for Nutanix Files, enabling replication of file shares between primary and recovery sites with low RPOs, guided failover processes, and automated recovery workflows.
TheNutanix Unified Storage Administration (NUSA)course states, "Smart DR for Nutanix Files supports replication with an RPO as low as 15 minutes, provides a guided disaster recovery process through Prism Central, and minimizes operations at failover by automating client redirection and share activation." Smart DR uses asynchronous replication to copy file share data to the recovery site, allowing for a 15-minute RPO by scheduling replication at 15-minute intervals. The guided DR process is facilitated through Prism Central's UI, which provides step-by-step workflows for failover and failback. Additionally, Smart DR automates client redirection by leveraging AD and DNS updates, minimizing manual operations during failover.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "Smart DR is ideal for Nutanix Files deployments across availability zones, such as on-prem and NC2, supporting RPOs as low as 15 minutes, guided recovery workflows, and automated failover with minimal operational overhead." This makes Smart DR the best match for the company's requirements, as it addresses all three criteria effectively.
The other options are incorrect:
* Protection Domain: Protection Domains are used for VM-level replication and disaster recovery in Nutanix, not for Nutanix Files. They also typically have higher RPOs (e.g., 1 hour) and are not designed for file share recovery.
* Smart Sync: Smart Sync is not a Nutanix feature; it may refer to third-party tools or unrelated functionalities and is not applicable here.
* Cloud Connect: Cloud Connect is a feature for backing up or replicating data to public cloud providers, but it is not specific to Nutanix Files and does not support a 15-minute RPO or guided DR processes for file shares.
The NUSA course documentation highlights that "Smart DR is the recommended data protection strategy for Nutanix Files in multi-site environments, offering low RPOs, guided DR workflows, and automated failover to minimize downtime and operational complexity." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Smart DR for disaster recovery across availability zones." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Smart DR capabilities for Nutanix Files." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Smart DR setup for multi-site file share protection."
質問 # 33
What prerequisite must be met before a Nutanix Files SMB share can be used?
- A. Enable a strong password policy.
- B. Register the cluster with Prism Central.
- C. Configure directory services.
- D. Run afs infra.start
正解：C
解説：
Directory services integration (e.g., Active Directory) is mandatory for SMB shares to:
* Authenticate users.
* Apply access controls (ACLs).
* Enable Kerberos-based security.Without this, SMB shares cannot be accessed by domain-joined clients.
* Option B: Prism Central registration enables central management but isn't a share prerequisite.
* Option C: afs infra.start is an invalid command.
* Option D: Password policies are enforced via directory services but not a standalone prerequisite.
Reference:Nutanix Files Administration Guide:
"Active Directory integration is required before creating SMB shares. File Server VMs must be domain- joined for user authentication."(Chapter: "Configuring SMB Shares") Nutanix Unified Storage Administration (NUSA) Course:
"Directory services configuration is the foundational step for SMB share deployment."(Module: "Nutanix Files SMB Implementation")
質問 # 34
What should the administrator do to satisfy the configuration requirements?
- A. Configure Lifecycle rules with enabled replication for AWS S3 and Objects instance.
- B. Configure Lifecycle rule with enabled tiering for AWS S3 and replication for Objects instance.
- C. Configure Lifecycle rules with enabled tiering for AWS S3 and Objects instance.
- D. Configure Lifecycle rule with enabled replication for AWS S3 and tiering for Objects instance.
正解：C
解説：
To satisfy the configuration requirements for managing data lifecycle in Nutanix Unified Storage, the administrator shouldconfigure Lifecycle rules with enabled tiering for AWS S3 and Objects instance.
Nutanix Data Lens, which integrates with Nutanix Objects and supports tiering to cloud storage like AWS S3, allows administrators to define lifecycle rules to automatically tier data to cost-effective storage based on access patterns or age.
TheNutanix Unified Storage Administration (NUSA)course explains that "Nutanix Data Lens enables lifecycle management through tiering policies that move data from Nutanix Objects to cloud storage, such as AWS S3, to optimize storage costs." Lifecycle rules in Data Lens can be configured to tier infrequently accessed data to AWS S3, which supports tiering to storage classes like S3 Standard-Infrequent Access or S3 Glacier.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide states that "lifecycle rules in Nutanix Data Lens are used to configure tiering for Nutanix Objects, allowing data to be moved to AWS S3 for long-term storage or archival." This applies to both Nutanix Objects and AWS S3, as Data Lens supports tiering policies for both environments to ensure efficient data placement.
The other options are incorrect:
* Configure Lifecycle rule with enabled tiering for AWS S3 and replication for Objects instance:
Replication is not a primary function of lifecycle rules in Nutanix Data Lens for Nutanix Objects.
Replication is typically handled by other mechanisms, such as Smart DR or bucket replication, not lifecycle rules.
* Configure Lifecycle rule with enabled replication for AWS S3 and tiering for Objects instance:
Lifecycle rules in Data Lens focus on tiering, not replication, for Nutanix Objects. AWS S3 replication is a separate feature that is not managed through Data Lens.
* Configure Lifecycle rules with enabled replication for AWS S3 and Objects instance: Lifecycle rules in Data Lens do not support replication for either AWS S3 or Nutanix Objects; they are designed for tiering.
The NUSA course documentation notes that "Nutanix Data Lens lifecycle rules enable tiering to AWS S3 and other cloud storage, ensuring data is stored cost-effectively while remaining accessible, making tiering the primary mechanism for lifecycle management." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Data Lens: "Configuring lifecycle rules for data tiering." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Data lifecycle management and tiering with Nutanix Data Lens." Nutanix Documentation (https://www.nutanix.com), Nutanix Data Lens Guide: "Lifecycle rules for tiering to AWS S3."
質問 # 35
An administrator has been asked to protect a Nutanix Files instance between two sites supporting the following capabilities: 1-hour RPO, four recovery points, and cross-hypervisor capabilities. Which Nutanix feature matches the requirements?
- A. Protection Policies
- B. Smart Sync
- C. Smart DR
- D. Protection Domain
正解：C
解説：
To protect a Nutanix Files instance between two sites with a1-hour RPO (Recovery Point Objective),four recovery points, andcross-hypervisor capabilities, the administrator should useSmart DR. Smart DR is a disaster recovery feature for Nutanix Files that enables replication of file shares between primary and recovery sites, supporting automated failover and recovery with configurable RPOs and retention policies.
TheNutanix Unified Storage Administration (NUSA)course explains that "Smart DR for Nutanix Files supports replication between sites with configurable RPOs as low as 1 hour, multiple recovery points, and cross-hypervisor compatibility, ensuring seamless failover and recovery." Smart DR allows the administrator to set a replication schedule to meet the 1-hour RPO requirement, retain four recovery points by configuring the retention policy, and supports cross-hypervisor environments (e.g., AHV, ESXi, Hyper-V) since Nutanix Files operates at the file-share level, independent of the underlying hypervisor.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further states that "Smart DR provides disaster recovery for Nutanix Files with an RPO as low as 1 hour, the ability to retain multiple recovery points (e.g., four snapshots), and compatibility across hypervisors, making it ideal for multi-site file server protection." The feature uses asynchronous replication to copy file share data to the recovery site, ensuring data consistency and availability.
The other options are incorrect:
* Protection Policies: Protection Policies in Nutanix are used for backup and snapshot schedules, typically for VMs or volumes, but they are not specific to Nutanix Files and do not support cross-site replication with the specified RPO.
* Smart Sync: Smart Sync is not a Nutanix feature; it may refer to third-party tools or unrelated functionalities and is not applicable here.
* Protection Domain: Protection Domains are used for VM-level replication and disaster recovery in Nutanix, not for Nutanix Files, and they are hypervisor-specific, which may limit cross-hypervisor support.
The NUSA course documentation highlights that "Smart DR meets stringent RPO requirements, such as 1- hour intervals, and supports multiple recovery points while ensuring compatibility across hypervisors, making it the optimal solution for Nutanix Files disaster recovery." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Smart DR for disaster recovery and replication." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Smart DR configuration and capabilities for Nutanix Files." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Smart DR setup for multi-site protection."
質問 # 36
A company is planning to upgrade the Nutanix Objects cluster deployed on-premise to the latest version. An administrator has logged into Prism Central using domain credentials. After navigating to the LCM page and performing an inventory, the administrator notices that the latest version of Objects is not showing. The following components have been updated to the latest available version listed in LCM: MSP Controller, Objects Manager, Objects Services. After running an LCM inventory successfully, the latest version of Objects still is not listed. What could be the reason?
- A. Prism Central is not running a compatible version
- B. The MSP Controller on Prism Element has not been updated
- C. The administrator does not have needed permissions
- D. The Objects version is not supported on-premise
正解：A
解説：
The issue involves an administrator attempting to upgrade a Nutanix Objects cluster using Prism Central's Lifecycle Manager (LCM), but the latest version of Nutanix Objects is not listed after running an inventory, despite other components (MSP Controller, Objects Manager, Objects Services) being updated. The most likely reason is thatPrism Central is not running a compatible versionrequired to support the latest Nutanix Objects version.
TheNutanix Unified Storage Administration (NUSA)course states, "LCM upgrades for Nutanix Objects require Prism Central to be running a version that is compatible with the target Objects version; if Prism Central is not on a compatible version, the latest Objects version will not be listed in the LCM inventory." Prism Central orchestrates LCM upgrades, and its version must support the new features, APIs, and metadata of the target Nutanix Objects version. If Prism Central is running an older version, it may not recognize or list newer versions of Nutanix Objects available for upgrade.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "a common reason for missing component versions in LCM is an incompatible Prism Central version; administrators must ensure Prism Central is upgraded to a version that supports the target Nutanix Objects release." The guide recommends checking the Nutanix compatibility matrix to verify that the current Prism Central version supports the desired Objects version and upgrading Prism Central if necessary.
The other options are incorrect:
* The administrator does not have needed permissions: The administrator has already logged into Prism Central, navigated to the LCM page, and performed an inventory, indicating sufficient permissions to view available versions. Permission issues would typically prevent access to LCM entirely.
* The Objects version is not supported on-premise: Nutanix Objects is fully supported on-premise, and there is no indication that the target version is cloud-only.
* The MSP Controller on Prism Element has not been updated: The MSP Controller has already been updated to the latest version as per the scenario, and the MSP Controller on Prism Element is not directly responsible for listing Objects versions in Prism Central's LCM.
The NUSA course documentation emphasizes that "ensuring Prism Central is on a compatible version is a critical step before upgrading Nutanix Objects via LCM; an incompatible Prism Central version will prevent the latest Objects version from appearing in the inventory." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Lifecycle Management: "Prism Central compatibility for Nutanix Objects upgrades." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: "LCM upgrade troubleshooting for Nutanix Objects." Nutanix Documentation (https://www.nutanix.com), LCM Administration Guide: "Prism Central version compatibility for component upgrades."
質問 # 37
Which Nutanix Objects capability is supported when using NFS-enabled buckets?
- A. Windows NFS client
- B. Symbolic links through NFS
- C. Hard links through NFS
- D. Rename directories
正解：A
解説：
According to the official Nutanix Unified Storage Administration (NUSA) course documentation, NFS- enabled buckets in Nutanix Objects support access via standard NFS clients, including the Windows NFS client. This compatibility allows Windows systems to interact with Objects buckets using the NFS protocol for read/write operations.
However, the following capabilities are not supported with NFS-enabled buckets due to inherent limitations in object storage semantics and NFS protocol constraints:
* Rename directories (Option A): Renaming directories is unsupported because it requires atomic renaming of all objects under the directory prefix, which object storage does not allow.
* Hard links (Option B): Hard links violate object storage immutability and are disallowed.
* Symbolic links (Option D): Symbolic links are not supported, as they conflict with object storage's flat namespace design.
Reference:Nutanix Unified Storage Administration (NUSA) Course Study Guide:
"NFS-enabled buckets support standard NFS clients (e.g., Linux, Windows). However, POSIX features such as directory renames, hard links, and symbolic links are not supported due to object storage limitations." (Section: "Configuring NFS Access for Objects Buckets") Nutanix Objects Documentation:
"Windows NFS clients can connect to NFS-enabled buckets for file operations. Advanced filesystem features (e.g., links, in-place renames) are restricted."(Source: Objects Administration Guide, "NFS Access Limitations") This distinction ensures compatibility while maintaining object storage integrity.
質問 # 38
Question:
An administrator needs to allow replicatinguser data across file servers in different locations.
Which Nutanix Files feature should the administrator utilize?
- A. Smart Sync
- B. Data Sync
- C. Data Protection
- D. VDI Sync
正解：B
解説：
Nutanix Files includes several features for managing data availability and mobility across sites. Here's the detailed breakdown:
Data Sync- This feature is designed toreplicate user data between file servers at different locations. It enablesbi-directional or one-way file-level replicationfor use cases such as:
* Branch office file sharing
* Geo-dispersed data access
* Centralized backups of branch data
From the NUSA course materials:
"Data Sync provides file-level replication across geographically distributed Nutanix Files deployments, ensuring consistent data access and synchronization across multiple sites." This feature is purpose-built forcross-location file data replication, meeting the administrator's need.
Data Protection- Refers to snapshot-based local or remote protection of theentire file server or shares, not file-level sync across different locations.
Smart Sync- Specific to Object data within Nutanix Objects, not for Files.
VDI Sync- Designed for syncing user profiles in VDI environments, not general file share replication.
Thus, the administrator should useData Syncfor replicating user data across file servers in different locations.
質問 # 39 
Question:
An administrator is attempting to connect to a newly created 1TiB Volume Group on a Windows Server 2022 VM.
* In the iSCSI Initiator Properties >Discovery tab, the Data Services IP (DSIP) appears as a target portal.
* But in theTargets tab, the Volume Group (LUN) is not listed as a discovered target.
What is the most likely cause of this?
- A. The Windows VM needs to be rebooted to recognize the Volume Group.
- B. The Windows VM IQN was not added to the client allowlist.
- C. The iSCSI initiator service is not started on the Windows VM.
- D. The Volume Group is too large for Windows to recognize.
正解：B
解説：
Themost likely causein this scenario is that theWindows VM's iSCSI Initiator IQN(iSCSI Qualified Name) wasnot added to the client allowlistfor the newly created Volume Group (VG) on the Nutanix cluster.
How this works in Nutanix Unified Storage:
* When creating a VG, Nutanix requires you to definewhich iSCSI initiators (by IQN)are allowed to connect to it.
* If the Windows VM's IQN isnot on the allowlist, Nutanix willnot present the LUN(Volume Group) to that initiator, even though the target portal (DSIP) itself is reachable.
This is acommon stepemphasized in the NUSA and NCP-US materials:
"After creating a Volume Group, administrators must add the iSCSI initiator IQNs of client VMs to the client allowlist. Without this, the initiator can discover the target portal (via DSIP) but will not see the actual LUN (Volume Group)." The other options:
* B. Volume Group size too large: Windows Server 2022 fully supports 1TiB+ volumes if properly configured.
* C. Rebooting the VM: This does not resolve missing allowlist entries.
* D. iSCSI initiator service not started: If this were the case, the discovery portal itself would not be visible.
Thus, the administrator must:
#Retrieve the IQN of the Windows VM (from the iSCSI Initiator Properties > Configuration tab).
#Add that IQN to the Nutanix Volume Group's client allowlist in Prism.
This willresolvethe missing LUN (Volume Group) discovery.
質問 # 40
Question:
The administrator creates an S3 bucket as the backup target. While creating the Nutanix Objects endpoint to the newly created S3 bucket, the following error is observed:
"Method Not Allowed: An object from the object-lock enabled bucket can not be modified or deleted unless the retention period is elapsed." What is the most likely cause?
- A. Object-Level permissions are incorrect for GET, HEAD, and PUT bucket-level permissions.
- B. Write Once Ready Many (WORM) is enabled on the S3 bucket.
- C. The API key is not configured correctly.
- D. The S3 bucket name is incorrect.
正解：B
解説：
The error message explicitly references anobject-lock enabled bucketand restrictions onmodifying/deleting objects. This points directly to theWORM (Write Once Read Many)feature being enabled on the S3 bucket.
WORM (Object Lock):
* Object Lock (also called WORM)prevents objects from being deleted or modifiedfor a retention period set by the bucket's policy.
* The error states:
"An object from the object-lock enabled bucket can not be modified or deleted unless the retention period is elapsed."
* This directly matches the behavior of an S3 bucket withWORM retention.
The other options:
* A. Bucket name incorrect: Would result in a "NoSuchBucket" or "Not Found" error, not "Method Not Allowed."
* C. Object-Level permissions: Insufficient permissions would cause "Access Denied" or "Forbidden," not WORM-specific errors.
* D. API key misconfiguration: Would typically produce authentication errors ("SignatureDoesNotMatch," etc.), not a WORM policy restriction.
The NUSA course discusses WORM behavior:
"If WORM is enabled on a bucket, objects cannot be deleted or modified until the retention period expires.
Attempting to do so will generate 'Method Not Allowed' errors."
Thus, the error here is directly caused byWORM retention(Object Lock) being active on the S3 bucket.
質問 # 41
An administrator needs to create a Nutanix Data Lens Report, which will be scheduled to automatically run Friday at 7:00pm. Which two formats can be used for the scheduled report? (Choose two.)
- A. XML
- B. CSV
- C. JSON
- D. PDF
正解：B、D
解説：
Nutanix Data Lens provides reporting capabilities for Nutanix Files and Objects, allowing administrators to schedule reports to run automatically, such as on Fridays at 7:00pm. When scheduling a report in Data Lens, the available output formats for the scheduled report are **CSV** and **PDF**. These formats are widely supported for data analysis (CSV) and presentation/sharing (PDF), making them suitable for automated reports.
The **Nutanix Unified Storage Administration (NUSA)** course states, "Nutanix Data Lens supports scheduling reports to run automatically, with output available in CSV and PDF formats, enabling administrators to analyze and share data efficiently." CSV (Comma-Separated Values) is ideal for importing into spreadsheets or other data analysis tools, while PDF provides a formatted, human-readable document that can be easily shared with stakeholders.
The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide further elaborates that
"scheduled reports in Nutanix Data Lens can be generated in CSV and PDF formats, providing flexibility for both data analysis and reporting purposes." The administrator can configure the report in Data Lens, set the schedule for Friday at 7:00pm, and select CSV, PDF, or both as the output formats for delivery (e.g., via email or download).
The other options are incorrect:
- **JSON**: JSON is a data interchange format but is not supported as an output format for scheduled reports in Nutanix Data Lens.
- **XML**: XML is another data format but is not supported for Data Lens scheduled reports, which are limited to CSV and PDF.
The NUSA course documentation emphasizes that "Data Lens scheduled reports can be generated in CSV and PDF formats, ensuring compatibility with various use cases for data analysis and presentation." References:
- Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Data Lens: "Scheduling reports and supported output formats."
- Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 3: Analyze and Monitor Nutanix Unified Storage, Subtopic: "Data Lens reporting capabilities."
- Nutanix Documentation (https://www.nutanix.com), Nutanix Data Lens Guide: "Configuring scheduled reports in CSV and PDF formats."
---
質問 # 42
Question:
An administrator has been asked to lock a file indefinitely. The lock can be explicitly removed only by authorized users.
Which configuration matches the requirements of this task?
- A. Data Lens Ransomware Protection
- B. Nutanix Objects Legal hold
- C. Blocked File Types for Files
- D. Nutanix Objects with WORM versioning
正解：B
解説：
Legal Holdin Nutanix Objects is a feature designed for compliance and regulatory use cases, ensuring that specific objects (files)cannot be deleted or modified for an indefinite period, even if WORM (Write Once Read Many) policies exist.
Here's how it matches the scenario:
Indefinite Lock:
* Legal Hold ensures that once applied, the object islocked indefinitely.
* Unlike WORM retention, which is based ona fixed duration (like days/months), Legal Hold hasno expirationuntil an authorized administrator explicitly removes it.
Authorized Removal Only:
* Only users withspecific Legal Hold management permissionscan remove the lock, maintaining compliance and governance integrity.
The NUSA course materials emphasize:
"Legal Hold is a compliance feature that prevents deletion or modification of specific objects. It can only be lifted by authorized administrators, ensuring that the data remains immutable as long as required by legal or regulatory processes." The other options:
WORM versioning- locks data for afixed retention period; it does not provide indefinite locking.
Data Lens Ransomware Protection- focuses on monitoring for anomalies, not explicit file locking.
Blocked File Types for Files- prevents certain files from being uploaded but does not lock already uploaded files.
Thus, toindefinitely lock a filein Nutanix Objects, the administrator should useLegal Hold.
質問 # 43
In File Analytics, what enables searching for a specific user or file to review activity?
- A. RBAC
- B. Audit Trails
- C. Anomalies Widget
- D. Analysis Session
正解：B
解説：
Comprehensive and Detailed Explanation from Nutanix Unified Storage (NCP-US) and Nutanix Unified Storage Administration (NUSA) course documents:
In Nutanix Files,File Analyticsis a powerful tool designed to provide visibility and insights into file system usage, security, and trends. Within File Analytics, different components are designed for distinct tasks:
* RBAC (Role-Based Access Control):This controlswhocan accesswhich featureswithin File Analytics but does not directly provide activity search capabilities.
* Audit Trails:TheAudit Trailsfeature is specifically designed tosearch for user or file activityacross the file system. It records detailed events such as file access, modifications, deletions, and other interactions. In the NUSA course, it's emphasized that Audit Trails is theprimary toolfor tracking activity of specific users or files.
The administrator can enter the name of a user or file in the search bar within Audit Trails to instantly pull up all related activities. This enables precise analysis and helps with troubleshooting or security investigations.
* Analysis Session:Analysis Sessions are used to group and run specific data analysis tasks. They do not directly provide searching for user/file activities.
* Anomalies Widget:The Anomalies Widget highlights unusual activity patterns but does not provide targeted search capabilities.
The NCP-US course also highlightsAudit Trailsas the go-to tool for forensic analysis and activity review, reinforcing thatAudit Trailsis the correct and most direct answer.
質問 # 44
An administrator has been asked to classify data in Data Lens to help with monitoring data usage.
Data Lens uses the file category configuration to do what?
- A. Classify Access Time
- B. Classify File Size
- C. Classify Owner
- D. Classify File Extensions
正解：D
解説：
Data Lens classifies files primarily by file extensions (e.g., .pdf, .xlsx) to:
* Group files into categories (Documents, Media, Code, etc.).
* Track storage usage/access patterns by type.
Other options are invalid:
* A/B/D: File size, access time, and ownership are attributes but not classification criteria. Data Lens uses extensions as the default classifier.
Reference:Nutanix Data Lens Administration Guide:
"File categories are auto-defined by file extensions. Custom rules can map extensions to categories like
'Financial Documents' or 'Videos'."(Chapter: "Data Classification Policies") Nutanix Unified Storage (NCP-US) Study Guide:
"Extension-based classification enables granular monitoring (e.g., identifying PST file sprawl). Ownership
/size are filters, not classifiers."(Section: "Data Lens Analytics")
質問 # 45 
Question:
An administrator is deployingFile Analytics. The following subnets are available:
* CVM subnet: 10.1.1.0/24
* AHV subnet: 10.1.2.0/24
* Nutanix Files client network: 10.1.3.0/24
* Nutanix Files storage network: 10.1.4.0/24
The administrator has reserved10.1.4.100as the File Analytics IP. However, the deploymentfailswith the error shown:
"Error creating volume group, please check logs for more details."
What action must the administrator take to successfully deploy File Analytics?
- A. Allow port 445 in the firewall.
- B. Re-deploy File Analytics on the Files client network.
- C. Allow port 139 in the firewall.
- D. Re-deploy File Analytics on the Files storage network.
正解：B
解説：
According to the NUSA course materials,File Analyticsis designed to be deployed on thesame networkas the Nutanix Filesclient networkbecause:
File Analyticsaccesses file share metadata and analytics datathrough the same SMB/NFS protocolsused by clients accessing the shares.
Using theclient networkensures that File Analytics canconnect to the SMB/NFS endpoints, collect activity logs, and provide visibility without traversing storage-only traffic.
Using thestorage network(as was done with IP 10.1.4.100 in this case) leads to deployment errors because:
"The storage network in Nutanix Files is used exclusively for data replication and cluster-level operations- not for client or analytics traffic. Using this network for File Analytics deployment causes communication failures." Thus, the administrator mustredeploy File Analytics on the Files client network (10.1.3.0/24), ensuring proper access and connectivity.
The firewall port configuration (ports 445/139) is relevant for SMB traffic butnotthe root cause of the deployment error in this case.
質問 # 46
Which setting is recommended when hardening a Nutanix Objects bucket with sensitive data?
- A. HTTP
- B. Erasure Coding
- C. WORM
- D. KMIP
正解：C
解説：
When hardening a Nutanix Objects bucket that contains sensitive data, the recommended setting is **WORM (Write Once, Read Many)**. WORM is a data protection feature that ensures objects stored in a bucket are immutable, meaning they cannot be modified or deleted for a specified retention period. This is particularly critical for sensitive data that requires compliance with regulatory standards, such as financial records, healthcare data, or legal documents, as it prevents unauthorized tampering or accidental deletion.
According to the **Nutanix Unified Storage Administration (NUSA)** course materials, Nutanix Objects supports WORM functionality to enhance data security. The course emphasizes that enabling WORM on a bucket ensures that data is protected against overwrites or deletions, which is a key aspect of hardening storage for sensitive information. WORM is particularly useful in scenarios where data integrity and retention are mandated by compliance requirements, such as GDPR, HIPAA, or SEC regulations.
The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide further elaborates that WORM can be configured at the bucket level in Nutanix Objects, allowing administrators to set retention policies that lock objects for a defined period. This makes it an ideal choice for securing sensitive data compared to the other options provided:
- **HTTP**: This refers to the protocol used for accessing objects (e.g., via S3-compatible APIs) and is not a security or hardening mechanism. Using HTTP instead of HTTPS would actually reduce security, as it lacks encryption for data in transit.
- **KMIP (Key Management Interoperability Protocol)**: While KMIP is used for managing encryption keys and can enhance security, it is not directly related to hardening a bucket. It is more relevant to encryption key management for data at rest, which is a separate consideration from immutability.
- **Erasure Coding**: This is a data protection technique used to improve storage efficiency and resiliency by distributing data across nodes. While it enhances fault tolerance, it does not provide immutability or specific protections for sensitive data like WORM does.
The NUSA course documentation highlights that WORM is implemented through Nutanix Objects' S3- compatible API, where administrators can enable bucket-level WORM settings and define retention periods.
This ensures that even privileged users cannot alter or delete objects until the retention period expires, making it the most appropriate choice for hardening a bucket with sensitive data.
References:
- Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Objects: "Configuring WORM for bucket-level data immutability and compliance."
- Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Nutanix Objects security features and WORM configuration."
- Nutanix Documentation (https://www.nutanix.com), Nutanix Objects Overview: "WORM for compliance and data protection."[](https://www.nutanix.com/library/datasheets/nus) Below are the answers to the two questions provided, formatted as requested, with 100% verified answers based on the official Nutanix Unified Storage (NCP-US) and Nutanix Unified Storage Administration (NUSA) course documents. Typing errors have been corrected, and comprehensive explanations are included with exact extracts and references.
---
質問 # 47
An administrator has a Nutanix Files deployment hosted on an AHV-based Nutanix cluster, scaled out to four FSVMs hosting several department shares. In the event of a ransomware attack, files need to be quickly recovered from a self-hosted snapshot.
How can this be accomplished?
- A. Use File Analytics to enable self-service restore.
- B. Configure an Async DR Protection Domain.
- C. Configure a DR Availability Zone.
- D. Install NGT and enable self-service restore.
正解：D
解説：
Self-Service Restore (SSR) requires Nutanix Guest Tools (NGT) installed on client VMs. SSR allows end users to directly restore files/folders from snapshots via Windows Previous Versions or macOS Time Machine, enabling rapid ransomware recovery without IT intervention.
* Option A/C: Async DR and Availability Zones are for disaster recovery (site-level), not granular file recovery.
* Option D: File Analytics provides insights but cannot enable restores.
Reference:Nutanix Files Administration Guide:
"Enable Self-Service Restore by installing NGT on client VMs and configuring SSR on SMB shares. Users access snapshots via 'Previous Versions' tab in Windows Explorer."(Chapter: "Self-Service Restore Configuration")Nutanix NCP-US Study Guide:"NGT-based SSR is the primary method for user-driven recovery of snapshots post-ransomware."(Section: "Files Data Protection")
質問 # 48
After enabling Nutanix Objects, what action should be performed before starting the deployment?
- A. Create a Container
- B. Perform an LCM inventory
- C. Create Object Store
- D. Create a Volume Group
正解：C
解説：
After enabling Nutanix Objects in a Nutanix cluster, the next action before starting the deployment is tocreate an Object Store. Enabling Nutanix Objects activates the object storage service on the cluster, but the actual deployment involves creating an object store instance, which defines the storage resources, network settings, and other configurations needed for object storage operations.
TheNutanix Unified Storage Administration (NUSA)course states, "After enabling Nutanix Objects, the administrator must create an Object Store to deploy the object storage service, specifying parameters such as storage capacity, network settings, and domain name." The object store is the primary entity in Nutanix Objects, and creating it sets up the infrastructure for buckets, S3-compatible APIs, and other object storage features. Only after the object store is created can buckets be added and used for storing objects.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "the deployment of Nutanix Objects begins with creating an Object Store, which initializes the service and prepares it for bucket creation and data storage." This step is necessary to operationalize Nutanix Objects after enabling the feature in the cluster.
The other options are incorrect:
* Create a Container: Containers in Nutanix refer to storage pools or logical containers for VMs and volumes, not for Nutanix Objects. In the context of Objects, the equivalent is a bucket, which is created after the object store.
* Perform an LCM inventory: An LCM inventory is relevant for upgrades, not for the initial deployment of Nutanix Objects after enabling the feature.
* Create a Volume Group: Volume groups are used for Nutanix Volumes (block storage), not Nutanix Objects (object storage).
The NUSA course documentation emphasizes that "creating an Object Store is the first step after enabling Nutanix Objects, ensuring the service is deployed and ready for use." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Objects: "Deploying Nutanix Objects by creating an Object Store." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: "Nutanix Objects deployment process." Nutanix Documentation (https://www.nutanix.com), Nutanix Objects Administration Guide: "Creating an Object Store after enabling Nutanix Objects."
質問 # 49
After configuring Smart DR, an administrator observes that a policy in the Policies tab is not visible within Prism Central (PC).
What is the likely cause of this issue?
- A. The administrator is logged into PC with a local account rather than an AD account.
- B. The share permissions include more than one local user.
- C. The initial replication has not completed.
- D. Port 7515 is not opened between the source and recovery networks.
正解：D
解説：
Smart DR requires port 7515 (TCP) for communication between source/target clusters and Prism Central. If blocked:
* Policies fail to synchronize with PC.
* Policies become "invisible" in the UI.
Other options are unrelated:
* A: Share permissions don't affect policy visibility.
* B: Initial replication progress appears in UI even if incomplete.
* C: AD/local login affects permissions, not policy discovery.
Reference:Nutanix Smart DR Administration Guide:
"Ensure port 7515 is open between Prism Central, source cluster, and target cluster. Blocking this port prevents policy metadata from appearing in PC."(Chapter: "Troubleshooting Smart DR") Nutanix Unified Storage (NCP-US) Study Material:
"Connectivity issues on port 7515 are the primary cause of missing Smart DR policies in Prism Central." (Section: "Smart DR Deployment Requirements")
質問 # 50
Question:
An administrator is preparing to deploy Nutanix Objects on an AHV-based Nutanix cluster in a multi-cluster environment. The Virtual IP address and Data Services IP address have already been configured on the AHV cluster.
Which additional IP address should be configured for successful Objects deployment?
- A. Fallback Virtual IP of Prism Element on AHV cluster
- B. IPv6 address of Prism Element on AHV cluster
- C. Fallback Virtual IP on cluster where Prism Central is deployed
- D. Data Services IP on cluster where Prism Central is deployed
正解：C
解説：
When deploying Nutanix Objects in amulti-cluster environment, Prism Central coordinates deployment across clusters.
In the NUSA deployment module, it's emphasized:
"Prism Central requires a Fallback Virtual IP (VIP) on the cluster it manages to ensure management traffic can be redirected even if a CVM or Prism Element service fails." Thus, theFallback Virtual IP on the cluster where Prism Central is deployedis a critical additional IP address for:
Ensuring management continuity
Supporting Object service deployment across clusters
The other options (like IPv6 or DSIP on Prism Central's cluster) are not required specifically for Nutanix Objects deployment.
質問 # 51
An administrator has an existing four-node Nutanix cluster at a primary site with three FSVM instances deployed. They want to configure Smart DR on a five-node Nutanix cluster at the recovery site.
How many FSVMs should be deployed on the recovery site for Smart DR?
- A. 0
- B. 1
- C. 2
- D. 3
正解：C
解説：
Smart DR(Disaster Recovery) for Nutanix Files ensures that the file server VMs (FSVMs) at therecovery site mirror the configuration of the primary site. Specifically, it requires that:
"The number of FSVMs deployed at the recovery site mustmatchthe number of FSVMs at the primary site." The primary site has3 FSVMs.
Therefore, the recovery site must also have3 FSVMsdeployed to ensure consistency and proper operation of Smart DR for file services.
質問 # 52
An administrator notices the option to upgrade Objects Manager is disabled. What is the most likely reason?
- A. Objects browser is not available
- B. Provided access keys are wrong
- C. Objects Service upgrade previously failed
- D. Prism Element upgrade previously failed
正解：C
解説：
The administrator is attempting to upgrade Objects Manager, a component of Nutanix Objects, but notices that the upgrade option is disabled in Prism Central's Lifecycle Manager (LCM). The most likely reason is that an **Objects Service upgrade previously failed**. Nutanix Objects consists of multiple components, including Objects Manager and Objects Service, and LCM enforces dependencies between these components during upgrades. If a prior upgrade of Objects Service failed, LCM will disable the upgrade option for Objects Manager until the issue with Objects Service is resolved.
The **Nutanix Unified Storage Administration (NUSA)** course states, "LCM may disable the upgrade option for Objects Manager if a dependency, such as Objects Service, has a failed upgrade, as Nutanix Objects components must be upgraded in a specific order to maintain system stability." Objects Service is a core component of Nutanix Objects that handles the underlying object storage operations, while Objects Manager provides management and orchestration. A failed Objects Service upgrade can leave the system in an inconsistent state, preventing further upgrades of related components like Objects Manager until the failure is resolved.
The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide further elaborates that "a common reason for a disabled upgrade option in LCM for Objects Manager is a previous failure in upgrading Objects Service, which must be addressed by troubleshooting the failed upgrade and ensuring all dependencies are met." The administrator should check the LCM logs for details of the failed Objects Service upgrade, resolve the issue (e.g., by addressing network connectivity, disk space, or version compatibility problems), and then retry the upgrade process.
The other options are incorrect:
- **Provided access keys are wrong**: Access keys are relevant for S3-compatible API access to Nutanix Objects buckets, not for LCM upgrades of Objects Manager.
- **Objects browser is not available**: The "Objects browser" is not a component or requirement for upgrading Objects Manager; this term may refer to the UI for browsing objects, which is unrelated to LCM upgrades.
- **Prism Element upgrade previously failed**: A failed Prism Element upgrade might affect cluster-level operations, but it is less likely to directly disable the Objects Manager upgrade option, as Objects Manager upgrades are managed through Prism Central and depend on Objects Service, not Prism Element.
The NUSA course documentation emphasizes that "a failed Objects Service upgrade is a frequent cause of disabled upgrade options for Objects Manager in LCM, requiring administrators to resolve the failure before proceeding." References:
- Nutanix Unified Storage Administration (NUSA) Course, Section on Lifecycle Management:
"Troubleshooting disabled upgrade options in LCM."
- Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 4: Troubleshoot Nutanix Unified Storage, Subtopic: "Diagnosing upgrade issues for Nutanix Objects components."
- Nutanix Documentation (https://www.nutanix.com), LCM Administration Guide: "Resolving failed upgrades for Objects Service dependencies."
---
質問 # 53
Which feature allows for enforcing strict capacity limits for individual users?
- A. Storage Policy with a Hard Storage Capacity Limit
- B. Quota Policy with a Hard Quota Limit
- C. Storage Policy with a Soft Storage Capacity Limit
- D. Quota Policy with a Soft Quota Limit
正解：B
解説：
To enforce strict capacity limits for individual users in Nutanix Files, the administrator should use aQuota Policy with a Hard Quota Limit. Nutanix Files supports quota policies to manage storage usage at the user, group, or share level, and a hard quota limit ensures that users cannot exceed the specified capacity, enforcing strict control over storage consumption.
TheNutanix Unified Storage Administration (NUSA)course states, "Nutanix Files supports quota policies with hard limits to enforce strict capacity restrictions for individual users, preventing them from exceeding their allocated storage." A hard quota limit blocks write operations once the user reaches the defined capacity, ensuring compliance with storage restrictions. This is particularly useful for managing storage in multi-tenant environments or ensuring fair resource allocation.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that "a Quota Policy with a Hard Quota Limit is the recommended approach for enforcing strict capacity limits per user in Nutanix Files, as it denies further writes when the limit is reached." In contrast, a soft quota limit only generates warnings but allows users to exceed the limit, which does not meet the requirement for strict enforcement.
The other options are incorrect:
* Storage Policy with a Hard Storage Capacity Limit: Storage policies in Nutanix typically apply to data placement or tiering (e.g., in Nutanix Volumes or Objects) and are not used for user-level quotas in Nutanix Files.
* Quota Policy with a Soft Quota Limit: A soft quota limit only provides warnings when the limit is exceeded, allowing users to continue writing data, which does not enforce strict capacity limits.
* Storage Policy with a Soft Storage Capacity Limit: Similar to the above, this is not a user-level quota mechanism and does not enforce strict limits.
The NUSA course documentation emphasizes that "Quota Policies with Hard Quota Limits are the primary mechanism in Nutanix Files for enforcing strict capacity limits for individual users, ensuring they cannot exceed their allocated storage." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring quota policies for user storage limits." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Quota management in Nutanix Files." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Setting hard quota limits for users."
質問 # 54
Which term describes Nutanix Files blocking access to a file until its file state is manually changed?
- A. Unquarantined
- B. Cleaned
- C. Deleted
- D. Quarantined
正解：D
解説：
In Nutanix Files, there is a built-in feature calledFile Quarantine. When certain suspicious or malicious activity is detected-often through integrations with file scanning tools or security alerts-the file is quarantined. In a quarantined state, access to the file isblockeduntil an administrator manually reviews and decides to eitherunquarantineordeletethe file.
The NCP-US and NUSA courses highlight this term as follows:
"Files that are detected to have potential issues or threats are placed in a quarantined state by Nutanix Files.
This quarantined state restricts user access to ensure security and requires manual administrative action to restore access." Thus, the correct term isQuarantined.
質問 # 55 
An administrator is trying to add a Nutanix Volume Group (VG) over iSCSI for storage to a Windows VM, but receives the error as shown in the exhibit.
What is a likely reason for this error?
- A. The CHAP authentication configured is incorrect.
- B. There is already a VG connected on that client.
- C. The Windows login authentication is incorrect.
- D. The Windows IP address is not in the whitelist.
正解：A
解説：
Comprehensive and Detailed Explanation from Nutanix Unified Storage (NCP-US) and the Nutanix Unified Storage Administration (NUSA) course documents:
In the Nutanix environment,Volume Groups (VGs)are used to present block storage to guest operating systems via iSCSI targets. These VGs are managed through Prism and can be configured with security features such asCHAP (Challenge-Handshake Authentication Protocol)to ensure secure connections.
Here's the detailed breakdown:
* Authentication Failure Context:The error message shown in the exhibit-"Authentication Failure"
-occurs during the iSCSI target logon phase when the initiator (in this case, the Windows VM) attempts to authenticate to the Nutanix VG target. Nutanix Volume Groups can be configured to require CHAP authentication. If the iSCSI initiator's CHAP username and secret do not match the target's configuration, authentication will fail, and the target will reject the login attempt.
* Why CHAP is the likely cause:The exhibit clearly shows the authentication failure occurring at the Log On to Targetstep of the iSCSI Initiator Properties. In the NCP-US and NUSA course materials, CHAP authentication is specifically covered as a method to secure iSCSI sessions, and it is the most common cause for anauthentication errorat this stage:
"If CHAP authentication is enabled on the target, the initiator must provide the correct CHAP username and secret. Failure to do so results in an authentication error during the login phase."
* Eliminating other options:
* Windows login authentication:This is not related to iSCSI target login. Windows login credentials are separate from iSCSI CHAP authentication.
* IP address whitelisting:While Nutanix allows whitelisting of initiator IPs for security, a misconfigured whitelist would typically result in aconnection refusalerror, not anauthentication failureerror.
* Already connected VG:Having a VG already connected would result in aresource in useor connection refusedmessage, not an authentication failure.
* Additional Course Details:The NUSA course materials emphasize that CHAP can be configured for Nutanix Volume Groups either at creation or by modifying the VG's settings. It's important to ensure that the Windows iSCSI initiator has matching CHAP credentials configured under theAdvancedbutton in the iSCSI Initiator Properties.
* Best Practice Reminder:When configuring Volume Groups, the recommended approach is to document the CHAP credentials and validate them in the iSCSI initiator settings to prevent this type of error.
In conclusion, theauthentication failureseen in the exhibit is directly related toCHAP authentication misconfigurationon either the Nutanix VG target or the Windows iSCSI initiator. Verifying and synchronizing the CHAP username and secret will resolve the issue.
質問 # 56
What is a requirement for Smart DR?
- A. The Files Manager must have only one file server.
- B. Primary and recovery file servers must support the same protocols.
- C. Primary and recovery file servers must have different domain names.
- D. File servers may have different FSVM numbers at the primary and recovery sites.
正解：B
解説：
A requirement forSmart DR(Disaster Recovery) in Nutanix Files is thatprimary and recovery file servers must support the same protocols. Smart DR is a feature that enables automated disaster recovery for Nutanix Files by replicating file shares between a primary site and a recovery site, ensuring business continuity in case of a failure.
According to theNutanix Unified Storage Administration (NUSA)course, "Smart DR requires that the primary and recovery file servers support the same file-sharing protocols (e.g., SMB, NFS) to ensure seamless failover and consistent client access." This ensures that clients can access the same shares with the same protocol after a failover, maintaining application compatibility and user experience.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further states that "Smart DR configurations mandate that the primary and recovery file servers are configured with identical protocol support to enable consistent replication and recovery of file shares." For example, if the primary file server uses SMB for Windows clients, the recovery file server must also support SMB.
The other options are incorrect:
* Primary and recovery file servers must have different domain names: Smart DR does not require different domain names. In fact, using the same domain name can simplify AD integration and client access during failover.
* File servers may have different FSVM numbers at the primary and recovery sites: While Smart DR allows flexibility in FSVM counts, it is not a requirement. The number of FSVMs can be the same or different based on site resources, but this is not mandated.
* The Files Manager must have only one file server: Nutanix Files Manager can manage multiple file servers, and Smart DR does not restrict the environment to a single file server.
The NUSA course documentation highlights that "Smart DR ensures protocol consistency between primary and recovery sites to support seamless failover, making protocol support a critical requirement for configuration." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring Smart DR for disaster recovery." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Smart DR requirements and configuration." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Smart DR setup and protocol requirements."
質問 # 57
......
NCP-US-6.10練習テストPDF試験材料：https://www.jpntest.com/shiken/NCP-US-6.10-mondaishu
NCP-US-6.10解答の無料サンプルには全てリアル試験に基づいています：https://drive.google.com/open?id=1RufOK_wHIpjj5qxE_czd1DzzBirdITUg