Nutanix NCP-CN Exam Dumps

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.

Two true statements regarding deploying NKP on Azure Kubernetes Service (AKS) Infrastructure are:

• Statement 1: NKP can be deployed as a workload cluster on existing AKS infrastructure (using AKS as the underlying Kubernetes platform)
• Statement 2: AKS clusters attached to NKP require the NKP management agent to be installed for centralized management and control

Additional true statements may include:

• Custom VM images can be used for AKS node pools when deploying NKP
• NKP requires appropriate Azure permissions and service principals for AKS integration
• Networking and security group configurations must be properly set up for AKS clusters in NKP
• AKS cluster registration requires valid kubeconfig and network connectivity to the NKP management cluster

False statements to avoid:

• NKP can only use default Azure-provided images (False - custom images are supported)
• AKS requires special AKS-only licensing separate from NKP licensing (False - standard NKP licensing applies)
• NKP cannot manage existing AKS clusters (False - attachment and management are supported)

When using Secure Tunnel to attach clusters with network restrictions, firewall rules must allow outbound HTTPS (port 443) traffic from the attached cluster network to the NKP management cluster. Specifically, the firewall rules should allow: (1) Outbound TCP port 443 (HTTPS) for secure communication between the Secure Tunnel agent on the attached cluster and the NKP management cluster; (2) DNS resolution to enable the attached cluster to reach the NKP management cluster by hostname; (3) The specific IP address or domain name of the NKP management cluster's Secure Tunnel endpoint. The Secure Tunnel creates an encrypted, outbound-only connection from the attached cluster to the management cluster, eliminating the need for inbound firewall access. This approach allows clusters in restricted networks to be managed by NKP without exposing them to inbound network access.

To control the standard configuration for both production and development environments across all clusters, the company should use NKP's Fleet Management capabilities combined with Kustomization or FluxCD. However, the most appropriate approach in NKP v2.x is to use Workspaces and Project or Workspace-level policies to enforce standardized configurations. Alternatively, they can leverage GitOps through FluxCD to maintain declarative configurations across all clusters, or use Management Clusters with standardized cluster profiles/templates that define baseline configurations for both production and development clusters. The NKP Ultimate license enables advanced fleet management features that allow centralized policy enforcement and configuration management.

To resolve the performance issue where worker VMs are running out of CPU and memory, the Platform Engineer could: (1) Scale up the worker nodes by increasing vCPU and RAM resources allocated to each VM, (2) Scale out by adding additional worker nodes to distribute the workload across more nodes, (3) Optimize pod resource requests and limits to ensure workloads are using resources efficiently, (4) Remove unnecessary or idle workloads consuming resources, or (5) Implement resource quotas and pod disruption budgets to manage resource allocation. Given that all 4 workers are experiencing resource exhaustion, scaling out (adding more nodes) would be the most immediate solution, though scaling up individual nodes may also be necessary. Additionally, the engineer should investigate what workloads are consuming resources and whether they are properly configured with appropriate requests and limits.