NCP-CN Exam Dumps : Nutanix Certified Professional - Cloud Native (NCP-CN-6.10)

For deployments in air-gapped environments where there is no external Internet connectivity, the --airgapped parameter is required. This instructs the NKP deployment to rely solely on internal resources, using pre-staged images and local container registries, ensuring that no external network dependencies cause deployment failures.

The NKPA course details that backup and restore functionality in NKP is provided through integration with Velero, which supports backing up persistent volumes, cluster resources, and application data to S3-compatible storage. This functionality is considered an advanced feature and is included in higher-tier NKP licenses: NKP Ultimate and NKP Pro.

NKP Ultimate: This top-tier license includes all NKP features, such as air-gapped deployments, fleet management, and backup/restore capabilities. It is designed for enterprise-grade environments requiring comprehensive disaster recovery.

NKP Pro: This mid-tier license also includes backup and restore functionality, catering to organizations needing robust data protection but not necessarily all the features of the Ultimate tier (e.g., air-gapped support).

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “Backup and restore functionality, powered by Velero, is available in NKP Pro and NKP Ultimate license tiers, enabling protection of persistent volumes and cluster resources.” These licenses provide the necessary tools and support for configuring Velero with S3-compatible storage, scheduling backups, and performing restores in production environments.

Incorrect Options:

A. NKP Starter: The Starter tier is entry-level and does not include advanced features like backup and restore. It focuses on basic cluster management.

B. NKP Essential: This tier, if it exists in NKP’s licensing model, would be a lower tier and unlikely to include backup/restore functionality, as it is not mentioned in the NKPA course.

The NKPA course covers user authentication for NKP clusters as part of Day 2 operations, emphasizing integration with external identity providers (IdPs) to manage user access securely. NKP uses Dex, an OpenID Connect (OIDC) identity provider, to facilitate authentication by acting as a connector between the Kubernetes cluster and external IdPs, such as LDAP, SAML, or OAuth-based systems.

The course explains that to set up user authentication, a Platform Engineer must configure a Dex connector to the user base’s identity provider. Dex integrates with the Kubernetes API server to enable OIDC-based authentication, allowing users to log in using their IdP credentials. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “NKP supports user authentication through Dex, which provides OIDC integration with external identity providers, enabling single sign-on (SSO) for cluster access.” The process involves deploying Dex as a platform application, configuring the IdP connector (e.g., specifying client IDs, secrets, and endpoints), and updating the Kubernetes API server to use OIDC authentication.

Incorrect Options:

A. Enable Gatekeeper and create a connector to the user base’s identity provider: Gatekeeper is a Kubernetes policy engine used for enforcing admission control policies, not for authentication. The NKPA course does not associate Gatekeeper with user authentication.

B. Disable native NKP authentication, enable Traefik, and create a connector to the user base’s identity provider: Traefik is an ingress controller for managing external traffic, not authentication. Disabling native authentication is unnecessary, as NKP supports OIDC alongside native methods. The NKPA course does not mention Traefik in the context of authentication.

C. Create a MetalLB connector to the user base’s identity provider: MetalLB is a load balancer for bare-metal Kubernetes clusters, not an authentication component. This option is irrelevant, as per the NKPA course.