An administrator is implementing two production networks for Nutanix Objects: Objects Storage Network (internal) Objects Public Network (external) In which two ways is it recommended the administrator configure these networks? (Choose two.)
Answer(s): B,C
Why the correct choices (B and C) are optimalB – Placing the Objects Storage Network (OSN) on a separate subnet from the Controller VM isolates storage traffic, preventing CVM-hosted services from contending with data-plane traffic and simplifying QoS/traffic-shaping policies. C – Keeping the OSN and the Objects Public Network (OPN) on distinct virtual networks guarantees logical separation of internal and external storage traffic, which enhances security (different ACLs, VLANs, or firewalls) and avoids broadcast-domain overlap that could cause ARP or routing conflicts.Why the remaining options are less suitableA – Converging the OSN onto the same network as the CVM shares the same broadcast domain and can expose storage traffic to CVM management processes, increasing latency spikes and reducing fault isolation. D – Using the same virtual network for both OSN and OPN merges internal and external storage traffic, making it difficult to enforce separate security zones and potentially exposing internal objects to internet-facing workloads.
Nutanix Architecture Overview – “Network Design Best Practices” Nutanix Xi Leap Deployment Guide – Chapter 4, “Objects Storage Network Configuration”
Technical requirements within an organization dictate the need for a common naming system across multiple Nutanix Objects instances for a particular application use case. Which Nutanix Objects feature should an administrator leverage to ensure compliance with this naming requirement?
Answer(s): D
Answer: D – Federated NamespaceA federated namespace allows a single, unified naming hierarchy to be shared across multiple Nutanix Objects instances or clusters. By defining a common namespace prefix, an administrator can ensure that all objects created for the application are addressed with the same logical name, regardless of which underlying cluster or bucket they reside in. This directly satisfies the organization’s requirement for a consistent naming scheme and simplifies policy, access, and monitoring across the distributed environment.Why it is the best choiceProvides a single logical namespace that spans multiple objects instances. Enforces naming consistency through configurable prefixes and shared root paths. Enables centralized administration of access controls, quotas, and metadata without needing separate naming conventions per cluster.Why the other options are less suitableA: Multicluster – Primarily a management abstraction for operating many clusters; it does not inherently enforce a common object-level naming scheme. B: Streaming Replication – Used for asynchronous data protection and disaster recovery; it copies data but does not address naming or namespace uniformity. C: Cloud Tiering – Moves data between storage tiers or to external object stores; it focuses on data placement, not on creating a coherent naming structure across clusters.Implementing a federated namespace is the recommended approach to meet the naming compliance requirement in a Nutanix environment.
Nutanix Objects – Federated Namespace Overview: https://docs.nutanix.com/extend/reference/federated-namespace/overview Nutanix Objects Documentation – Managing Namespaces: https://docs.nutanix.com/extend/reference/federated-namespace/manage-namespace
An administrator needs to recover a previous version of a file or share. Which Nutanix Files feature should the administrator enable to allow this?
Answer(s): C
Solution: Enable Self-Service Restore .Why it’s best – Self-Service Restore is the built-in feature of Nutanix Files that lets end users or administrators browse previous filesystem snapshots and restore individual files or shares without involving the IT team. It directly satisfies the requirement to recover a previous version of a file or share. Why the other options don’t fitProtection Policies – Define retention and scheduling for snapshots but do not provide a UI for users to pick and restore specific previous versions. Snapshot – Snapshots are the underlying mechanism that creates point-in-time copies, but they must be exposed through Self-Service Restore to be usable for file-level recovery. Data Protection – Refers to broader backup/replication strategies (e.g., protection groups) and is not intended for ad-hoc, per-file restoration.Result: Enabling Self-Service Restore makes previous file versions accessible for users to retrieve on demand, which is the only feature that directly addresses the stated need.
Nutanix Files – Self-Service Restore Overview: https://docs.nutanix.com/frames/acropolis-files/self-service-restore.html Nutanix Files – Managing Snapshots and Restores: https://docs.nutanix.com/frames/acropolis-files/snapshots.html
An administrator is tasked with creating a Grandfather-father-son backup rotation scheme. Backups retention is set and maintained by the third party backup software. The primary backup is written by third-party backup software to Nutanix Objects WORM enabled bucket, and second and third copies should be written to two different offsite locations. A second copy should also be written to a Nutanix Objects instance on a different cluster, and a third copy to an AWS S3 bucket. What should the administrator do to satisfy the configuration requirements?
Technical justificationThe Grandfather-Father-Son rotation requires three distinct copies: 1 ⃣ Primary copy stays in the source Nutanix Objects bucket (WORM). 2 ⃣ A replica must be written to a Nutanix Objects bucket on a different cluster (inter-cluster replication). 3 ⃣ The final copy must be archived to an off-site AWS S3 bucket.Lifecycle rules in Nutanix Objects can be configured to tier data to external storage (e.g., AWS S3) and replicate data to another Nutanix cluster.Using a rule that enables replication for the Nutanix Objects instance satisfies the requirement to place a second copy on a separate cluster.Enabling tiering for AWS S3 moves the data from the on-premises bucket to the S3 bucket, providing the third off-site copy required for the rotation scheme.Why option D is correctReplication is applied to the Nutanix Objects bucket (second copy on a different cluster). Tiering is applied to AWS S3 (third copy in the cloud). This combination directly matches the retention and placement rules of a GFS scheme.Why the other options are unsuitableA & B – Attempt to replicate to AWS S3, which is not a supported replication target; S3 can only be a tiering destination, not a replication endpoint. C – Uses tiering for both AWS S3 and the Nutanix bucket, but fails to provide the required inter-cluster replication for the second copy.
Nutanix Prism Object Storage – Lifecycle Policies: https://portal.nutanix.com/page+portal/api-nc2012/v2/docs/Prism-Object-Storage-Administration-Guide Replicating Buckets Across Clusters: https://docs.nutanix.com/ahrs/web/aos/6-10/ahsv610_object_storage.html#replicating-buckets-across-clusters
An administrator is managing two Nutanix clusters that are both hosting Nutanix Files instances. One cluster is running out of space, compression is already enabled, and data can't be deleted. Which feature could help the administrator to reduce the space constraints on the affected cluster?
Correct answer: D – Smart TieringTechnical justificationSmart Tiering automatically moves cold or infrequently accessed blocks to lower-cost storage tiers (e.g., from All-Flash to Capacity-Optimized) while keeping the data accessible through the same namespace. It operates at the block level, so it can reclaim space even when the dataset is “locked” (e.g., no deletable snapshots or immutable objects). Because compression is already in place and cannot be increased further, tiering offers an additional compression/rehydration path that reduces the effective footprint without requiring data deletion. The feature is transparent to applications and can be applied to an individual Nutanix Files instance, making it the only option that directly alleviates storage pressure under the described constraints.Why the other options are unsuitableA: Object Replication – Replicates data to a remote cluster, increasing overall storage usage rather than freeing space on the source cluster; it does not compress or tier existing data locally. B: Smart Sync – Provides cloud-based tiering to an external object store, but requires a configured sync destination and is not intended for immediate on-premises space reclamation within the same cluster. C: Smart DR – Focuses on disaster-recovery orchestration and data protection; it does not address intra-cluster capacity limitations.Therefore, Smart Tiering is the only feature that can dynamically reduce the on-cluster storage footprint without needing to delete data or modify existing replication configurations.
1. Nutanix Prism User Guide – Smart Tiering: https://docs.nutanix.com/acropolis/nutanix-files/smart-tiering 2. Nutanix Files Administration – Managing Storage Tiers: https://frames.ntnx.com/Frames/Foxtrot/web 辦公室 /nutanix-files-admin/smart-tiering
Post your Comments and Discuss Nutanix NCP-US v6.10 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the NCP-US v6.10 content, but please register or login to continue.