Nutanix NCP-CN Actual Questions

NKP uses Cluster API (CAPI) to provision and manage Kubernetes clusters across supported infrastructures, including Nutanix AHV, vSphere, AWS, and GCP. CAPI components, such as controllers and providers, are deployed to manage the lifecycle of clusters on these platforms. However, when NKP attaches to a managed Kubernetes service like Azure Kubernetes Service (AKS), CAPI components are not deployed because AKS is managed by Azure, and NKP only integrates with the cluster for fleet management, not provisioning.

The NKPA course explains: “For managed Kubernetes services like AKS, NKP attaches the cluster to its management plane without deploying CAPI components, as the underlying infrastructure is managed by the cloud provider.” The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide reinforces this: “CAPI is used for NKP-managed clusters on Nutanix, vSphere, AWS, and GCP, but not for attached managed services like AKS.”

Incorrect Options:

A. vSphere: NKP deploys CAPI components (e.g., CAPV provider) to manage vSphere-based clusters.

B. GCP: NKP deploys CAPI components (e.g., CAPG provider) for GCP-based clusters.

C. Nutanix: NKP deploys CAPI components (e.g., CAPA provider for AHV) for Nutanix AHV clusters.

The NKPA course explains that to access a Kubernetes cluster managed by NKP, such as iot-1 in the workspace iot-plant-3, a kubeconfig file is required to authenticate and interact with the cluster’s API server. If the kubeconfig file is missing, the engineer can generate it using the NKP CLI. The correct command is nkp get kubeconfig -c iot-1 -w iot-plant-3 > iot-1.conf (Option B).

This command retrieves the kubeconfig for the specified cluster (-c iot-1) in the specified workspace (-w iot-plant-3) and redirects the output to a file named iot-1.conf. The engineer can then use this kubeconfig file with kubectl (e.g., kubectl --kubeconfig=iot-1.conf get pods) to review the deployment. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To generate a kubeconfig file for an NKP-managed cluster, use nkp get kubeconfig -c -w , which retrieves the necessary credentials for cluster access.”

Incorrect Options:

A. kubectl get kubeconfig: kubectl does not have a get kubeconfig subcommand, and it cannot generate kubeconfig files for NKP clusters.

C. kubectl get secret iot-1 -n kommander: While secrets in the kommander namespace may store credentials, this command does not format them as a kubeconfig file.

D. nkp get configmaps: This is not a valid command for retrieving kubeconfig files; ConfigMaps do not store kubeconfig data in this context.

The NKPA course clarifies that NKP licenses are based on the number of CPU cores in the infrastructure hosting the Kubernetes clusters. This licensing model applies to both on-premises (e.g., Nutanix AHV) and cloud-based deployments. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “NKP licenses are obtained based on the total number of CPU cores allocated to the clusters managed by the platform.” This core-based licensing ensures flexibility across different infrastructure types while aligning with the resource consumption of Kubernetes workloads.

Incorrect Options:

A. Flash: Flash storage is not a licensing unit for NKP.

B. CPU Sockets: Nutanix licenses for other products may use sockets, but NKP uses cores.

C. TiBs: Terabytes are used for storage licensing, not NKP.

To push the NKP Catalog Applications image bundle to a private registry, the official nkp push bundle command must be used with the specified parameters to authenticate and push the bundle to the registry.

Exact extract:

“Use the nkp push bundle command to upload the NKP catalog applications image bundle to the specified private registry, ensuring secure and complete image upload.”