Nutanix Certified Professional - Cloud Native v6.10 NCP-CN Exam Questions
A company recently deployed NKP. A Platform Engineer was asked to attach the existing Amazon EKS. A workspace and project were created accordingly, and resource requirements were met. What does the engineer need to do first to prepare the EKS clusters?
Correct Answer: B
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 to create a service account with cluster-admin permissions in 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.
Prior to implementing NKP, a company had created a number of Kubernetes (K8s) clusters using kubeadm. While they are deploying new managed clusters via NKP, the company does not wish to migrate workloads from these pre-existing native K8s clusters over to new NKP clusters just yet.
What are the requirements to have these clusters attached to their NKP management cluster?
Correct Answer: B
As per the NKPA 6.10 documentation , the primary requirement for attaching external (self-managed) Kubernetes clusters to NKP is network connectivity . Specifically, the NKP management cluster must be able to communicate with the Kubernetes API server and relevant services of the target cluster. This allows NKP to collect metrics, perform health checks, and manage the attached cluster through Kommander and associated tools.
Exact extract:
“For attaching existing Kubernetes clusters, ensure the NKP management cluster can reach the Kubernetes API server of the target cluster and that the kubeconfig used has sufficient permissions.”
There is no requirement that the Kubernetes versions be exactly matched or within N-1, nor that an NKP admin account be directly established on the target clusters; the connectivity and valid kubeconfig file are the essential requirements.
Which CAPI provisioning method requires creating an inventory file of the servers to become NKP nodes?
Correct Answer: C
According to the NKPA 6.10 documentation , the Pre-provisioned infrastructure provider (CAPPP) requires the user to provide an inventory file of the servers that will become the cluster nodes. This inventory file contains connection information (IP addresses, credentials, etc.) for each pre-provisioned node, enabling the Cluster API to connect and configure these servers directly during cluster creation.
A Platform Engineer is getting started with NKP and has created a bastion host with all needed prerequisites.
How should the engineer install Kommander?
Correct Answer: D
As per the NKPA 6.10 documentation , the standard and supported approach for installing Kommander on an NKP cluster is using the NKP CLI . The CLI provides commands for deploying Kommander and associated platform components as part of the cluster lifecycle management workflow.
Key Reference:
“The recommended approach to deploy Kommander is by using the nkp CLI, which ensures compatibility and streamlined installation with the rest of the Nutanix Kubernetes Platform stack.”
A technology company has decided to migrate its infrastructure to NKP to improve the scalability and management of its applications. After a successful initial implementation, the operations team faces a new challenge of validating the HelmReleases to ensure that all applications are running correctly and avoid problems in production. Which command should the company execute to know the right status of their HelmReleases?
Correct Answer: B
NKP uses Helm and Flux for application deployment, where applications are managed as HelmReleases , a custom resource that defines Helm chart deployments. The NKPA course explains that to validate the status of HelmReleases, administrators can use the kubectl command to query these resources. The correct command is kubectl get helmreleases -n ${PROJECT_NAMESPACE} , which lists all HelmReleases in the specified project namespace, showing their status (e.g., Ready, Failed) and other details like chart version and reconciliation status.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To check the status of HelmReleases in NKP, use kubectl get helmreleases -n < namespace > to view the current state of application deployments managed by Flux.” This command helps the operations team verify that applications are running correctly and identify any issues in production.
Incorrect Options :
A. kubectl get namespaces : This lists namespaces, not HelmReleases or their status.
C. kubectl edit helmreleases -n ${PROJECT_NAMESPACE} : This edits HelmRelease resources, not displays their status.
D. kubectl apply -f fluent-bit-overrides.yaml : This applies a configuration for Fluent Bit, unrelated to HelmRelease status.