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.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Application Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Flux Documentation: https://fluxcd.io/docs/components/helm

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.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Fleet Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Attaching External Clusters.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Amazon EKS Documentation: https://docs.aws.amazon.com/eks

When attaching an Amazon EKS cluster to NKP for fleet management, persistent volume (PV) errors during application deployments often indicate issues with storage configuration. The NKPA course identifies a common cause: the absence of a default StorageClass. Kubernetes requires a default StorageClass to automatically provision PVs for PersistentVolumeClaims (PVCs) when none is specified. Without a default, applications fail to bind PVCs, resulting in deployment errors.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "For attached EKS clusters, ensure a default StorageClass is configured to support dynamic provisioning of persistent volumes. Review existing StorageClasses and set one as default using the storageclass.kubernetes.io/is-default-class annotation." The engineer should run kubectl get storageclass to list available StorageClasses, verify their configurations, and set one as default by patching it with kubectl patch storageclass <name> -p '{"metadata": {"annotations":
{"storageclass.kubernetes.io/is-default-class":"true"}}}'. In EKS, the default StorageClass is typically backed by Amazon EBS (e.g., gp2 or gp3).
Incorrect Options:
* A. The storage appliance is having issues: This assumes a hardware issue, which is not indicated by PV errors. The NKPA course suggests checking Kubernetes configurations first.
* B. There is no compatible storage: EKS supports EBS and EFS, which are compatible with NKP. The issue is likely configuration, not compatibility.
* D. There could be a misconfiguration in the ConfigMap: ConfigMaps are not directly related to PV provisioning. The NKPA course points to StorageClass issues for PV errors.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Fleet Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Storage Configuration.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Amazon EKS Storage Documentation: https://docs.aws.amazon.com/eks

The NKPA course highlights that NKP Insights is 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.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Observability and Insights.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

The NKPA course addresses resource contention in Kubernetes clusters, where one application (e.g., ApplicationB) consumes excessive resources, impacting others (e.g., ApplicationA). To mitigate this, the course recommends implementing Quotas and Limit Ranges.
* Resource Quotas restrict the total amount of CPU, memory, and other resources a namespace can consume, ensuring fair resource allocation across teams.
* Limit Ranges set minimum and maximum resource limits for individual pods and containers within a namespace, preventing any single application from monopolizing resources.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To prevent resource contention in NKP clusters, apply Resource Quotas to limit namespace resource usage and Limit Ranges to enforce pod and container resource boundaries." For example, the administrator can create a ResourceQuota to cap ApplicationB's namespace resource usage and a LimitRange to restrict its pod resource requests/limits, ensuring ApplicationA has sufficient resources.
Incorrect Options:
* B. Setting up Network Policies: Network Policies control network traffic, not resource usage.
* C. Configuring RBAC: RBAC manages access permissions, not resource allocation.
* D. Implementing Continuous Deployment (CD): CD automates deployments but does not address resource contention.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Resource Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Kubernetes Documentation: https://kubernetes.io/docs/concepts/policy/resource-quotas