When deploying NKP to AWS, the bootstrap process requires AWS credentials to interact with AWS APIs for provisioning resources like EC2 instances. The NKPA course specifies that the nkp CLI supports the --aws-profile flag to specify a custom AWS profile for authentication. This profile, defined in the AWS credentials file (~/.aws/credentials), contains the access key and secret key for the desired AWS account.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To deploy NKP on AWS with custom credentials, use the --aws-profile= flag during the nkp create bootstrap command to reference a specific AWS profile.” This approach leverages the AWS CLI’s profile management, ensuring secure and flexible credential handling. For example, the command would be nkp create bootstrap --aws-profile=my-profile --kubeconfig bootstrap-cluster.conf.

Incorrect Options:

B. --cloud-credentials=<my-profile></my-profile>: This flag is not used by the nkp CLI. The NKPA course specifies --aws-profile for AWS.

C. --with-aws-bootstrap-credentials=true: This flag does not exist in the NKPA documentation for NKP bootstrap.

D. --aws-access-key=<aws access="" key=""> --aws-secret-key=<aws secret="" key=""></aws></aws>: While these flags may be used in some tools, the NKPA course recommends using --aws-profile to avoid hardcoding sensitive credentials.

According to theNKPA 6.10 documentation, licensing in an NKP cluster is constrained by the total number of vCPUs assigned to all nodes (workers and control planes). In this scenario, the cluster has a maximum of 150 vCPUs available.

The existing output shows 10 worker nodes, each with 8 vCPUs (10×8=80 vCPUs) and 3 control plane nodes, each with 4 vCPUs (3×4=12 vCPUs).

Current vCPU usage: 80 + 12 = 92 vCPUs.

Remaining vCPUs: 150 - 92 = 58 vCPUs.

Option A:

Adding 6 control plane nodes (6×4=24 vCPUs).

This would increase control planes to 9 total (3 existing + 6 new). Control plane nodes would consume 9×4=36 vCPUs.

Worker nodes remain at 80 vCPUs.

Total vCPU usage: 36 + 80 = 116 vCPUs (still under 150 vCPUs).

However, it’s unusual and unnecessary to have 9 control planes in a typical NKP setup. NKPA and NCP-CN best practices indicate typically no more than 3 or 5 control planes for HA. Therefore, this is technically possible but not recommended or standard practice. So not selected.

Option B:

Expanding the existing worker nodepool by 8 nodes (8×8=64 vCPUs).

This would add 64 vCPUs to the current 92 vCPUs:

92 + 64 = 156 vCPUs → exceeds licensing limit.

Correction:The question specifies “expand up to 8 nodes,” so it’s possible to expand by only 7 nodes (7×8=56 vCPUs).

92 + 56 = 148 vCPUs → within licensing limits.

Thus, expanding byup to 7 nodesis valid.

Option C:

Creating a new worker nodepool with 10 nodes (10×8=80 vCPUs).

This would add 80 vCPUs to the existing 92 vCPUs:

92 + 80 = 172 vCPUs → exceeds 150 vCPU licensing limit.

Not valid.

Option D:

Expanding the original worker nodepool by up to 4 nodes (4×8=32 vCPUs) = +32 vCPUs.

Adding a new nodepool of 6 nodes with 4 vCPUs/node (6×4=24 vCPUs) = +24 vCPUs.

Total increase: 32 + 24 = 56 vCPUs.

Total vCPU usage: 92 + 56 = 148 vCPUs → within the 150 vCPU limit.

Thus, valid.

Extract Reference:

NKPA 6.10– “Cluster Sizing and Licensing”

Nutanix Kubernetes Platform Administration (NKPA) – Licensing Considerations

"The total number of vCPUs for all nodes (control planes and workers) must not exceed the licensed vCPU capacity of the NKP deployment."

This confirms thatOptions B and Dare the two valid approaches to expand the cluster while remaining compliant with licensing constraints.

The error message:

python

Copy

failed to list clusters: command "docker ps -a --filter label=io.x-k8s.kind.cluster --format '{{.Label "io.x-k8s.kind.cluster"}}'" failed with error: exit status 1

indicates that the command failed while attempting to listdockercontainers with the given filter. The kind tool (used for creating a bootstrap cluster) depends on Docker as the container runtime.

Root cause:

If Docker is not running or a compatible container runtime is not available (such as containerd), the kind tool cannot list or interact with the required containers, resulting in this error.

Key Reference:

“When creating bootstrap clusters, the kind tool requires Docker to be installed and running. If Docker is not running, errors will be encountered listing or interacting with containers.”

According to theNKPA 6.10 documentationand Nutanix licensing details, NKP Starter is bundled with theNCI Starterentitlement. This basic licensing tier includes essential capabilities for deploying and managing Kubernetes clusters within a Nutanix environment.

Key reference:

“NKP Starter is included with NCI Starter, providing foundational Kubernetes cluster lifecycle management features for small-scale or starter deployments.”

As per theNKPA 6.10 documentationunder “Day 2 Operations: Managing Applications”, the recommended procedure to enable an application (like NKP Insights) involves accessing the cluster’sApplication Dashboard. The NKP Insights application does not appear in the general category list if the cluster does not have the correct context or if the application category is not globally enabled.

The specific procedure to enable NKP Insights includes:

Navigate to theClusterssection from the left-side menu.

SelectView Detailsfor the target cluster (prod-01 in this case).

In theApplication Dashboardof that specific cluster, locate the NKP Insights application.

Click the three-dot menu (ellipsis) for NKP Insights and selectEnable.

The exhibit indicates an error during the creation of a bootstrap cluster using the nkp create bootstrap command in an air-gapped environment. The NKPA course explains that a bootstrap cluster is a temporary Kubernetes cluster used to initialize Cluster API (CAPI) components for provisioning the target NKP cluster. In an air-gapped environment, all required resources, including container images, must be available locally since there is no Internet access to pull them from public registries.

The most likely reason for the error is thatthe bootstrap cluster image needs to be loaded prior to creating the bootstrap cluster(Option B). The course specifies that in air-gapped deployments, the bootstrap cluster image (typically a kind or k3s image used by CAPI) must be pre-loaded into a local container registry or the bastion host before running nkp create bootstrap. This image is part of the Air-Gapped Bundle provided by Nutanix, which includes all necessary container images for NKP deployment. Without pre-loading this image, the nkp create bootstrap command fails because it cannot pull the required image.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “In an air-gapped NKP deployment, ensure the bootstrap cluster image (e.g., kindest/node) is loaded into a local registry or host before executing nkp create bootstrap, as the command requires this image to create the temporary cluster.” The engineer must extract the bootstrap image from the Air-Gapped Bundle, load it using docker load or similar, and configure the local registry to make it accessible during the bootstrap process.

Incorrect Options:

A. The CAPI provisioning method needs to be specified as nkp create bootstrap nutanix: The nkp create bootstrap command does not require a provisioning method like nutanix at this stage; the provider (e.g., CAPX for Nutanix) is specified during the actual cluster creation (nkp create cluster), not bootstrap creation.

C. The Ubuntu 22.04 OS image needs to be NIB-prepped prior to creating the bootstrap: The Ubuntu 22.04 image is for the target NKP cluster nodes, not the bootstrap cluster, which uses a pre-built image (e.g., kind). NIB-prepping this image is a later step.

D. The nkp create bootstrap command needs to be executed as root: While some commands may require elevated privileges, the NKPA course does not specify that nkp create bootstrap must be run as root. The error is more likely related to missing images in an air-gapped setup.

The NKPA course clarifies that NKP licenses are based on the number ofCPU coresin 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.

NKP Platform Applications (e.g., Rook Ceph, Prometheus, Fluent Bit) are pre-integrated tools that can be deployed to Kubernetes clusters within a workspace to provide services like storage, monitoring, and logging. The NKPA course specifies that to deploy a platform application to all clusters in a workspace from the command line, the engineer uses thenkp create appdeploymentcommand. This command creates an application deployment resource that targets the specified workspace and clusters.

The required parameters include theapplication ID(to identify the platform application), theversion(to specify the desired version of the application), and theNKP workspace(to define the scope of clusters). For example: nkp create appdeployment --app-id prometheus --version 2.30.0 --workspace fin-vd. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “Use the nkp create appdeployment command to deploy platform applications, specifying the application ID, version, and target workspace to apply the deployment across all clusters in that workspace.”

Incorrect Options:

B. nkp deploy platform-app: This is not a valid NKP command. The correct command is nkp create appdeployment.

C. nkp deploy app: This is not a recognized command in the NKPA documentation.

D. kubectl create appdeployment: kubectl interacts with Kubernetes resources, not NKP-specific platform applications.

The NKPA course details the deployment of an NKP Management cluster on AWS using the nkp install kommander command, which installs the Kommander component responsible for fleet management. For a testing environment with minimal resource usage, the engineer can optimize the installation process by adjusting parameters that control timeouts and initialization settings, reducing overhead and ensuring the deployment completes efficiently on smaller infrastructure.

The two relevant parameters are:

--wait-timeout (Option B): This parameter sets the maximum time the nkp install kommander command waits for the Kommander components to become ready. In a testing environment with minimal resources, components may take longer to start due to limited CPU and memory. Reducing the wait timeout (e.g., --wait-timeout=10m) ensures the command does not hang indefinitely, allowing the engineer to troubleshoot if needed. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “Use --wait-timeout with nkp install kommander to adjust the waiting period for component readiness, useful in low-resource environments.”

--init (Option D): This parameter initializes the Kommander installation with default settings optimized for minimal resource usage, suitable for a testing environment. It ensures that Kommander deploys with a lightweight configuration, reducing the resource footprint (e.g., fewer replicas, lower resource requests). The NKPA course notes: “The --init flag with nkp install kommander sets up a minimal configuration for testing purposes, minimizing resource usage on AWS.”

Incorrect Options:

A. --request-timeout: This parameter is not relevant to nkp install kommander. It is typically used for API request timeouts, not installation optimization.

C. --yaml: This parameter would specify a custom YAML configuration file, but the question asks for minimal resource usage, which is better achieved with --init for default lightweight settings.

TheNKPA 6.10 documentationconfirms thatVelerois the built-in backup and recovery solution provided as part of the NKP platform. It provides cluster-level and namespace-level backup, restore, and migration capabilities.

Exact extract from the documentation:

“Velero is the integrated, out-of-the-box backup and restore solution in NKP. It supports scheduled backups, disaster recovery, and application migration workflows.”

In an air-gapped NKP environment with no Internet access, a bastion host is a critical component for secure management. The NKPA course defines the primary purpose of a bastion host asproviding a secure point for creating and operating NKP clusters. The bastion host acts as a jump server, allowing administrators to securely access the isolated environment, manage cluster deployments, and perform operations like cluster creation, scaling, and upgrades without exposing the environment to external threats.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “In a dark site NKP deployment, a bastion host serves as a secure entry point for administrators to create, manage, and operate NKP clusters, ensuring isolation from external networks.” The bastion host is configured with SSH keys and tools like the NKP CLI to facilitate secure interactions with the cluster infrastructure.

Incorrect Options:

A. To store and manage sensitive data: The bastion host is not a storage system; its role is access and management, not data storage.

C. To serve as a load balancer: A bastion host does not perform load balancing; that role is handled by Kubernetes components like MetalLB or cloud-native load balancers.

D. To act as a firewall: While a bastion host enhances security, it is not a firewall. Firewalls are separate components in the network architecture.

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 emphasizes that NKP’s fleet management capabilities allow administrators to manage multiple Kubernetes clusters, including lightweight clusters on edge devices, by attaching them to an NKP workspace. With the NKP Ultimate license tier, the administrator has access to advanced fleet management features, including GitOps-based application deployment across attached clusters.

The most efficient way to lifecycle manage application deployments across the 30 edge devices is tocreate a new workspace and attach the 30 edge devices to this workspace using the Attach Cluster functionality(Option D). Once attached, NKP can use GitOps (via Flux) to push applications to all clusters in the workspace simultaneously, ensuring consistent deployment and lifecycle management. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “For managing edge devices with lightweight Kubernetes, attach the clusters to an NKP workspace using the Attach Cluster feature, enabling centralized application deployment and lifecycle management via GitOps.” The administrator can use the kubeconfig files to attach each cluster via the NKP UI or CLI (e.g., nkp attach cluster).

Incorrect Options:

A. Create a GitHub configuration for each device: This is manual and inefficient compared to NKP’s centralized GitOps management.

B. Create a script to automate deployment: Scripting is error-prone and lacks NKP’s built-in fleet management capabilities.

C. Delete lightweight Kubernetes and deploy new clusters: This is unnecessary, as NKP can manage existing clusters, including lightweight ones.

When mirroring the NKP bundle to a private registry, the recommended method is to use the nkp bundle push or similar commands with the--to-registryoption, specifying the target registry along with the credentials (--to-registry-username and --to-registry-password).

Key reference from documentation:

“Use the --to-registry flag along with --to-registry-username and --to-registry-password to push the NKP bundle to a private registry.”

The scenario describes an isolated environment in Antarctica, implying an air-gapped NKP deployment where the bastion host serves as the primary management point for deploying and managing NKP clusters without Internet access. The NKPA course outlines the essential tools that must be installed on a bastion host to facilitate NKP deployment and management in such environments.

The required programs arekubectlandnkp:

kubectl: This is the Kubernetes command-line tool used to interact with Kubernetes clusters, essential for managing cluster resources, debugging, and applying configurations during and after deployment.

nkp: The NKP CLI (nkp) is the primary tool for deploying, managing, and scaling NKP clusters, including creating bootstrap clusters, deploying clusters, and managing platform applications. In an air-gapped setup, the nkp CLI is critical for executing deployment commands using the Air-Gapped Bundle.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “For an air-gapped NKP deployment, ensure the bastion host has kubectl and the nkp CLI installed to manage the deployment process and interact with the resulting Kubernetes clusters.” These tools are sufficient for the engineer to deploy and operate NKP in an isolated environment.

Incorrect Options:

A. awscli and nkp: The awscli is specific to AWS environments, but the question does not specify AWS infrastructure. Additionally, in an isolated environment, awscli is less relevant without Internet access.

B. oc and kubectl: oc is the OpenShift CLI, not used for NKP deployments. NKP uses nkp CLI instead.

C. oc and az: az is the Azure CLI, and oc is for OpenShift—neither is relevant to NKP deployment.

The NKPA course explains that NKP’s monitoring stack includesPrometheusfor metrics collection and storage, andFluent Bitfor log collection and forwarding. To retain system resource utilization data over several months, the company must focus on Prometheus, as it is responsible for storing time-series metrics data, such as CPU, memory, and network utilization, which are critical for long-term trend analysis.

To handle the increased workload from the online retail application, the Platform Engineer should adjust Prometheus byincreasing its container resource limits and memory settingsto ensure it can process and store more metrics, andincreasing its storageto retain data for several months. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “For long-term metrics retention in NKP, scale the Prometheus deployment by increasing its resource limits (CPU and memory) and expanding its persistent storage to accommodate larger time-series data.” This involves editing the Prometheus deployment’s resource settings (e.g., via kubectl edit deployment) and updating the PersistentVolumeClaim (PVC) to allocate more storage.

Incorrect Options:

A. Adjust the number of replicas for Fluent Bit: Fluent Bit handles logs, not metrics. Increasing replicas does not address long-term metrics storage.

B. Adjust the number of replicas for Prometheus: Increasing replicas improves availability but does not directly address storage or resource needs for metrics retention.

C. Adjust the resource settings for Fluent Bit: Fluent Bit is for log collection, not metrics storage, and is not relevant for this use case.

The NKPA 6.10 documentation confirms that the proper method to customize application deployment (including disabling Velero) is by generating a configuration file using thenkp install kommander --initcommand. The file can then be modified to set custom specs and disable Velero, and finally deployed using the nkp install kommander command.

Exact extract:

“Generate a custom configuration file using --init, modify it for your specific environment (including disabling Velero), and deploy with the same nkp install kommander command.”

The NKPA course explains that deleting a workspace in NKP, especially after all associated clusters have been removed, is a straightforward process through the NKP UI. The correct method is to navigate to theGlobalview in the top menu bar, selectWorkspacesfrom the menu, locate the target workspace, click thethree-dot buttonnext to it, and selectDelete. This action removes the workspace and its associated configurations from NKP, ensuring a clean environment after the project is finished.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To delete an empty workspace in NKP, go to the Global view in the UI, select Workspaces, click the three-dot menu for the workspace, and choose Delete.” The course confirms that a workspace must be empty (no clusters or resources) before it can be deleted, which aligns with the scenario where the three clusters have already been removed.

Incorrect Options:

A & B. Run kubectl delete workspace: Both options are syntactically similar, but kubectl delete workspace is not a valid command in NKP. Workspaces are managed through the NKP UI or CLI (nkp), not directly via kubectl.

D. Ask a workspace user to delete the workspace: Workspace users typically lack permissions to delete workspaces; this action is reserved for administrators via the Global view.

A bastion host in a dark site environment serves as a secure entry point for managing the NKP deployment, providing access to the cluster infrastructure without direct Internet connectivity. The NKPA course outlines the prerequisites for preparing a Linux VM as a bastion host, focusing on secure access and time synchronization, which are critical for air-gapped Kubernetes deployments.

Get or create SSH Keys (Option B):The bastion host requires SSH keys to enable secure, passwordless access to the NKP cluster nodes and other infrastructure components (e.g., Nutanix AHV hosts). The NKPA course specifies that SSH keys must be generated or obtained and configured on the bastion host to facilitate secure communication during deployment and management tasks. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “For a bastion host in an NKP dark site deployment, ensure SSH keys are created or obtained to enable secure access to cluster nodes and infrastructure.” The engineer can generate SSH keys using ssh-keygen and distribute the public key to the target systems.

Enable NTP Service (Option D):Time synchronization is essential in Kubernetes clusters to ensure consistent logging, certificate management, and scheduling. In a dark site with no Internet access, the bastion host must be configured to synchronize time with an internal NTP (Network Time Protocol) server or act as an NTP server itself. The NKPA course emphasizes enabling the NTP service on the bastion host to maintain accurate time across the air-gapped environment. The NCP-CN 6.10 Study Guide notes: “Enable the NTP service on the bastion host to ensure time synchronization in a dark site NKP deployment, as Kubernetes requires accurate time for proper operation.” The engineer can enable NTP using commands like systemctl enable ntpd and configure it to use an internal time source.

Incorrect Options:

A. Install LDAP Server: LDAP is used for centralized authentication, but it is not a requirement for a bastion host in an NKP dark site deployment. The course focuses on SSH access instead.

C. Install Docker: While Docker is needed on Kubernetes nodes for container runtimes, the bastion host’s role is to provide secure access and management, not to run containers.

Continuous Deployment (CD) is the practice of automatically deploying new software releases across environments after a successful build and testing phase. In the context of NKP, enabling CD ensures that software changes are consistently and reliably rolled out to all clusters associated with a project, ensuring operational uniformity and rapid feature adoption.

The NKPA course specifies that the Nutanix Image Builder (NIB), used for creating custom machine images for NKP cluster nodes, supports specific Linux distributions that are compatible with Nutanix infrastructure and Kubernetes requirements. For NKP v2.12.x, the supported distributions for NIB areUbuntuandRocky Linux, as these are tested and optimized for NKP deployments, ensuring stability and compatibility with Cluster API (CAPI) and Nutanix AHV.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “NKP Image Builder (NIB) supports Ubuntu and Rocky Linux as base distributions for creating custom images for NKP cluster nodes, ensuring compatibility with Kubernetes and Nutanix infrastructure.” Ubuntu provides a widely-used, well-supported base with long-term support (LTS) versions, while Rocky Linux is a CentOS replacement that Nutanix has adopted for its reliability and enterprise focus, especially after CentOS 8’s end-of-life in 2021.

Incorrect Options:

B. Fedora: Fedora is not a supported distribution for NIB in NKP, as it is more suited for bleeding-edge development rather than production Kubernetes environments.

D. CentOS: CentOS 8 reached end-of-life in December 2021, and Nutanix has shifted to Rocky Linux as its replacement for NKP image building. The course does not list CentOS as a supported option for NIB in NKP v2.12.x.

The NKPA course highlights thatNKP Insightsis the platform’s integrated solution for observability and analytics, providing predictive analytics to detect current and future anomalies in Kubernetes clusters. NKP Insights leverages machine learning to analyze metrics, logs, and events, identifying performance issues and potential failures proactively. After deploying a new cluster, the administrator can enable NKP Insights as a platform application in the workspace to meet the predictive analytics requirement.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “NKP Insights provides predictive analytics and anomaly detection for Kubernetes clusters, enabling administrators to monitor and optimize cluster performance.” This is deployed via the NKP UI or CLI by enabling the Insights application in the workspace.

Incorrect Options:

B. NCM Intelligent Ops: Nutanix Cloud Manager (NCM) Intelligent Ops is for broader infrastructure management, not Kubernetes-specific analytics.

C. Nutanix Pulse: Pulse is a telemetry service for Nutanix support, not for analytics.

D. NKP AI Navigator: This is not a recognized NKP component in the NKPA documentation.

Comprehensive and Detailed Explanation:

Both the Konvoy Image Builder (KIB) and the Nutanix Image Builder (NIB) are included tools used to create and manage custom OS images suitable for NKP deployments. KIB is responsible for building images that conform to the standards required by Konvoy-based environments, while NIB is designed for direct integration with the Nutanix AHV infrastructure. These tools support automated preparation, hardening, and upload of images to the appropriate repositories.

Attaching an existing Amazon EKS cluster to NKP for fleet management involves integrating the cluster into NKP’s management plane, which requires specific preparatory steps. The NKPA course outlines that the first step is tocreate a service account with cluster-admin permissionsin the EKS cluster. This service account is used by NKP to authenticate and manage the cluster, enabling operations like monitoring, scaling, and application deployment.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide explains: “To attach an external Kubernetes cluster, such as Amazon EKS, to NKP, a service account with cluster-admin role bindings must be created to allow NKP to interact with the cluster’s API server.” The service account is configured with a token that NKP uses to authenticate requests. The NKPA course provides detailed steps, including creating the service account, assigning the cluster-admin ClusterRole, and generating a token for NKP integration. This step is critical to ensure NKP has the necessary permissions to manage the EKS cluster.

Incorrect Options:

A. Configure a ConfigMap according to EKS configuration: While ConfigMaps may be used for specific configurations, they are not the first step for attaching an EKS cluster. The NKPA course prioritizes service account creation.

C. Configure HAProxy to get connected to EKS clusters: HAProxy is a load balancer, not required for attaching EKS clusters to NKP. EKS uses AWS-native load balancers, and NKP connects via the Kubernetes API.

D. Deploy cert-manager in the EKS clusters: Cert-manager is used for certificate management, not a prerequisite for attaching EKS clusters. The NKPA course does not list it as a required step.

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 --ami --kubernetes-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 --cluster-name --kubernetes-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.

The output indicates that an AppDeployment resource named grafana-logging was created in the kommander-default-workspace namespace, which corresponds to an NKP workspace. The NKPA course explains that NKP Platform Applications, such as Grafana Logging, are deployed using the nkp create appdeployment command. This command creates an AppDeployment resource that deploys the specified application (e.g., Grafana Logging) across all clusters in a workspace.

The command inOption A, nkp create appdeployment grafana-logging --app grafana-logging-6.57.4 --workspace default-workspace, matches the output:

grafana-logging is the name of the AppDeployment.

--app grafana-logging-6.57.4 specifies the application and version.

--workspace default-workspace targets the workspace, which corresponds to the namespace kommander-default-workspace in the output (the kommander- prefix is a standard NKP namespace convention).

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To deploy a platform application like Grafana Logging, use nkp create appdeployment --app - --workspace , which creates an AppDeployment resource in the workspace namespace.” This command aligns with the output provided.

Incorrect Options:

B. export WORKSPACE_NAMESPACE and nkp create package-bundle: There is no nkp create package-bundle command in NKP for deploying applications. The correct command is nkp create appdeployment.

C. kubectl get appdeployment: This retrieves the status of an AppDeployment, not creates it. The output indicates creation, not retrieval.

D. kubectl get helmreleases: This retrieves HelmRelease resources, not AppDeployments, and does not create the Grafana Logging deployment.

The NKPA course specifies the supported operating systems for NKP clusters deployed using the Nutanix provisioning method (CAPX), which leverages Cluster API for Nutanix (CAPX) to provision clusters on Nutanix AHV. The supported OS platforms for CAPX areRocky LinuxandUbuntu, as these distributions are tested and optimized for Nutanix infrastructure and Kubernetes requirements.

Rocky Linux is a CentOS replacement adopted by Nutanix after CentOS 8’s end-of-life in 2021, providing a stable, enterprise-grade OS. Ubuntu, particularly LTS versions like 20.04 or 22.04, is widely supported due to its compatibility with Kubernetes and Nutanix AHV. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “When deploying NKP with the Nutanix provisioning method (CAPX), the supported OS platforms are Rocky Linux and Ubuntu, ensuring compatibility with Nutanix AHV and Kubernetes.” These OS images are typically prepared using NKP Image Builder (NIB) to include necessary components like kubeadm and containerd.

Incorrect Options:

A. CentOS and Rocky Linux: CentOS 8 is no longer supported post-2021, and Nutanix has shifted to Rocky Linux.

C. Flatcar, Rocky Linux, and Ubuntu: Flatcar Container Linux is not a supported OS for CAPX in NKP deployments.

D. CentOS and Ubuntu: CentOS is not supported, as noted above.

The documentation confirms that when a new license is activated to upgrade to a higher tier, users mustlog out and log back infor 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.”