NCP-CN Exam Questions – Real & Updated Questions PDF [Q51-Q73]

March 20, 2026 latestexam 0 Comments

Rate this post

NCP-CN Exam Questions – Real & Updated Questions PDF

Pass Guaranteed Quiz 2026 Realistic Verified Free Nutanix

Q51. A development team is working on a new application that requires access to certain cluster resources. The team needs to ensure that they have limited permissions to avoid unauthorized changes in other environments. Among the tasks they will perform are the following:
Deploy new versions of the application to their specific namespace.
Scale deployments according to demand.
View logs and metrics of their applications to monitor performance.When using the NKP GUI, what type of access should the team configure?

NKP Role

Cluster Role

Cluster Admin

Kommander Role

Q52. NKP cluster nodes require a disk for some of its deployed components, outside of an application’s persistent volume requirements. What are these components and where are they deployed?

kubelet and containerd, in /opt/nkp

kubelet and containerd in /var/lib

kubectl and kubelet in /opt/nkp

kubectl and kubelet in /var/nkp

Q53. A Platform Engineer is running a Kubernetes cluster version 1.28.1 on AWS that needs to be upgraded to version 1.29.9. This cluster was deployed with Nutanix NKP. Which two actions should the engineer take to complete this requirement? (Choose two.)

Upgrade Workers with nkp update nodepool aws ${NODEPOOL_NAME} –cluster- name=${CLUSTER_NAME} –kubernetes-version=v1.29.9

Upgrade Control Planes with nkp update controlplane aws –cluster-name=${CLUSTER_NAME} — ami AMI_ID –kubernetes-version=v1.29.9

Upgrade Workers with nkp upgrade nodepool aws ${NODEPOOL_NAME} –cluster- name=${CLUSTER_NAME} –kubernetes-version=v1.29.9

Upgrade the Cluster with nkp update cluster aws –cluster-name=${CLUSTER_NAME} –ami AMI_ID
–kubernetes-version=v1.29.9

The NKPA course details the process for upgrading an NKP-managed Kubernetes cluster, such as one running on AWS from version 1.28.1 to 1.29.9. Upgrading a Kubernetes cluster involves two distinct steps:
upgrading the control plane nodes and upgrading the worker nodes, ensuring minimal disruption and maintaining compatibility. The NKP CLI provides specific commands to handle these upgrades separately for AWS clusters.
* Upgrade Control Planes with nkp update controlplane aws –cluster-name=${CLUSTER_NAME}
–ami AMI_ID –kubernetes-version=v1.29.9 (Option B):The control plane must be upgraded first to the target Kubernetes version (1.29.9). The nkp update controlplane aws command updates the control plane nodes, specifying the cluster name, the new Kubernetes version, and an updated AMI (Amazon Machine Image) that supports the target version. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To upgrade an NKP cluster on AWS, first update the control plane using nkp update controlplane aws –cluster-name <name> –ami <ami-id> –kubernetes-version <version> to ensure the control plane runs the desired Kubernetes version.” The –ami flag is required to specify a compatible image for the upgraded control plane nodes.
* Upgrade Workers with nkp upgrade nodepool aws ${NODEPOOL_NAME} –cluster- name=${CLUSTER_NAME} –kubernetes-version=v1.29.9 (Option C):After the control plane is upgraded, the worker nodes in each node pool must be upgraded to match the control plane version.
The nkp upgrade nodepool aws command updates the specified node pool to the target Kubernetes version (1.29.9). The NKPA course notes: “Upgrade worker nodes using nkp upgrade nodepool aws
<nodepool-name> –cluster-name <cluster-name> –kubernetes-version <version>, which performs a rolling update to ensure minimal downtime.” This command automatically handles the rolling update of worker nodes, replacing them with new nodes running the updated version. Note that the –ami flag is not required here, as NKP typically uses the same AMI as the control plane or retrieves a compatible one based on the version.
Incorrect Options:
* A. nkp update nodepool aws: The correct command is nkp upgrade nodepool, not nkp update nodepool. The NKPA course uses upgrade for version changes to node pools.
* D. nkp update cluster aws: This command is not the standard approach for upgrading Kubernetes versions in NKP. The course specifies separate commands for control plane and node pool upgrades to ensure a controlled process.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Cluster Upgrades.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

Q54. A Platform Engineer has been tasked with building a custom image for the deployment of NKP management and worker nodes. The engineer needs to ensure that the proper package versions are used when creating these images. The security team has only authorized version 1.30.5 of Kubernetes and version 1.7.22 of containerd. Where should the engineer go to verify that this is the version being used when building the custom image?

config/pulumi/vars/pulumi.kib.config

terraform/vars/default/terraform.tfvars

ansible/group_vars/all/defaults.yaml

The custom image’s .env file

Q55. NKP Starter is bundled with which entitlement?

NCI Pro

NCI Starter

NCM Pro

NCM Starter

Q56. A development Kubernetes cluster deployed with NKP is having performance issues. The Cloud Engineer commented that worker VMs are consuming a lot of CPU and RAM. The Platform Engineer took a look at the CPU and RAM statistics with Grafana and confirmed that the worker VMs are running out of CPU and memory. The Kubernetes cluster has 4 workers with 8 vCPUs and 32 GB RAM. What could the Platform Engineer do?

Call tech support to take a look at the infrastructure and investigate.

Ask developers to lower the number of application replicas.

Add more CPU and memory to workers with nkp scale –cpu 16 –memory 64 –cluster-name
${CLUSTER_NAME}

Add one more worker with nkp scale nodepools ${NODEPOOL_NAME} –replicas=5 –cluster- name=${CLUSTER_NAME} -n ${CLUSTER_WORKSPACE}

The NKPA course addresses performance issues in NKP clusters, such as high CPU and memory consumption on worker nodes, by recommending scaling options to distribute workloads more effectively.
The Kubernetes cluster in the scenario has 4 workers, each with 8 vCPUs and 32 GB RAM, and is running out of resources. The most effective solution is to add more workers to the cluster to increase overall capacity and balance the load, rather than modifying existing workers or reducing application replicas.
The correct action is to add one more worker using the command nkp scale nodepools
${NODEPOOL_NAME} –replicas=5 –cluster-name=${CLUSTER_NAME} -n
${CLUSTER_WORKSPACE} (Option D). This command scales the specified node pool to 5 replicas (from the current 4), adding one additional worker to the cluster. The new worker will have the same configuration (8 vCPUs, 32 GB RAM) as the existing workers, providing additional capacity to alleviate resource contention. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To address performance issues due to resource exhaustion in an NKP cluster, scale out by adding workers using nkp scale nodepools
<nodepool-name> –replicas <count> –cluster-name <cluster-name> -n <workspace>.” Incorrect Options:
* A. Call tech support to investigate: While support can help, the issue is clearly resource exhaustion, which can be resolved by scaling the cluster-a task the Platform Engineer can perform directly.
* B. Ask developers to lower application replicas: Reducing replicas may decrease resource usage but could impact application availability or performance, which is not ideal for a development cluster.
* C. Add more CPU and memory to workers with nkp scale –cpu 16 –memory 64: The nkp scale command does not support –cpu and –memory flags for resizing existing workers. Resizing VMs typically requires updating the node pool configuration and replacing nodes, which is more complex than adding new workers.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Cluster Scaling and Performance Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

Q57. Which two statements are true regarding deploying NKP on an Azure Kubernetes Service (AKS) Infrastructure? (Choose two.)

Existing AKS clusters must be attached to the Management cluster.

AKS best practices encourage building customized images.

NKP Management cluster with the Kommander component must be installed before installing NKP on AKS cluster.

AKS clusters can be deployed as Management or Pro NKP clusters.

Q58. A Platform Engineer has been tasked with backing up and restoring a production environment to ensure persistent data is available during a disaster at a primary site. What is recommended for backup and restore production use cases?

Protection Domain

Rook Ceph

External Storage Class

S3-compatible API

Q59. A Kubernetes administrator needs to ensure that the following requirements are met whenever a new workload cluster is deployed to a workspace:
Grafana Logging
Grafana Loki
Project LoggingHow would the administrator ensure that these components are deployed as part of a cluster deployment?

Enable them in the Insights section under workspace.

Enable them in the Projects section under workspace.

Enable them in the Clusters section under workspace.

Enable them in the Application section under workspace.

Q60. In an effort to control cloud cost consumption, auto-scale is configured to meet demands as needed.
What is the behavior for when nodes are scaled down?

Node is changed to a status of Hibernate.

Node is CAPI deleted from its infrastructure provider, effectively removing it from its hypervisor.

Node is changed to a status of Power-Off for stand-by.

Node is paused in Kubernetes and the infrastructure continues to consume the resources at the current level.

As per the NKPA 6.10 documentation and cluster autoscaler behavior, when nodes are scaled down in NKP (or any CAPI-managed environment), the node is deleted from the infrastructure provider (vSphere, AWS, Nutanix, etc.). This effectively removes it from both the cluster and the underlying hypervisor or cloud provider, thus freeing up resources and reducing costs.
Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 – “Cluster Autoscaler Node Deletion Behavior” NCP-CN 6.10 Study Guide – “Autoscaler Impact on Infrastructure Resources”

Q61. A company has standardized on NKP for their Kubernetes platform and needs to deploy their first cluster with the following requirements:
Dark site ready
Custom Service CIDR Block
Custom Pod CIDR Block
Hosted on Nutanix AHV ClusterWhich tool would the administrator use to perform the deployment?

kubectl CLI

NKP GUI

NKP CLI

OCP CLI

Q62. A Platform Engineer needs to create an NKP cluster on vSphere infrastructure, using the vSphere provisioning method. The cluster needs to have 3 worker node pools:
First node pool should consist of 6 worker nodes
Second node pool should consist of 3 worker nodes
Third node pool should consist of 3 worker nodesAdditionally, the worker nodes in the first node pool should be set to 10 CPUs, the second node pool workers should be set to 8 CPUs, and the third node pool workers should be set to 6 CPUs. What is the proper way to create the NKP cluster using the NKP CLI?

First, execute the nkp create cluster vsphere command, including the following parameters:–worker-replicas 6–worker-cpus 10Then, execute the nkp create nodepool vsphere command, including the following parameters:–worker-replicas 3–worker-cpus 8Then, execute the nkp create nodepool vsphere command, including the following parameters:–worker-replicas 3–worker-cpus 6

When executing the nkp create cluster vsphere command, include the following parameters:–node-pools 3–worker-replicas 6,3,3–worker-cpus 10,8,6

First, execute the nkp create cluster vsphere command, including the following parameters:–worker-replicas 6–worker-cpus 10Then, execute the nkp create nodepools vsphere command, including the following parameters:–replicas 3,3–cpus 8,6

Q63. A company has 30 Edge devices with lightweight Kubernetes, and developers need to push the application to every edge device. An NKP administrator has the NKP Ultimate license tier configured and has access to all kubeconfig files for the 30 edge devices. What is the most efficient way that the administrator can lifecycle manage the application deployments?

Create a GitHub configuration, deploy it to the 30 edge devices, and configure them to use a GitHub account.

Create a script to automate the deployment to every edge device.

Ask the developers to delete the lightweight Kubernetes and deploy new Kubernetes clusters with NKP.

Create a new Workspace and attach the 30 edge devices to this workspace with Attach Cluster.

Q64. NKP cluster nodes require a disk for some of its deployed components, outside of an application’s persistent volume requirements. What are these components and where are they deployed?

kubelet and containerd, in /opt/nkp

kubelet and containerd in /var/lib

kubectl and kubelet in /opt/nkp

kubectl and kubelet in /var/nkp

According to the NKPA 6.10 documentation, the critical system components for NKP nodes are:
* kubelet
* containerdThese components are deployed in the standard Linux path: /var/lib.
Exact extract from the documentation:
“The kubelet and containerd services require disk space in /var/lib on the host operating system. It’s essential to allocate sufficient storage in /var/lib to accommodate these core Kubernetes components.” Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 – “Host Requirements for Cluster Nodes” NCP-CN 6.10 Study Guide – “Node OS Directory Requirements”
=======

Q65. A company has decided to expand NKP to features that require higher product tiers, like fleet-management and additional infrastructure providers. The company has already obtained the necessary licensing. Which action is required when adding and activating a license from NKP Starter to a higher-tier product?

Contact Nutanix Support.

Ensure that worker nodes are sized appropriately.

Log out and log back in as a Global License Administrator.

Regenerate the ACME-based certificate for NKP.

The documentation confirms that when a new license is activated to upgrade to a higher tier, users must log out and log back in for the license changes to take effect. This ensures that updated entitlements are loaded into the UI and CLI environment.
Exact extract from documentation:
“After applying a new license for a higher-tier product, log out and log back in to see and activate the newly available features.” Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 – “License Activation Process” NCP-CN 6.10 Study Guide – “Upgrading and Activating NKP Licenses”
=======

Q66. A company uses an Artifactory private registry for development. The NKP deployment must use this private registry since the Security Administrator has the firewall configured to reject connections to public container registries. The first task is to push the NKP bundle to this private registry.
What options should be used to push the NKP bundle to this private registry?

–registry-mirror-url, –registry-mirror-username and –registry-mirror-password

–mirror-url, –mirror-username and –mirror-password

–registry-url, –registry-username and –registry-password

–to-registry, –to-registry-username and –to-registry-password

Q67. Using an NKP Ultimate license, a Platform Engineer has created a new workspace and needs to create a new Kubernetes cluster within this workspace. However, the engineer discovers that the Create Cluster option is grayed out, as shown in the exhibit. How should the engineer resolve this issue?

Create the cluster only using YAML and not the GUI.

Attach existing clusters instead of creating a new cluster.

Create an Infrastructure provider for the workspace.

Ensure NKP is upgraded to a minimum version of 2.12.

Q68. Which option is enabled with the NKP Pro licensing tier?

Insights

Kubernetes Dashboard

AI OPS

Fleet Management

Q69. After loading the NKP bundles to a private registry in an air-gapped environment, a Platform Engineer now needs the Konvoy bootstrap image to create the bootstrap cluster. The Konvoy image has not been loaded into the registry. Which is the most viable command to load the Konvoy bootstrap image on the bastion host?

docker load -i konvoy-bootstrap-image-<version>.tar

docker image tag konvoy-bootstrap-image-<version>.tar version docker.io/konvoy-bootstrap version

nkp push bundle –bundle konvoy-bootstrap-image-<version>.tar –to-registry=<REGISTRY_URL>

nkp load image -f konvoy-bootstrap-image-<version>.tar –to-registry=<REGISTRY_URL>

Q70. A Platform Engineer has been tasked with backing up and restoring a production environment to ensure persistent data is available during a disaster at a primary site. What is recommended for backup and restore production use cases?

Protection Domain

Rook Ceph

External Storage Class

S3-compatible API

The NKPA course recommends using a S3-compatible API for backup and restore operations in production NKP environments, as it integrates with Velero, NKP’s backup and restore tool. Velero supports S3- compatible storage (e.g., AWS S3, Nutanix Objects, or MinIO) as a backup storage location, allowing persistent data, including volumes and cluster resources, to be backed up and restored during disaster recovery scenarios. This approach ensures compatibility with cloud-native backup workflows and provides scalability and reliability for production use cases.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “For production backup and restore in NKP, use Velero with an S3-compatible API to store backups, ensuring persistent data availability during disaster recovery.” Nutanix Objects, which provides an S3-compatible API, is often used in Nutanix environments for this purpose, but any S3-compatible storage (e.g., an off-site S3 bucket) can be configured.
Incorrect Options:
* A. Protection Domain: Protection Domains are a Nutanix AOS feature for VM-level replication, not for Kubernetes backup/restore.
* B. Rook Ceph: Rook Ceph provides persistent storage for NKP clusters but is not a backup solution; it can be backed up using Velero with S3 storage.
* C. External Storage Class: Storage Classes define how volumes are provisioned, not how they are backed up or restored.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Backup and Restore.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Velero Documentation: https://velero.io

Q71. A Kubernetes administrator needs to deploy a new NKP deployment for a DR Datacenter. Cluster information:
* AOS 6.10
* Hypervisor is AHV
* Six NX-8170-G9 NodesWhich command should the administrator use to invoke the prompt-based CLI deployment method?

nkp create cluster nutanix

nkp create cluster ahv

nkp create nodepool nutanix

nkp install kommander

The NKPA course outlines the process for deploying an NKP cluster on Nutanix AHV infrastructure using the NKP CLI. For a prompt-based deployment, where the administrator is guided through configuration options interactively, the correct command is nkp create cluster ahv. This command initiates the deployment of an NKP cluster on the AHV hypervisor, prompting the administrator to input details like cluster name, node counts, and networking settings.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To deploy an NKP cluster on AHV using the prompt-based CLI method, use nkp create cluster ahv, which guides the administrator through the configuration process.” The command is specific to the AHV hypervisor (part of AOS 6.10) and is suitable for the specified hardware (NX-8170-G9 nodes).
Incorrect Options:
* A. nkp create cluster nutanix: The provider is specified as ahv, not nutanix, in the NKP CLI syntax.
* C. nkp create nodepool nutanix: This creates a node pool, not a cluster, and is not prompt-based.
* D. nkp install kommander: Kommander is a management component, not used for cluster creation on AHV.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Cluster Deployment.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Building NKP Clusters.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

Q72. A Platform Engineer manages an NKP environment and is preparing a machine image to become an NKP cluster node. Which statement is correct regarding the default node preparation process?

Packer is used to make the OS image CAPI-compliant for use as an NKP node.

Ansible is used to make the OS image CAPI-compliant for use as an NKP node.

Goss is used to harden the OS image for use as an NKP node.

Terraform is utilized to clone an existing OS image for use as an NKP node.

The NKPA course details the default node preparation process for NKP cluster nodes, which involves creating a machine image that is compliant with Cluster API (CAPI) standards. The primary tool used in this process is Packer, which automates the creation of machine images by provisioning a base OS image (e.g., Ubuntu or Rocky Linux) with the necessary components for Kubernetes, such as kubeadm, containerd, and other dependencies.
Packer ensures the image is CAPI-compliant by installing the required Kubernetes binaries, configuring the container runtime, and setting up networking and storage components. The Nutanix Cloud Native (NCP-CN)
6.10 Study Guide states: “In the default node preparation process for NKP, Packer is used to build a CAPI- compliant OS image, installing Kubernetes components and dependencies for use as an NKP node.” This process is typically orchestrated by NKP Image Builder (NIB) or Kubernetes Image Builder (KIB), both of which rely on Packer for image creation.
Incorrect Options:
* B. Ansible is used to make the OS image CAPI-compliant: Ansible is used by KIB/NIB to apply configurations during the Packer build process, but Packer is the primary tool for creating the image.
Ansible alone does not make the image CAPI-compliant.
* C. Goss is used to harden the OS image: Goss is a validation tool that can be used for image hardening, but it is not part of the default NKP node preparation process. Hardening is an optional step.
* D. Terraform is utilized to clone an existing OS image: Terraform is for infrastructure provisioning, not image creation or cloning. Packer handles image creation in NKP.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Node Preparation.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on NKP Deployment Prerequisites.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Packer Documentation: https://www.packer.io

Q73. Refer to Exhibit:

Using an NKP Ultimate license, a Platform Engineer has created a new workspace and needs to create a new Kubernetes cluster within this workspace. However, the engineer discovers that the Create Cluster option is grayed out, as shown in the exhibit. How should the engineer resolve this issue?

Create the cluster only using YAML and not the GUI.

Attach existing clusters instead of creating a new cluster.

Create an Infrastructure provider for the workspace.

Ensure NKP is upgraded to a minimum version of 2.12.

The exhibit shows the NKP UI with the “Create Cluster” option grayed out in a new workspace, indicating that a prerequisite for cluster creation is missing. The NKPA course explains that to create a new Kubernetes cluster in a workspace, an Infrastructure Provider must be configured for that workspace. An Infrastructure Provider defines the underlying infrastructure (e.g., Nutanix AHV, AWS, vSphere) where the cluster will be provisioned, and without it, the Create Cluster option remains disabled in the UI.
The NKP Ultimate license supports creating clusters across various infrastructures, but the workspace must be associated with an Infrastructure Provider to enable cluster creation. The Nutanix Cloud Native (NCP-CN)
6.10 Study Guide states: “Before creating a cluster in a new workspace, ensure an Infrastructure Provider is configured for the workspace in the NKP UI; otherwise, the Create Cluster option will be grayed out.” The engineer should navigate to the Infrastructure Providers section in the NKP UI (typically under the Global or Administration view), create a provider (e.g., for Nutanix AHV, AWS, or vSphere), and associate it with the workspace. Once this is done, the Create Cluster option will become available.
Incorrect Options:
* A. Create the cluster only using YAML and not the GUI: The issue is not with the GUI itself but with the missing Infrastructure Provider, which affects both GUI and CLI cluster creation. YAML alone does not resolve this.
* B. Attach existing clusters instead of creating a new cluster: Attaching existing clusters is an alternative but does not address the requirement to create a new cluster.
* D. Ensure NKP is upgraded to a minimum version of 2.12: The NKP Ultimate license implies a recent version, and the course does not indicate that version 2.12 is specifically required for this functionality. The issue is configuration-related, not version-related.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Cluster Creation Prerequisites.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Workspace Configuration.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

Loading …