A company has been modernizing on cloud-native platforms for the past few years and has been running some small consumer support utilities on their production NKP cluster. After a thorough testing and QA cycle with simulated workloads on a development cluster, the company is ready to bring their online retail application into the fold. While they have sufficient system resources to scale the NKP cluster properly from a performance standpoint, they also want to ensure they properly scale their monitoring stack's resource settings to retain a sufficient amount of data to see how overall system resource utilization trends for the NKP cluster over several months' time with the added workloads. Which NKP Platform Application component should the company be most concerned with adjusting, and how should their Platform Engineer adjust it?
Correct Answer: D
The NKPA course explains that NKP's monitoring stack includes Prometheus for metrics collection and storage, and Fluent Bit for 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 by increasing its container resource limits and memory settings to ensure it can process and store more metrics, and increasing its storage to 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. : Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Monitoring and Platform Applications. Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations. Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Prometheus Documentation: https://prometheus.io
NCP-CN Exam Question 7
A Platform Engineer sees no insight in all workspaces, and it is a critical feature to control all the alerts on all company's Kubernetes clusters. What does the engineer need to do to begin generating NKP Insights?
Correct Answer: C
The exhibit shows an NKP UI message stating "No insights identified," indicating that NKP Insights, the platform's predictive analytics and observability feature, is not active. The NKPA course explains that NKP Insights is a platform application that provides anomaly detection and alerting for Kubernetes clusters but requires deployment and configuration to generate insights. The correct approach (Option C) involves two steps: * Create a persistent volume claim (PVC) and assign it to nkp-insights: NKP Insights requires persistent storage to save logs, metrics, and historical data for analysis. The course specifies that a PVC must be created to provide this storage, ensuring the application can retain data for generating insights. * Install nkp-insights with nkp create appdeployment nkp-insights --app nkp-insights-1.2.2 -- workspace kommander-workspace: This command deploys the NKP Insights application across all clusters in the specified workspace (kommander-workspace). The --app flag specifies the application version, and the deployment ensures that insights are generated for all clusters in the workspace. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To enable NKP Insights, create a PersistentVolumeClaim for storage and deploy the application using nkp create appdeployment nkp-insights -- app <version> --workspace <workspace-name> to begin generating insights across clusters." This aligns with the need to control alerts across all company clusters, as NKP Insights provides centralized observability. Incorrect Options: * A. Acquire the NKP Insights Add-on license: NKP Insights is a platform application included in higher-tier licenses (e.g., NKP Ultimate), not a separate add-on. The course does not indicate a separate license requirement. * B. Install nkp-insights in every cluster with kubectl apply: This method is manual and inefficient. NKP's appdeployment command automates deployment across all clusters in a workspace. : 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
NCP-CN Exam Question 8
After selecting the Production workspace and selecting View Details for the cluster prod-01, a Platform Engineer wanted to enable the NKP Insights application. This application is under the Observability category, but this category doesn't appear in the list. Which action should the engineer take to be able to deploy the NKP Insights application in the Kubernetes cluster for this workspace?
Correct Answer: D
As per the NKPA 6.10 documentation under "Day 2 Operations: Managing Applications", the recommended procedure to enable an application (like NKP Insights) involves accessing the cluster's Application 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 the Clusters section from the left-side menu. * Select View Details for the target cluster (prod-01 in this case). * In the Application Dashboard of that specific cluster, locate the NKP Insights application. * Click the three-dot menu (ellipsis) for NKP Insights and select Enable. Reference: Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Enabling Applications in a Specific Cluster" NCP-CN 6.10 Study Guide - "Application Deployment in Workspaces" This exact approach ensures that NKP Insights is deployed in the proper cluster-level context, circumventing the missing "Observability" category in the global Applications view. =======
NCP-CN Exam Question 9
A company has a new DevOps team that needs to be provided cloud native computing resources. This team will need to have access to multiple NKP clusters for development, testing and validation of an in-house application. However, they also need to be restricted to a specific namespace and a consistent level of access across the clusters within this namespace so that they do not adversely impact the environment of other user groups or the clusters themselves. As a part of this consideration, the new team also needs to be limited to the amount of storage, CPU and memory they can consume on the clusters. A Platform Engineer has been tasked with providing the appropriate level of access to the team on these multiple NKP clusters. How should the engineer best accomplish this task?
Correct Answer: C
The NKP documentation recommends using a combination of RBAC assignments and exported manifests to manage access across multiple clusters. By exporting the role assignments to YAML, the engineer can consistently apply these settings across the different environments, ensuring the new team has the necessary resources and limits. This approach is especially useful for environments with multiple clusters and standardized configurations. References: Nutanix Kubernetes Platform Administration Guide - RBAC Management Across Clusters
NCP-CN Exam Question 10
Some time ago, an EKS cluster was attached to be managed with NKP (Fleet Management). Now, a Platform Engineer has been asked to disconnect the EKS cluster from NKP for licensing reasons. After disconnecting the cluster, the developers realized that application changes are still being reflected in the EKS cluster, despite the fact that the EKS cluster was successfully detached from NKP. How should the engineer resolve this issue?
Correct Answer: D
When an Amazon EKS cluster is attached to NKP for fleet management, NKP uses GitOps principles, leveraging Flux (a GitOps operator) to synchronize application deployments and configurations from a management Git repository to the attached cluster. The NKPA course explains that detaching a cluster from NKP removes it from the NKP management plane, but the Flux installation on the cluster may continue to reconcile with the Git repository, causing application changes to persist post-detachment. To resolve this, the engineer must manually disconnect the Flux installation by suspending the Git repository reconciliation. The correct command, as per the NKPA course, is: kubectl -n kommmander-flux patch gitrepo management -p '{"spec":{"suspend":true}}' --type merge. This command suspends Flux's synchronization with the management Git repository, stopping further application updates. The Nutanix Cloud Native (NCP- CN) 6.10 Study Guide states: "After detaching an external cluster from NKP, the Flux GitOps operator may continue to apply changes unless its GitRepo resource is suspended using kubectl patch in the kommmander- flux namespace." Incorrect Options: * A. Forcefully detach EKS cluster: The --force flag is not a standard option for the nkp detach cluster command, and forceful detachment does not address the Flux reconciliation issue. * B. Detached cluster must also be deleted from NKP: The cluster is already detached, and deletion is not necessary to stop GitOps updates. The issue lies with Flux, not NKP's state. * C. Developers must have some bad configuration: The issue is not with developer configurations but with Flux's ongoing synchronization, as explained in the NKPA course. : Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Fleet Management and GitOps. Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Detaching Clusters. Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Flux Documentation: https://fluxcd.io
