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

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 details the process of creating an NKP cluster on vSphere using the NKP CLI, including the configuration of multiple node pools with specific worker node counts and CPU settings. The correct approach involves creating the cluster with the initial node pool and then adding additional node pools separately.

The steps inOption Aalign with this process:

nkp create cluster vsphere --worker-replicas 6 --worker-cpus 10: This command creates the NKP cluster on vSphere with the first node pool, consisting of 6 worker nodes, each with 10 CPUs.

nkp create nodepool vsphere --worker-replicas 3 --worker-cpus 8: This adds the second node pool to the cluster with 3 worker nodes, each with 8 CPUs.

nkp create nodepool vsphere --worker-replicas 3 --worker-cpus 6: This adds the third node pool with 3 worker nodes, each with 6 CPUs.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To create an NKP cluster with multiple node pools on vSphere, use nkp create cluster vsphere to define the first node pool, then add additional node pools with nkp create nodepool vsphere, specifying --worker-replicas and --worker-cpus for each pool.” This method ensures precise control over each node pool’s configuration.

Incorrect Options:

B: The second nkp create nodepool command uses --replicas and --cpus, which are not the correct flags. The NKPA course specifies --worker-replicas and --worker-cpus.

C: The --node-pools, --worker-replicas 6,3,3, and --worker-cpus 10,8,6 flags are not supported in a single nkp create cluster command. Node pools must be created separately.

D: There is no nkp create nodepools command; the correct command is nkp create nodepool. Additionally, --replicas and --cpus are incorrect flags.

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.

As outlined in theNKPA 6.10 documentationunder "Customizing Resource Requests and Limits for Logging," to override the default resource values for the logging operator, a ConfigMap named logging-operator-logging-overrides in the kommander namespace is used. The values.yaml in the ConfigMap should precisely define fluentd resource limits and requests in a valid YAML format.

The correct YAML format is:

yaml

Copy

apiVersion: v1

kind: ConfigMap

metadata:

name: logging-operator-logging-overrides

namespace: kommander

data:

values.yaml: |

fluentd:

resources:

limits:

cpu: 4

memory: 4Gi

requests:

cpu: 4

memory: 4Gi

This ensures that the desired CPU and memory resources are correctly applied for the fluentd daemon, avoiding parsing errors and meeting the high-demand logging needs.

TheNKPA 6.10 documentationclarifies that when creating a workload cluster using the nkp create cluster command, specifying the target workspace (namespace) is critical for properly associating the workload cluster with that workspace in the NKP UI. If the --namespace parameter is omitted, the cluster is provisioned in the default workspace, not in the intended workspace (in this case, code-green).

Key documentation excerpt:

“If you do not specify the workspace (namespace) using the --namespace parameter when creating a cluster, the cluster will be created in the default workspace. It will not appear in custom workspaces until manually assigned.”

In an air-gapped NKP installation, the engineer starts with the NKP Air-Gapped Bundle, a tarball containing all necessary components (e.g., container images, binaries, configuration files) for deployment without Internet access. The NKPA course specifies that the first step is to extract this bundle on the bastion host to make its contents available for the installation process. The correct command istar -xzvf nkp-air-gapped-bundle_v2.12.0_linux_amd64.tar.gz, which extracts the bundle into a directory, revealing the container images, CLI tools, and other resources needed for the deployment.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To begin an air-gapped NKP installation, first extract the NKP Air-Gapped Bundle using tar -xzvf .tar.gz on the bastion host to access the installation artifacts.” After extraction, the engineer can proceed with loading container images (e.g., using docker load) and running NKP CLI commands to deploy the cluster, ensuring all dependencies are available locally.

Incorrect Options:

A. nkp push bundle --bundle: This is not a valid command. The bundle must be extracted before its contents can be used.

B. docker load -i konvoy-bootstrap-image-v2.12.0.tar: Loading the bootstrap image is a subsequent step after extracting the bundle, which contains this image tarball.

D. nkp create cluster nutanix: This command creates a cluster but cannot be run until the bundle is extracted and its images are loaded.

According to theNKPA 6.10 documentation, theFIPS Compliant Build featureis exclusively available forEnterprise tierlicensing. This ensures compliance with NIST security standards and provides hardened cryptographic capabilities throughout the Kubernetes cluster stack.

Exact extract from documentation:

“The FIPS-compliant build feature is included in the NKP Enterprise tier, enabling deployments in environments that require strict security compliance.”

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.

The error states:

lua

Copy

Could not find or access '/home/.../nkp-image-builder-.../playbooks/.../artifacts/1.29.6_ubuntu_22.04_x86_64.tar.gz'

This indicates that theOS package bundle(artifacts/1.29.6_ubuntu_22.04_x86_64.tar.gz) has not been created or is missing. Creating the OS package bundle is a prerequisite step in the NIB workflow.

Key Reference:

Nutanix Kubernetes Platform Administration (NKPA) 6.10 – “Creating OS Package Bundles for NIB”

NCP-CN 6.10 Study Guide – “NIB Preparation Prerequisites”

=======

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.