Free Nutanix Certified Professional - Cloud Native v7.5 NCP-CN Exam Questions

The NKP Platform Application component the company should be most concerned with adjusting is Prometheus, by increasing its storage retention and compute resources.

Why this is correct:

• Metrics Retention: Prometheus stores time-series metrics data; to retain several months of historical data, the data storage capacity must be significantly increased
• Data Volume Increase: With the new retail application workloads added to the cluster, Prometheus will collect substantially more metrics, requiring additional disk storage
• Resource Scaling: Prometheus itself (CPU and memory) needs to be scaled up to handle the increased volume of metrics collection and queries across multiple workloads
• Long-Term Trending: To see system resource utilization trends over several months, retention policies must be configured to keep data for that duration
• Monitoring Stack Capacity: Prometheus is the core component of the monitoring stack that handles metrics storage and retrieval

Prometheus is the critical component to adjust when scaling monitoring infrastructure for increased workload and longer data retention requirements.

When deploying NKP in AWS for testing with minimal resources, the Cloud Engineer should specify parameters during the nkp install kommander command that reduce resource consumption. These typically include flags like --minimalist (or --test-mode) to deploy a minimal Kommander configuration, and --skip-optional-services (or similar) to skip non-essential services. These parameters reduce the number of replicas, disable redundancy, and skip optional components, significantly lowering AWS infrastructure costs.

NKP comes bundled with two key tools for custom OS image creation and deployment: Image Builder (used to create custom OS images) and Cluster API (used to manage the placement and provisioning of these images into the respective infrastructure providers). Image Builder handles the creation and customization of OS images, while Cluster API orchestrates their deployment across different platforms like Nutanix AHV and AWS, placing them into the appropriate image repositories for each infrastructure.

When deploying an NKP bootstrap cluster in an air-gapped environment with CAPX (Nutanix CAPI provisioner), an error during bootstrap cluster creation likely indicates one of several issues: (1) The required container images for NKP and CAPI components are not available in the air-gapped environment's private registry; (2) The Ubuntu 22.04 base image has not yet been imported into Prism Central or made available; (3) Network connectivity issues prevent the bootstrap cluster from pulling required images from the private registry; (4) The NKP cluster configuration references images that haven't been mirrored to the private registry; (5) Credentials or authentication issues prevent access to the private registry; (6) The Nutanix infrastructure (Prism Central) connectivity or API access is not properly configured. The engineer should verify that all required NKP container images have been downloaded and pushed to the private registry before attempting bootstrap cluster creation. The NIB-prep of the Ubuntu image should complete successfully before bootstrap cluster creation begins.

To mitigate the problem where ApplicationB is consuming the majority of cluster resources and affecting ApplicationA's performance, the IT team should implement Resource Quotas and Limit Ranges.

Why this is correct:

• Resource Quotas enforce aggregate resource constraints per namespace or team, preventing one team from monopolizing cluster resources
• Limit Ranges restrict the CPU and memory that individual pods can request or consume
• Together, these mechanisms ensure fair resource allocation across teams and prevent one application from starving others of resources

This is a Kubernetes best practice for multi-tenant environments where multiple teams share a cluster.

When deploying a Kubernetes cluster that requires predictive analytics for detecting anomalies, the administrator should deploy Nutanix's monitoring and observability service (or equivalent anomaly detection solution) after cluster provisioning. This solution provides machine learning-based capabilities to detect current and future anomalies in the cluster, workloads, and infrastructure. It integrates with NKP's observability stack and provides predictive insights for proactive cluster management.

The NIB (Node Image Build) preparation failure is likely caused by the hardened Ubuntu 22.04 image not meeting NKP's requirements. Common causes include: SELinux being enabled when NKP expects it disabled, missing or incompatible kernel modules, missing system dependencies, or security hardening configurations that conflict with NKP's needs. The engineer should verify that the hardened image includes all required dependencies and that security configurations (like SELinux) are aligned with NKP's node requirements.

The purpose of preparing machine images for NKP through the NIB (Nutanix Image Builder) or KIB (Kubernetes Image Builder) process is to create customized, pre-configured OS images that can be used to provision NKP nodes. These builders allow engineers to: include custom packages, security patches, and configurations, enable FIPS compliance, install additional drivers or kernel modules, pre-stage container images, and ensure consistency across all nodes. Using pre-built images accelerates cluster deployment, reduces configuration drift, improves security by including hardening measures, and ensures compliance requirements are met. The resulting images can be stored and reused across multiple cluster deployments.

To delete an NKP cluster along with its nodes and associated applications, the administrator uses the nkp delete cluster command followed by the cluster configuration file. In this case, the correct command is nkp delete cluster temp-ecommerce.conf. This command will remove the entire cluster infrastructure, associated nodes, and all deployed applications, provided the cluster configuration file is available for reference.