Pass the Nutanix Nutanix Certified Professional (NCP) NCP-CN Questions and answers with CertsForce

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 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 isnkp 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.