NCP-CN Dumps with Practice Exam Questions Answers

As per theNKPA 6.10 documentationunder “Application Backup and Recovery with Velero,” Velero is the out-of-the-box backup and restore solution integrated with NKP. To schedule application backups at a specific frequency (in this case, every six hours, equivalent to four times daily), the recommended approach is to use theVelero CLIto create a backup schedule.

The procedure involves:

Using the Velero CLI to create ascheduled backuptargeting the specificKubernetes namespace(victory-finance) rather than the entire workspace.

Specifying the frequency as --schedule="0 */6 * * *" (every six hours).

Providing the cluster’s kubeconfig for authentication.

Exact extract from the documentation:

“Velero’s CLI can be used to create backup schedules for application-specific workloads. Use the namespace parameter to target the namespace where the applications are deployed, and set the cron-like schedule to the desired frequency.”

TheNKPA 6.10 documentationoutlines that in air-gapped environments where default pod network CIDR conflicts exist, the cluster manifest (created via the nkp create cluster command) should be updated to specify an alternate, non-conflicting pod CIDR block range before deployment.

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 Nutanix Kubernetes Platform (NKP) uses the Kubernetes Image Builder (KIB) or Nutanix Image Builder (NIB) to create custom machine images for NKP management and worker nodes. These images are tailored to include specific versions of Kubernetes, container runtimes (e.g., containerd), and other dependencies. The NKPA course specifies that KIB relies on Ansible playbooks to configure the image, and the versions of packages like Kubernetes and containerd are defined in Ansible configuration files.

The correct location to verify the package versions isansible/group_vars/all/defaults.yaml. This file contains the default variables used by Ansible during the image-building process, including the versions of Kubernetes and containerd. For example, it may include entries like kubernetes_version: 1.30.5 and containerd_version: 1.7.22. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To ensure the correct versions of Kubernetes and containerd are used in KIB, check the ansible/group_vars/all/defaults.yaml file, which specifies the package versions for the image build.” The engineer can review and modify this file to confirm that the security team’s authorized versions (Kubernetes 1.30.5 and containerd 1.7.22) are being used.

Incorrect Options:

A. config/pulumi/vars/pulumi.kib.config: Pulumi is an infrastructure-as-code tool, but it is not used by KIB for specifying package versions. The NKPA course does not reference this file.

B. terraform/vars/default/terraform.tfvars: Terraform is used for infrastructure provisioning, not for defining software versions in KIB images.

D. The custom image's .env file: KIB does not use a .env file for version configuration; Ansible variables are used instead.

As per theNKPA 6.10 documentationunder “NKP Insights Prerequisites”, one of the essential requirements for deploying NKP Insights is thatcert-manageris installed and properly configured in the target workload cluster. Cert-manager provides the necessary certificates for secure communication and observability between the cluster components and the NKP Insights platform.

The documentation specifies:

“NKP Insights requires cert-manager to be installed on the target workload cluster. If cert-manager is not enabled, the cluster will be shown as unavailable (grayed out) for NKP Insights deployment.”

Without cert-manager, the Insights operator cannot validate or securely deploy its components, resulting in the cluster being unavailable for selection during the Insights enablement process.