NCP-US-6.5 Dumps With Exact Questions and Answers

Nutanix Objects, part of Nutanix Unified Storage (NUS), provides S3-compatible object storage. After installing Objects and creating a bucket, the administrator is accessing the bucket via its reference URL (e.g., the S3 endpoint) using an Active Directory (AD) account but cannot write data. This indicates a permissions or configuration issue related to the AD account’s access to the bucket.

Analysis of Options:

Option A (Replace SSL Certificates at the Objects store level): Incorrect. SSL certificates are used for secure communication with the Objects store (e.g., HTTPS access via the reference URL). While an invalid or untrusted certificate might cause connection issues, the administrator can access the bucket (as they are attempting to write), so the issue is not with SSL certificates—it’s with write permissions for the AD account.

Option B (Verify Access Keys for the user): Incorrect. Access Keys (e.g., AWS-style access key and secret key) are used for programmatic access to Nutanix Objects via S3 APIs. However, the question specifies that the administrator is using an AD account, which suggests authentication via AD integration (e.g., SSO or LDAP). In this case, Access Keys are not relevant—permissions are managed through AD user accounts and bucket policies, not S3 Access Keys.

Option C (Verify sharing policies at the bucket level): Correct. Nutanix Objects supports AD integration for user authentication, allowing AD accounts to access buckets. However, bucket access (e.g., read, write) is controlled by sharing policies (or bucket policies) defined at the bucket level. If the AD account cannot write data, the sharing policy likely does not grant write permissions to the user or their AD group. The administrator should verify and update the bucket’s sharing policies in Prism Central to ensure the AD account has write access.

Option D (Reset the Active Directory user password): Incorrect. Resetting the AD user password might resolve authentication issues (e.g., if the password was incorrect), but the question implies the administrator can authenticate and access the bucket (since they are attempting to write). The issue is with write permissions, not authentication, so resetting the password will not resolve the problem.

Why Option C?

When using an AD account to access a Nutanix Objects bucket, permissions are managed through bucket-level sharing policies. The inability to write data indicates that the AD account (or its associated group) lacks write permissions in the bucket’s policy. Verifying and updating the sharing policies in Prism Central to grant write access to the AD account resolves the issue, ensuring the user can write data to the bucket.

Exact Extract from Nutanix Documentation:

From the Nutanix Objects Administration Guide (available on the Nutanix Portal):

“Nutanix Objects supports Active Directory integration for user authentication. Bucket access for AD accounts is controlled by sharing policies at the bucket level. If an AD user cannot write data to a bucket, verify the sharing policies in Prism Central to ensure the user or their AD group has write permissions.”

The appropriate configuration to verify to allow successful Objects cluster deployment to this ESXi cluster is to ensure that vCenter in PE cluster is registered using FQDN (Fully Qualified Domain Name) and that vCenter details in Objects UI are using FQDN. FQDN is a domain name that specifies the exact location of a host in the domain hierarchy. For example, esxi01.nutanix.com is an FQDN for an ESXi host. Using FQDN instead of IP addresses can avoid certificate validation errors when deploying Objects clusters to ESXi clusters. References: Nutanix Objects User Guide, page 9; Nutanix Objects Troubleshooting Guide, page 5

Nutanix Objects, part of Nutanix Unified Storage (NUS), is deployed and managed through Prism Central (PC), which provides a centralized interface for managing multiple Prism Element (PE) clusters. When deploying Objects or adding multi-cluster support to an Object Store, the administrator selects a PE cluster and associated subnets from drop-down lists in the Prism Central UI. If these drop-down lists are empty or show an error, it indicates an issue with visibility or access to the clusters or subnets.

Analysis of Options:

Option A (The logged-in user does not have access to any Prism Central): Correct. Prism Central is required to manage Nutanix Objects deployments and multi-cluster configurations. If the logged-in user does not have access to any Prism Central instance (e.g., due to RBAC restrictions or no PC being deployed), they cannot see any PE clusters or subnets in the UI, as Prism Central is the interface that aggregates this information. This would result in empty drop-down lists for clusters and subnets, as well as during multi-cluster addition for the Object Store.

Option B (The logged-in user does not have access to any subnets on the allowed Prism Central): Incorrect. While subnet access restrictions could prevent subnets from appearing in the Subnets drop-down, this does not explain why the Cluster drop-down is empty or why no clusters are listed during multi-cluster addition. The issue is broader—likely related to Prism Central access itself—rather than subnet-specific permissions.

Option C (The administrator has just created an access policy granting user access to Prism Element): Incorrect. Granting access to Prism Element directly does not affect visibility in Prism Central’s UI. Objects deployment and multi-cluster management are performed through Prism Central, not Prism Element. Even if the user has PE access, they need PC access to see clusters and subnets in the Objects deployment workflow.

Option D (The administrator has just created an access policy denying user access to a subnet in Prism Element): Incorrect. Denying access to a subnet in Prism Element might affect subnet visibility in the Subnets drop-down, but it does not explain the empty Cluster drop-down or the inability to see clusters during multi-cluster addition. Subnet access policies are secondary to the broader issue of Prism Central access.

Why Option A?

The core issue is that Prism Central is required to display PE clusters and subnets in the UI for Objects deployment and multi-cluster management. If the logged-in user does not have access to any Prism Central instance (e.g., they are not assigned the necessary role, such as Prism Central Admin, or no PC is registered), the UI cannot display any clusters or subnets, resulting in empty drop-down lists. This also explains why no clusters are listed during multi-cluster addition for the Object Store, as Prism Central is the central management point for such operations.

Exact Extract from Nutanix Documentation:

From the Nutanix Objects Deployment Guide (available on the Nutanix Portal):

“Nutanix Objects deployment and multi-cluster management are performed through Prism Central. The logged-in user must have access to Prism Central with appropriate permissions (e.g., Prism Central Admin role) to view Prism Element clusters and subnets in the deployment UI. If the user does not have access to Prism Central, the Cluster and Subnets drop-down lists will be empty, and multi-cluster addition will fail to list available clusters.”