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