Free NCP-CN Practice Test Questions and Answers (2026)

To attach an external Kubernetes cluster, such as Amazon EKS, to Nutanix Kubernetes Platform (NKP) for fleet management, NKP requires administrative access to the target cluster. The first preparatory step on the EKS cluster is to create a Service Account and bind it to the cluster-admin ClusterRole. This grants NKP the necessary permissions to discover resources, monitor the cluster, and manage its lifecycle. NKP will use the token associated with this service account to authenticate with the EKS API server.

A. Configure a ConfigMap according to EKS configuration: A ConfigMap is not a prerequisite for establishing the initial administrative connection. The primary requirement is for authentication and authorization, not configuration data storage.

C. Configure HAProxy to get connected to EKS clusters: Amazon EKS provides its own managed, highly available control plane endpoint. There is no need to configure a separate HAProxy instance for NKP to connect to it.

D. Deploy cert-manager in the EKS clusters: Cert-manager is used for managing TLS certificates for applications within a cluster. It is not a prerequisite for the initial attachment of the cluster to the NKP management plane.

Nutanix Kubernetes Platform Administration Guide v4.2

Registering an External Cluster: "Before you register an external cluster

ensure that you have the following: A service account with cluster-admin permissions on the external cluster." The guide provides the specific kubectl commands to create the service account and the necessary cluster role binding.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide-v42:ecm-kps-register-external-cluster-t.html

Kubernetes Documentation

Managing Service Accounts: This official Kubernetes documentation explains the role of Service Accounts in providing an identity for processes that run in a Pod

which is the mechanism used by NKP to interact with the managed cluster's API.

URL: https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/

The Nutanix Kubernetes Platform (NKP) custom image creation process utilizes Packer and Ansible. Packer builds the machine image, while Ansible playbooks are used to install and configure the software packages within that image. The ansible/groupvars/all/defaults.yaml file within the nutanix-kps-image-builder repository is the standard location where default variables, including the specific versions for Kubernetes (k8sversion) and containerd (containerdversion), are defined. An engineer must modify or verify the values in this file to ensure the correct package versions are used during the image build.

A. config/pulumi/vars/pulumi.kib.config: This path relates to Pulumi, an Infrastructure as Code (IaC) tool. While used by NKP, it is not the tool responsible for defining package versions inside the OS image.

B. terraform/vars/default/terraform.tfvars: This file contains variables for Terraform, which provisions the infrastructure (VMs, networks). It does not control the software versions installed within the OS image.

D. The custom image's .env file: A .env file is not a standard part of the NKP image build process for defining component versions. These versions are build-time parameters, not runtime environment variables in this context.

1. Nutanix Kubernetes Platform Administration Guide: The section "Creating a Custom OS Image for NKP Clusters" describes the process of using the nutanix-kps-image-builder repository

which contains the Packer and Ansible scripts.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide:aks-kps-image-create-custom-t.html

2. Nutanix Kubernetes Platform Image Builder Repository: The file structure of the official repository shows the ansible/groupvars/all/defaults.yaml file containing the version variables.

URL: https://github.com/nutanix/nutanix-kps-image-builder/blob/main/ansible/groupvars/all/defaults.yaml

Specifics: This file explicitly lists variables such as k8sversion and containerdversion.

In an air-gapped Nutanix Kubernetes Platform (NKP) deployment, the Konvoy bootstrap image must be made available to the local Docker daemon on the bastion host before initiating the bootstrap cluster creation. The docker load command is the standard and officially documented method for this task. It directly loads an image from a tar archive (.tar file) into the local image cache on the bastion host. This makes the image accessible for the konvoy up command, which creates the temporary bootstrap cluster.

B. docker image tag konvoy-bootstrap-image-.tar version docker.io/konvoy-bootstrap version: This command is syntactically incorrect. docker image tag is used to apply a new tag to an existing local image, not to load an image from a file archive.

C. nkp push bundle --bundle konvoy-bootstrap-image-.tar --to-registry=: This command is for pushing a complete NKP bundle (a collection of many images and addons) to a private registry, a step that the scenario states has already been completed.

D. nkp load image -f konvoy-bootstrap-image-.tar --to-registry=: While this command loads an image, its primary purpose is to immediately push it to a registry. The specific task is to make the image available on the bastion host for bootstrapping, for which docker load is the more direct and prescribed command.

1. Nutanix Kubernetes Platform 2.5 Documentation

Deploying NKP in an Air-Gapped Environment

Section: Preparing the Bastion Host. The documentation explicitly provides the command for this step: docker load -i konvoy-image-bundle-v.tar.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-v25:ecm-air-gapped-deployment-bastion-host-prep-t.html

2. Docker Official Documentation

docker load. This documentation confirms that docker load restores images and tags from a tar archive.

URL: https://docs.docker.com/engine/reference/commandline/load/

For an air-gapped (dark-site) NKP deployment the bastion host must 1) provide password-less SSH connectivity to the CVM/worker nodes and 2) have its clock synchronised to avoid TLS certificate and cluster-coordination problems.

Nutanix NKP Deployment Guide (section “Prepare the Bastion Host”) lists as mandatory steps:

• “Generate (or copy) an SSH key pair and place the public key on every host that will be reached from the bastion.”

• “Configure and enable NTP on the bastion host so that it stays in time sync with the cluster nodes.”

Docker or LDAP services are not cited as bastion-host requirements.

A. Install LDAP Server – Directory services are not required for bastion preparation; NKP consumes existing identity sources separately.

C. Install Docker – Container runtime is only needed on NKP worker/control-plane nodes or a separate registry server, not on the bastion host itself.

1. Nutanix Kubernetes Platform 2.0 Deployment and Operations Guide

“Prepare the Bastion Host” – Steps 1 & 2 (SSH keys

NTP). https://portal.nutanix.com/page/documents/kubernetes-platform/2.0/prepare-bastion

2. Nutanix Karbon Platform Services Air-Gap Installation Guide

“Bastion Host Requirements” – bullet points on SSH key pair and NTP configuration. https://portal.nutanix.com/page/documents/karbon/airgap/bastion-requirements

Nutanix Kubernetes Platform (NKP) Insights is the specific predictive analytics solution designed to monitor Kubernetes clusters managed by NKP. It proactively detects current and future anomalies related to cluster health, capacity, and performance. After deploying a Kubernetes cluster, the administrator would enable NKP Insights for that cluster to gain the required predictive analytics and anomaly detection capabilities. This aligns directly with the scenario's requirement for a solution that analyzes the deployed cluster.

B. NCM Intelligent Ops: This is a broader Nutanix Cloud Manager feature for AI-driven operations across the entire Nutanix infrastructure (VMs, hosts), not a specialized tool for Kubernetes cluster-specific analytics.

C. Nutanix Pulse: This is a health-monitoring and diagnostics telemetry feature that sends system data to Nutanix Support for proactive case management, not a customer-facing analytics tool.

D. NKP AI Navigator: This is not a valid Nutanix product or feature name and serves as a distractor.

1. Nutanix Kubernetes Platform (NKP) Insights: "NKP Insights is a predictive analytics solution that detects current and future anomalies in your Kubernetes clusters."

Source: Nutanix Kubernetes Platform 4.1 Documentation

"NKP Insights Overview".

2. Nutanix Pulse Health Monitoring: "Pulse is a health monitoring and diagnostics feature of Nutanix clusters... Pulse shares this system-level information with the Nutanix support team to help them resolve issues."

Source: Nutanix Prism Central Guide

"Pulse Health Monitoring".

3. Nutanix Cloud Manager (NCM) Intelligent Operations: "NCM Intelligent Operations... adds AI-driven runbook automation

advanced monitoring

and reporting to your Nutanix environment."

Source: Nutanix.com

"Nutanix Cloud Manager (NCM)".

Upgrading a Nutanix Kubernetes Platform (NKP) managed cluster is a multi-step process that involves upgrading the control plane first, followed by the worker node pools. The correct Nutanix CLI (nkp) command to upgrade the control plane's Kubernetes version is nkp update controlplane, specifying the target version. After the control plane is successfully upgraded, the worker nodes are upgraded on a per-nodepool basis using the nkp upgrade nodepool command. This two-step approach ensures a controlled and safe upgrade process, maintaining cluster stability.

A: The command update nodepool is used for scaling or modifying labels, not for upgrading the Kubernetes version. The correct command verb is upgrade.

D: The update cluster command is used for modifying cluster-level configurations, not for performing the Kubernetes version upgrade of its constituent control plane and worker nodes.

1. Nutanix Kubernetes Platform Command Line Interface (CLI) Reference v4.2: The documentation outlines the commands for managing clusters.

nkp update controlplane: This command is used to "Update a control plane

" which includes modifying the Kubernetes version. See the CLI reference for command usage. (URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-v42-CLI-Reference:Nutanix-Kubernetes-Platform-v42-CLI-Reference

Section: nkp update controlplane)

nkp upgrade nodepool: This command is specifically designed to "Upgrade a nodepool

" which is the correct procedure for upgrading the Kubernetes version on worker nodes. (URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-v42-CLI-Reference:Nutanix-Kubernetes-Platform-v42-CLI-Reference

Section: nkp upgrade nodepool)

Enabling Federal Information Processing Standards (FIPS) compliance for Nutanix Kubernetes Platform (NKP) is a multi-layered process that begins at the operating system level. Before any NKP components can be installed or configured for FIPS mode, the underlying OS on the nodes must be hardened and prepared according to the specific OS vendor's FIPS guidelines. This foundational step ensures that the core cryptographic modules used by the system are FIPS 140-2 validated, which is a mandatory prerequisite for the entire platform to operate in a compliant manner.

A. Run the command export FIPSENABLED=true: This is a subsequent step used to inform the NKP installer that the environment is FIPS-prepared, but it is not the first action.

B. Run the command nkp cluster create --fips: This command initiates the cluster creation process. It is performed after the environment, including the OS, has been fully prepared for FIPS.

D. Click Enable in the NKP Kommander Web UI, Global Workspace -> Settings -> FIPS menu: This UI action is for managing FIPS on an existing Kommander management cluster, not the initial, foundational step of preparing the OS environment.

1. Nutanix Kubernetes Platform Security Guide v2.7

FIPS Compliance: "To run NKP in a FIPS-compliant manner

you must first prepare your environment. Follow your OS vendor’s instructions to ensure that the OS or OS images are prepared for operating in FIPS mode." This is explicitly stated as the first prerequisite. (URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Security-Guide-v27:Nutanix-Kubernetes-Platform-Security-Guide-v27)

2. NIST

Security Requirements for Cryptographic Modules

FIPS PUB 140-2

Section 4.2 Roles

Services

and Authentication: This standard outlines that the operational environment is a key part of the cryptographic module's boundary. Preparing the OS is the first step in defining this compliant environment. (URL: https://csrc.nist.gov/publications/detail/fips/140/2/final)

The correct procedure for creating a Nutanix Kubernetes Platform (NKP) cluster with multiple, distinct worker node pools via the CLI is a multi-step process. First, the nkp create cluster command is executed. This command provisions the Kubernetes control plane and the initial, default worker node pool, as specified by the --worker-replicas and --worker-cpus parameters. Subsequently, each additional worker node pool must be created individually by executing the nkp create nodepool command for each new pool, again specifying its unique configuration with the appropriate parameters. This sequential approach is the standard, documented method for building complex cluster topologies.

B: This option is incorrect because it uses invalid parameter names (--replicas, --cpus) for the nkp create nodepool command. The correct parameters are --worker-replicas and --worker-cpus.

C: This option is incorrect as the nkp create cluster command does not support creating multiple node pools simultaneously using comma-separated values. It only configures the initial worker node pool.

D: This option is incorrect because it uses a non-existent command (nkp create nodepools with an 's') and invalid parameter names (--replicas, --cpus).

1. Nutanix Kubernetes Platform Administration Guide - Creating a Kubernetes Cluster Using the CLI: This guide details the nkp create cluster command. The examples demonstrate that this command is used to create the cluster and its first worker node pool. It does not show syntax for creating multiple pools at once.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide:Nutanix-Kubernetes-Platform-Admin-Guide/cli-reference-platform-cli-reference-c/cli-create-k8s-cluster-t.html

2. Nutanix Kubernetes Platform Administration Guide - Managing Node Pools Using the CLI: This section explicitly describes the process for adding node pools to an existing cluster using the nkp create nodepool command. The parameters shown

such as --worker-replicas

confirm the syntax used in the correct answer.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide:Nutanix-Kubernetes-Platform-Admin-Guide/manage-k8s-clusters-platform-c/manage-node-pools-cli-t.html

To deploy a Nutanix Kubernetes Platform (NKP) cluster with a minimal resource footprint, the administrator must perform a customized installation. This process involves two main steps using the nkp install kommander command set. First, the --init parameter is used to generate a default installation.yaml configuration file. Second, after editing this file to specify a minimal resource profile (e.g., essential), the --yaml parameter is used to direct the installer to use this customized file for the deployment. Both parameters are essential for the workflow of deploying a non-default, minimal resource configuration.

A. --request-timeout: This parameter configures the timeout for individual API server requests, which does not influence the allocation of system resources for the cluster components.

B. --wait-timeout: This parameter adjusts the overall time the installer waits for components to become ready. While useful in slow environments, it does not define or select a minimal resource profile.

Nutanix Kubernetes Platform 2.4 Documentation - Installing Kommander: The official documentation outlines the installation process. It specifies using nkp install kommander --init to generate the configuration file and nkp install kommander --yaml installation.yaml to apply the customized configuration. This two-step process is the standard method for non-default installations

such as selecting a specific resource profile. (Source: Nutanix Portal - Search for "Installing Kommander on the Management Cluster" in the NKP documentation).

D2iQ Kommander Documentation - Customizing the Installation: NKP is based on D2iQ Kommander. The D2iQ documentation details the use of --init to create the installation.yaml and --yaml to apply it. It also describes setting resourceProfile: essential within the YAML for minimal deployments. (Source: D2iQ Kommander Documentation

Installation section).

When a new workload cluster is associated with a Nutanix Kubernetes Platform (NKP) workspace, it inherits the configurations defined at the workspace level by default. This ensures consistency across all clusters managed within that logical boundary. Specifically, NKP automatically deploys any applications that have been "enabled" for the workspace onto the new cluster. Additionally, the cluster's GitOps agent is configured to sync with all Git repositories that have been added as sources to the workspace, facilitating continuous delivery of applications and configurations.

B. The NKP workload cluster will receive all of the NKP RBAC policy that has been assigned to this NKP workspace.

RBAC policies are enforced by the central NKP management plane to control user access to the cluster, not deployed as a configuration onto the cluster itself.

C. The NKP workload cluster will also be assigned to all of the NKP projects that have been created within the NKP workspace.

Projects are logical constructs within a workspace used to organize applications. A cluster is associated with a workspace, not assigned to projects.

1. Nutanix Kubernetes Platform Administration Guide - Application Management: This guide explains that when an application is enabled for a workspace

NKP deploys it to all associated clusters. "When you enable an application for a workspace

NKP deploys the application to all the clusters associated with the workspace." This directly supports option D.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide:Nutanix-Kubernetes-Platform-Admin-Guide/nke-app-mgmt-c.html

2. Nutanix Kubernetes Platform Administration Guide - GitOps: This section details how Git repositories are added to a workspace for continuous delivery to all clusters within it. "You can add a Git repository to a workspace to continuously deliver applications and configurations to the Kubernetes clusters in the workspace." This directly supports option A.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide:Nutanix-Kubernetes-Platform-Admin-Guide/nke-gitops-c.html

3. Nutanix Kubernetes Platform Administration Guide - Project Management: This reference clarifies that projects are for organizing applications

not for assigning clusters.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide:Nutanix-Kubernetes-Platform-Admin-Guide/nke-project-mgmt-c.html

Kommander is the management plane for the Nutanix Kubernetes Platform (NKP). The official and prescribed method for deploying the NKP management cluster, which includes Kommander, is by using the dedicated NKP Command Line Interface (CLI). After setting up a bastion host with the necessary prerequisites, the platform engineer uses commands from the NKP CLI, such as nkp create cluster, to initiate and manage the installation process. This ensures a standardized and supported deployment.

A. AWS CLI: This tool is used for managing Amazon Web Services resources and is not the designated tool for installing the NKP management plane.

B. Terraform: This is an Infrastructure as Code (IaC) tool for provisioning underlying infrastructure, not the specific CLI used to execute the Kommander installation itself.

C. Ansible: This is a configuration management tool. While it can automate setup tasks, it is not the primary command-line tool for deploying NKP.

1. Nutanix Kubernetes Platform v2.4 Documentation

Deploying a Management Cluster

Section: Create a Management Cluster. This section explicitly details the use of the nkp CLI command to deploy the cluster.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-v24:top-create-management-cluster-t.html

2. Nutanix Kubernetes Platform v2.4 Documentation

NKP CLI Command Reference. This reference guide documents all available commands for the nkp CLI

including create

which is fundamental to the installation process.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-v24:Nutanix-Kubernetes-Platform-v24-nkp-cli-command-reference-w-c.html

The most efficient method using Nutanix Kubernetes Platform (NKP) is to leverage its fleet management capabilities. This is achieved by creating a Workspace, which acts as a logical grouping for managing multiple clusters as a single entity. The "Attach Cluster" feature is specifically designed to onboard existing CNCF-conformant Kubernetes clusters, such as the lightweight Kubernetes on the 30 edge devices, into the NKP management plane. Once attached, the administrator can use NKP's centralized tools for consistent application lifecycle management, policy enforcement, and monitoring across the entire fleet from a single interface.

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

This describes a generic GitOps implementation but omits the crucial first step of bringing the clusters under NKP's centralized management. Attaching them to a workspace is required to manage GitOps at scale via NKP.

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

This is a manual, less scalable approach that bypasses the advanced fleet management, governance, and visibility features inherent to the NKP Ultimate license. It introduces maintenance overhead that NKP is designed to eliminate.

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

This is highly disruptive, time-consuming, and unnecessary. NKP is designed to manage existing third-party clusters, making a "rip and replace" strategy the least efficient option.

1. Nutanix Kubernetes Platform Administration Guide - Attaching a Cluster: "You can attach any CNCF-conformant Kubernetes cluster to NKP for centralized management. After you attach a cluster

you can manage the cluster from the NKP console." This directly supports using the "Attach Cluster" feature for existing clusters.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide-v29:ecm-attach-cluster-t.html

2. Nutanix Kubernetes Platform Administration Guide - Workspaces: "A Workspace is a logical grouping of one or more Kubernetes clusters... Workspaces enable you to manage multiple clusters as a single entity

providing a single pane of glass for all your Kubernetes needs." This confirms that a Workspace is the correct construct for managing the fleet of 30 devices.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide-v29:ecm-workspaces-c.html

When deploying a Nutanix Kubernetes Platform (NKP) cluster to AWS using the command-line interface, the deployment tool must be aware of the target AWS region. Setting the AWSREGION environment variable (e.g., export AWSREGION=us-east-1) is a standard and required method for configuring the environment for AWS CLI tools and SDKs, which NKP utilizes for the deployment. This ensures all API calls are directed to the correct regional endpoint as specified in the requirements.

A. Use --dry-run parameter: The --dry-run parameter is used to validate a command without executing it. It is a best practice for testing but not a requirement for the actual deployment.

B. Use --ami-format parameter: This is not a valid parameter. To specify a custom Amazon Machine Image (AMI), the --aws-ami-id parameter would be used, not one related to format.

D. Set an export KUBECONFIG: The KUBECONFIG environment variable is used to point kubectl to a configuration file for accessing an existing cluster. It is not a prerequisite for creating a new one.

1. Nutanix Kubernetes Platform Administration Guide v2.6: In the "Creating a Kubernetes Cluster on AWS (CLI)" section

a prerequisite is to "Configure your AWS credentials." This configuration includes specifying the default region. (URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide-v26:nke-k8s-cluster-aws-create-cli-c.html)

2. AWS Command Line Interface User Guide: The AWS documentation specifies that the region can be configured using the AWSREGION environment variable. This is a standard method for preparing the environment for any AWS operation. (URL: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html

Section: "Environment variables")

The scenario describes a "noisy neighbor" problem, where one application consumes a disproportionate amount of shared cluster resources, negatively impacting others. In Kubernetes, the standard mechanism to enforce fair resource usage and prevent this issue is by using ResourceQuotas and LimitRanges. ResourceQuotas constrain aggregate resource consumption per namespace, capping the total CPU and memory a team can use. LimitRanges enforce resource requests and limits on individual pods within that namespace, ensuring no single workload can monopolize resources. This directly mitigates the problem described.

B. Setting up Network Policies: Network Policies control network traffic flow between pods. They do not manage or limit the consumption of computational resources like CPU or memory.

C. Configuring RBAC: Role-Based Access Control (RBAC) manages user permissions—what actions a user can perform on cluster objects. It does not control the quantity of resources those objects can consume.

D. Implementing Continuous Deployment (CD): CD is a software development practice for automating deployments. It is a process methodology and has no built-in capability to manage or limit cluster resource allocation.

1. Kubernetes Documentation

"Resource Quotas": "A resource quota

defined by a ResourceQuota object

provides constraints that limit aggregate resource consumption per namespace. It can limit the quantity of objects that can be created in a namespace by type

as well as the total amount of compute resources that may be consumed by resources in that namespace."

URL: https://kubernetes.io/docs/concepts/policy/resource-quotas/

2. Kubernetes Documentation

"Limit Ranges": "A LimitRange is a policy to constrain resource allocations (to Pods or Containers) in a namespace." This works in conjunction with quotas to manage resources at a granular level.

URL: https://kubernetes.io/docs/concepts/policy/limit-range/

3. Nutanix Karbon Documentation

"Creating a Kubernetes Cluster (Karbon UI)": While Karbon simplifies deployment

it operates on standard Kubernetes principles. Resource management is a fundamental Kubernetes concept applied to any Karbon-deployed cluster. The solution lies within Kubernetes constructs

not a Karbon-specific feature distinct from them.

URL: https://portal.nutanix.com/page/documents/details?targetId=Karbon-v28:kar-karbon-cluster-create-ui-t.html (This reference establishes that Karbon deploys standard Kubernetes

to which the above Kubernetes documentation directly applies).

The nkp delete cluster command is used to remove a Nutanix Kubernetes Platform (NKP) cluster. According to the scenario, the cluster to be deleted is named temp-ecommerce, and it is a self-managed "Starter" cluster. The correct syntax requires specifying the cluster's name using the --cluster-name flag. Since it is a self-managed cluster, the --self-managed flag is mandatory. Finally, the --kubeconfig flag must point to the cluster's specific configuration file, which is provided as temp-ecommerce.conf. Option C is the only command that correctly assembles all these required parameters.

A: The --all flag is not a valid parameter for the nkp delete cluster command. Deleting a cluster requires explicitly specifying its name for safety.

B: The command is for deleting a cluster, not an application. Using the --application-name flag is incorrect for this operation; --cluster-name must be used.

D: This option incorrectly uses the application's name (temp-shop) as the cluster's name and references a kubeconfig file that does not match the one provided in the scenario.

Nutanix Kubernetes Platform Administration Guide: The procedure for removing a self-managed cluster is detailed here. The guide specifies the exact command syntax: nkp delete cluster --cluster-name --self-managed --kubeconfig . This directly validates the structure and flags used in the correct answer.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide-v29:Nutanix-Kubernetes-Platform-Admin-Guide-v29/kps-kps-cluster-delete-self-managed-t.html

Section: Deleting a Self-Managed NKP Cluster

The error message Error: failed to create cluster: failed to connect to docker daemon: is docker running? explicitly indicates that the nkpctl command-line utility cannot communicate with the Docker service on the local machine where the command is being executed. The Nutanix Kubernetes Platform (NKP) requires a local container runtime, such as Docker, to create a temporary bootstrap cluster during the provisioning process. If this runtime is not installed or is not running, the bootstrap process fails, preventing the creation of the target NKP cluster.

B: The error originates from the nkpctl tool's interaction with the local container runtime, not from an Ansible playbook's syntax or execution.

C: A file permission error on the nkpctl binary would typically result in a "Permission denied" shell error, preventing the program from running at all.

D: Helm charts are used to deploy applications onto an already existing Kubernetes cluster; this error occurs during the cluster creation phase itself.

Nutanix Kubernetes Platform Administration Guide: In the "Setting Up the CLI" section

the guide lists "A Docker-compatible container runtime" as a prerequisite for the machine where you run the nkpctl CLI. It states

"The CLI uses a local container runtime to create a local bootstrap cluster to provision a Kubernetes cluster." This directly supports that a non-running Docker service would cause a creation failure. (URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide:Nutanix-Kubernetes-Platform-Admin-Guide

search for "Setting Up the CLI" -> "Prerequisites").

To deploy a Nutanix Kubernetes Platform (NKP) cluster on pre-existing AWS infrastructure, the documented and correct method is to create an overrides file. This YAML file specifies the identifiers for the existing VPC, subnets, and other components. The nkp create cluster aws command is then executed with the --overrides parameter pointing to this file. This instructs the NKP deployment process to use the specified infrastructure instead of provisioning new resources, thereby meeting the requirement.

A: The nkp adopt command is used for bringing an existing, externally created Kubernetes cluster under NKP management, not for adopting infrastructure components before creating a new cluster.

C: While the UI may offer some customization, the standard and fully supported method for deploying on existing infrastructure (a "brownfield" deployment) is via the CLI with an overrides file.

D: The nkp create cluster aws command does not accept direct command-line parameters for existing infrastructure like VPC or subnet IDs; this level of customization requires an overrides file.

1. Nutanix Karbon Platform Services Documentation - Deploying a Kubernetes Cluster on an Existing AWS VPC: This official guide explicitly states

"To deploy a Kubernetes cluster on an existing AWS VPC

you must create an overrides file that contains the details of your existing AWS infrastructure. You then reference this overrides file when you run the nkp create cluster aws command." It also provides the exact command syntax: nkp create cluster aws --name --version --overrides .

URL: https://portal.nutanix.com/page/documents/details?targetId=Karbon-Platform-Services-v25:kps-kps-deploy-k8s-cluster-aws-existing-vpc-t.html

2. Nutanix Karbon Platform Services Documentation - Adopting an Existing Kubernetes Cluster: This document clarifies the purpose of the adopt command

showing it is for managing existing clusters

not infrastructure.

URL: https://portal.nutanix.com/page/documents/details?targetId=Karbon-Platform-Services-v25:kps-kps-adopt-existing-k8s-cluster-t.html

For a Nutanix Kubernetes Platform (NKP) deployment in a dark site (an environment without internet access), the --airgapped flag is a mandatory attribute in the nkp create cluster command. This flag signals to the installer that it must not attempt to reach public repositories for software components. Instead, it must rely exclusively on the pre-downloaded OS images and the container images available in the specified private registry (--registry-url). While the command correctly provides details for a private registry, it is the --airgapped flag that enables the specific dark site deployment workflow.

B. --insecure: This flag is used to trust a private registry with a self-signed or invalid TLS certificate. It is not the primary flag for enabling a dark site deployment.

C. --registry-url: This attribute is already present in the provided command, specifying the location of the private container registry. Therefore, it is not missing.

D. --registry-username: The command already includes --registry-mirror-username, which is the correct flag for providing credentials to the private registry. It is not a missing attribute.

1. Nutanix Kubernetes Platform Deployment Guide: In the section "Deploying a Kubernetes Cluster in a Dark Site (Air-Gapped)

" the documentation explicitly states: "To deploy a Kubernetes cluster in a dark site

you must include the --airgapped flag in the nkp create cluster command." This confirms it is a required flag for this scenario. (URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Deployment-Guide:Nutanix-Kubernetes-Platform-Deployment-Guide - Search for "Deploying a Kubernetes Cluster in a Dark Site").

2. Nutanix Kubernetes Platform Command Reference: The reference for the nkp create cluster command details the --airgapped flag as the method to "Deploy a Kubernetes cluster in an air-gapped environment." It also shows the --registry-url and --registry-mirror-username flags

confirming they are distinct from the --airgapped flag. (URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Command-Reference:Nutanix-Kubernetes-Platform-Command-Reference - Search for "nkp create cluster").

The correct procedure to deploy an application from the Nutanix Kubernetes Platform (NKP) catalog to a specific cluster involves navigating to that cluster's management interface. The engineer must first select the cluster (prod-01) and view its details. This action leads to the cluster-specific dashboard, which includes the "Application Dashboard". From this dashboard, the engineer can find and enable (deploy) applications like NKP Insights directly onto the selected cluster. This ensures the operation is performed in the correct context, targeting only the prod-01 cluster as intended.

A: This option is less precise. The "Applications" menu selected directly after "Clusters" typically shows a global view, not the specific application management dashboard for the prod-01 cluster.

B: This path describes managing the global application catalog, not deploying an application to a specific cluster. This action would make an app available but not install it on prod-01.

C: This describes an incorrect and non-existent user interface path for deploying the NKP Insights application. The application is managed under the cluster's Application Dashboard.

1. Nutanix Kubernetes Platform 2.1 Administration Guide

App Management > Deploying an App: The official documentation outlines the procedure for deploying an application. The steps are: Navigate to Kubernetes Management

select the target cluster

which opens the cluster details page

click the "Applications" tab

find the desired app

and select "Deploy". This workflow directly corresponds to the actions described in option D.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide-v21:ecm-app-management-deploy-t.html

Section: App Management > Deploying an App.

The correct method for achieving multi-tenancy and delegating administrative control in Nutanix Kubernetes Platform (NKP) is by using workspaces. A workspace serves as a dedicated, isolated environment for a team or tenant. The proper sequence is to first create a workspace for the R&D team. Then, an infrastructure provider (e.g., a Nutanix cluster) is registered specifically within that workspace. Finally, an R&D group is created, and the 'Workspace Admin' role is assigned to this group within the context of the 'R&D' workspace, granting them full control over the resources and clusters deployed inside it.

B: An NKP connector is used for integrating external services like identity providers or container registries, not for creating isolated tenant environments or assigning infrastructure permissions.

C: This option is incorrect because an infrastructure provider is created at the workspace level, not within a project. Projects exist within a workspace and consume the infrastructure assigned to that workspace.

D: Permissions are assigned to groups within the context of a workspace or project, not directly to an infrastructure provider. This option also incorrectly uses the concept of a connector.

1. Nutanix Cloud Native Administrator Guide - Multi-Tenancy: "Nutanix Cloud Native provides multi-tenancy to enable you to create logically isolated environments called workspaces for different teams or tenants... Each workspace has its own set of users

infrastructure

and projects." This confirms that a workspace is the correct top-level object for isolation.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Cloud-Native-Admin-Guide-v32:glo-multi-tenancy-c.html

2. Nutanix Cloud Native Administrator Guide - Onboarding an Infrastructure: The procedure for onboarding an infrastructure provider clearly states that you must first select the workspace into which the infrastructure will be added. "To onboard an infrastructure

you must be a platform administrator or a workspace administrator... In the Workspaces view

select the workspace where you want to onboard the infrastructure." This refutes option C.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Cloud-Native-Admin-Guide-v32:oss-onboarding-infrastructure-t.html

3. Nutanix Cloud Native Administrator Guide - Identity and Access Management (IAM): "You can assign roles to users and groups at the platform

workspace

or project level." This documentation details assigning roles like 'Workspace Admin' to a group within a specific workspace

supporting the methodology in option A.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Cloud-Native-Admin-Guide-v32:glo-iam-c.html