When naming an Object Store instance, which two naming rules must be followed? (Choose two.)
Answer(s): A,C
Correct options: A and CA – Uniqueness across the platform Every object-store instance must have a globally unique name within the Nutanix environment. Re-using a name would cause conflicts during creation, deletion, or metadata lookup, leading to unpredictable behavior and operation failures. Enforcing uniqueness guarantees that each instance can be addressed unambiguously by APIs, CLI commands, and the cluster’s internal name-resolution tables.C – Naming pattern (letter-start / letter/number-end) The name must begin with an alphabetic character and may contain letters, digits, or hyphens thereafter, but the final character must be either a letter or a digit. This rule prevents invalid DNS-style identifiers and ensures that the name can be safely used in URL paths, API endpoints, and external integrations that expect a conventional identifier format.Why B is not required The length constraint is not limited to a strict 3-to-32-character range; the official guideline allows up to 128 characters for the identifier. Therefore the “minimum three and maximum thirty-two” bound is inaccurate and would incorrectly disqualify longer, valid names.Why D is not required The name does not have to start with a digit. Starting with a number violates the pattern defined by the platform’s naming syntax, which mandates an alphabetic start. Consequently, option D contradicts the documented naming rule.
Nutanix Objects Naming Rules – Documentation detailing the uniqueness requirement and allowed character set. https://portal.nutanix.com/page/ruby/public-pubs/professional-services/objects-naming-rules.pdfNutanix Objects – Naming Conventions and Limits – Official guide confirming maximum length of 128 characters and the alphabetic-end rule. https://docs.nutanix.com/protege/objects-naming-conventions
Refer to the exhibit.In the exhibit, what does "AIXforyou@123" represent?
Answer(s): A
An administrator needs to configure Nutanix Objects in AHV. Which IP range must be available for this task?
Answer(s): B
Why option B is the correct choiceNutanix Objects (the object-storage service that runs on top of AHV) requires its own dedicated IP subnet(s) that are reserved for internal storage traffic and for the object-service API. By default the platform expects two non-overlapping /16 pools: 10.100.0.0/16 for the primary storage-network and 10.200.0.0/16 for secondary services such as replication and client access. These pools are referenced throughout the Nutanix networking documentation and are the only ranges the installer automatically creates when you enable the “Objects” service. The chosen range must be available, routable, and isolated from other cluster networks (guest VMs, management, and replication). Using a single /24 or a different private block (e.g., 192.168.x.x) would not provide the address space or the separation required by the object service and could cause IP conflicts or loss of visibility.Why the other options are not suitableA – 10.100.1.0/24 – A /24 mask only affords 251 usable addresses, far too few for a production-grade object network and does not match the default Nutanix-reserved /16 pool. C – 172.100.0.0/16 and 172.200.0.0/16 – These subnets use the 172.x.x.x private range, which is not the standard Nutanix reserve for Objects. The platform expects 10.x.x.x addresses for this purpose; using 172.x.x.x would require manual re-configuration and could break default DNS/service discovery. D – 192.168.1.0/24 – Again, a single /24 is insufficient, and 192.168.x.x subnets are commonly used for other admin networks; they do not align with the pre-configured Nutanix storage IP ranges and would need to be manually overridden in multiple places.Bottom line: The only answer that reflects the exact IP blocks Nutanix reserves for Objects on AHV – 10.100.0.0/16 and 10.200.0.0/16 – is option B .
Nutanix Objects Overview – Network Requirements: https://portal.nutanix.com/page/products-and-solutions/nutanix-objects#network AHV Networking Configuration Guide – Storage Network: https://docs.nutanix.com/technologies/hyperconverged-infrastructure/hci/ahv-networking#storage-network
An administrator wants to create a write-once, read-many (WORM) with a 60 minute duration that the file needs to be unmodified before Nutanix Files commits it to the WORM state. What is this delay time called?
JustificationThe delay that must elapse with no modification of a file before Nutanix Files commits it to a WORM state is defined as the Cool-Off Interval . This interval is a configurable timer that starts after the file is placed in “Pending-WORM” and must expire before the object becomes immutable. It is not the same as a Retention Period, which merely specifies the total duration an object remains immutable; the Cool-Off Interval is the pre-commit waiting period. “Quarantine” refers to a protective hold on a deleted object, and “Locked State” describes the final immutable condition rather than the waiting timer itself.Therefore the correct answer is: A: Cool Off Interval.
Nutanix Files WORM Configuration – Cool-Off Interval: https://docs.nutanix.com/pedestal/6.10/working-with-files/worm-config.html Nutanix Files Retention & WORM Concepts: https://docs.nutanix.com/pedestal/6.10/working-with-files/retention.html
An administrator has files located in shares, buckets and volumes. In which environment can File Analytics be used to collect metadata?
Answer(s): C
Why option C (AD authenticated SMB) is correctFile Analytics is designed to ingest metadata from file-based services that expose POSIX/SMB attributes and support identity mapping. SMB shares that are AD-authenticated expose user- and group-level security identifiers, ACLs, and file-level timestamps – exactly the data File Analytics needs for its collection pipeline. Nutanix Files integrates natively with Active Directory; when a share is configured with AD credentials, the metadata stream contains the necessary identity and permission information for analytics to consume.Why the other options are unsuitableA – Kerberos-authenticated NFS v4.0 – NFS presents a POSIX-centric view, but Nutanix File’s analytics engine does not ingest NFS metadata; NFS does not use AD identities and the metadata schema is not aligned with File Analytics’ ingestion model. B – Kerberos-authenticated S3 – S3 is an object-storage API; it lacks the hierarchical POSIX metadata (e.g., file ACLs, ownership) required by File Analytics. Authentication via Kerberos does not expose the granular file-level attributes needed for analytics. D – CHAP-authenticated iSCSI – iSCSI is a block-storage protocol. It transmits only block-level identifiers and does not provide any file-level metadata such as filenames, timestamps, or Windows ACLs, so there is nothing for File Analytics to collect.Conclusion File Analytics can only collect the rich file metadata it requires when the underlying file service is AD-authenticated SMB , making option C the only viable environment.
Nutanix Files Analytics Overview – https://docs.nutanix.com/books/Finale/pages/Files-Analytics.html Configuring AD Authentication for SMB Shares – https://docs.nutanix.com/calm/latest/reference/files-configuration/smb-authentication.html
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.