Get Aug-2026 Download Latest & Valid Questions For Nutanix NCP-CN exam
Ensure Success With Updated Verified NCP-CN Exam Dumps
NEW QUESTION # 62
A Platform Engineer is deploying a new NKP cluster that has internet connectivity. Now, a Cloud Administrator and Security Administrator are discussing the security of communications between the NKP Kubernetes cluster and the container registry. The engineer proposes to have an on-prem private registry.
What is the most significant reason that the engineer should create a private registry instead of configuring a secure connection between the NKP cluster and Github (SaaS)?
- A. Private registry provides security and privacy.
- B. NKP requires specific registry versions.
- C. NKP cannot connect to public clouds.
- D. Private registry license is included with NKP.
Answer: A
Explanation:
The primary benefit of a private registry is to ensure security and privacy for container images, especially when dealing with sensitive data and compliance requirements (such as financial or government use cases).
While secure connections to public registries like DockerHub or GitHub container registries are possible, using a private registry ensures full control over image access and auditing.
Key reference:
"Private registries ensure images remain within the security and compliance boundaries of the enterprise, avoiding potential risks associated with public SaaS registries." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Private Registry Use Cases and Benefits" NCP-CN 6.10 Study Guide - "Security and Compliance Considerations"
NEW QUESTION # 63
A Kubernetes administrator needs to deploy a new Kubernetes cluster into a new workspace. This cluster requires a predictive analytics solution that detects current and future anomalies. Which option does the administrator need to deploy after the cluster is ready?
- A. Nutanix Pulse
- B. NCM Intelligent Ops
- C. NKP Insights
- D. NKP AI Navigator
Answer: C
Explanation:
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
NEW QUESTION # 64
A company has different Kubernetes clusters for different business units. Every business unit has separate Kubernetes clusters for production and development because the software deployed in production is different than development. Now, all production clusters for all business units are standardized and all clusters for development are standardized as well.
The company recently acquired NKP Ultimate licenses for all Kubernetes clusters.
How can the company control the standard configuration for both environments in all clusters (production and development)?
- A. Install Flux in every Kubernetes cluster with the appropriate kustomize.yaml, with nkp install flux -- kustomize=kustomize.yaml --kubeconfig=<cluster>.conf
- B. Create new Kubernetes clusters for production and development with NKP for every business unit.
- C. Configure a production workspace and a development workspace and attach each Kubernetes cluster to the corresponding workspace.
- D. Install Flux in every Kubernetes cluster and configure the appropriate kustomize.yaml in every Kubernetes cluster.
Answer: C
Explanation:
The NKPA 6.10 documentation confirms that workspaces in NKP are used to logically group and standardize configurations across multiple clusters. By creating a production workspace and a development workspace, the organization can control and enforce standardized configurations and policies for all relevant clusters.
Exact extract:
"Workspaces provide logical separation for resources, configuration, and policy management across multiple clusters, enabling standardized operations." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Workspaces and Multi-Cluster Management" NCP-CN 6.10 Study Guide - "Standardizing Configurations Across Clusters"
=======
NEW QUESTION # 65
A Platform Engineer is preparing machine images for NKP through the NIB or KIB process. What is the purpose of doing this?
- A. Tagging the image to be used specifically for NKP
- B. Creating a CAPI-compliant image for use as NKP cluster nodes
- C. Creating a custom user account for NKP admins to ensure access to NKP nodes
- D. Hardening an OS image with client-supplied hardening scripts
Answer: B
Explanation:
The Nutanix Kubernetes Platform (NKP) leverages Cluster API (CAPI) to manage the lifecycle of Kubernetes clusters. When preparing machine images for NKP deployment, the Nutanix Image Builder (NIB) or Kubernetes Image Builder (KIB) process is used to create custom machine images that are compatible with NKP's infrastructure requirements. According to the NKPA course, the primary purpose of this process is to create CAPI-compliant images that can be used as the base for NKP cluster nodes.
The NKPA course explains that NKP uses CAPI to provision and manage Kubernetes clusters, and CAPI requires machine images that meet specific criteria, such as including the necessary Kubernetes components, container runtimes, and operating system configurations. The NIB/KIB process ensures that the images are pre-configured with these components, making them suitable for use as NKP worker and control plane nodes.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "The Nutanix Image Builder (NIB) or Kubernetes Image Builder (KIB) is used to create CAPI-compliant machine images that include the required OS, Kubernetes binaries, and dependencies for NKP cluster nodes." These images are typically based on supported operating systems like Rocky Linux or Ubuntu, as provided by Nutanix, and are customized to include the container runtime (e.g., containerd), kubeadm, and other dependencies required for CAPI-based cluster provisioning. The resulting images are stored in a location accessible to the NKP deployment process, such as a local registry or Nutanix Prism Central.
Incorrect Options:
* A. Hardening an OS image with client-supplied hardening scripts: While hardening the OS is a good practice, it is not the primary purpose of the NIB/KIB process. The NKPA course notes that hardening can be applied as part of image customization, but the core goal is to ensure CAPI compliance, not just hardening.
* B. Creating a custom user account for NKP admins to ensure access to NKP nodes: The NIB/KIB process does not focus on creating user accounts. User access is managed through Kubernetes RBAC or external identity providers, as covered in the NKPA course's authentication section.
* C. Tagging the image to be used specifically for NKP: Tagging may occur as part of image management, but it is not the primary purpose. The NKPA course emphasizes CAPI compliance over tagging.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Preparing Machine Images.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on NKP Deployment Prerequisites.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Cluster API Documentation: https://cluster-api.sigs.k8s.io
NEW QUESTION # 66
A Platform Engineer wants to deploy a custom OS image for multiple NKP clusters for Nutanix AHV and AWS. Which two tools come bundled to facilitate creating and placing a custom image into the respective image repository?
- A. Nutanix Image Builder
- B. Konvoy Image Builder
- C. Ansible
- D. Terraform
Answer: A,B
NEW QUESTION # 67 
A DevOps team faces a growing challenge of managing logs from multiple applications in an NKP cluster.
With several teams working on different projects, it is essential to implement a Multi-Tenant Logging system that allows each team to access their own logs securely and efficiently. Initially, two namespaces have been configured for each project, as shown in the exhibit. Then a ConfigMap has also been configured for each tenant, which contains the logging configuration. Which YAML output corresponds to a retention period of
30 days for tenant-innovation and seven days for tenant-analytics?
- A. yaml
CollapseWrap
Copy
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-innovation-config
namespace: tenant
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 30d
---
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-analytics-config
namespace: tenant
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 7d - B. yaml
CollapseWrap
Copy
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-innovation-config
namespace: tenant-innovation
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 30h
---
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-analytics-config
namespace: tenant-analytics
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 7h - C. yaml
CollapseWrap
Copy
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-innovation-config
namespace: tenant-innovation
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 30d
---
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-analytics-config
namespace: tenant-analytics
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 7d - D. yaml
CollapseWrap
Copy
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-innovation-config
namespace: tenant-innovation
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 30d
---
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-analytics-config
namespace: tenant-innovation
data:
values.yaml: |
loki:
structuredConfig:
limits_config:
retention_period: 7d
Answer: C
Explanation:
The NKPA course explains that NKP uses Grafana Loki as part of its logging stack to implement a multi- tenant logging system, allowing teams to access their logs securely within their respective namespaces. The exhibit indicates two namespaces, tenant-innovation and tenant-analytics, each with a ConfigMap for logging configuration. The requirement is to set a retention period of 30 days for tenant-innovation and 7 days for tenant-analytics.
The correct YAML output (Option A) configures Loki's retention period using ConfigMaps in the appropriate namespaces:
* For tenant-innovation, the ConfigMap logging-innovation-config in the tenant-innovation namespace sets retention_period: 30d.
* For tenant-analytics, the ConfigMap logging-analytics-config in the tenant-analytics namespace sets retention_period: 7d.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "In NKP, configure multi-tenant logging with Grafana Loki by creating a ConfigMap per namespace, specifying retention periods under loki.
structuredConfig.limits_config.retention_period (e.g., 30d for 30 days, 7d for 7 days)." The d suffix denotes days, aligning with the requirement for 30 days and 7 days retention periods.
Incorrect Options:
* B: The second ConfigMap incorrectly uses the tenant-innovation namespace instead of tenant-analytics, breaking the multi-tenant isolation.
* C: The retention periods are set to 30h and 7h (hours), not 30d and 7d (days), which does not meet the requirement.
* D: Both ConfigMaps use a generic tenant namespace, which does not match the specific namespaces (tenant-innovation, tenant-analytics) shown in the exhibit.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Multi-Tenant Logging with Loki.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Grafana Loki Documentation: https://grafana.com/docs/loki
NEW QUESTION # 68
A company uses an Artifactory private registry for development. The NKP deployment must use this private registry since the Security Administrator has the firewall configured to reject connections to public container registries. The first task is to push the NKP bundle to this private registry.
What options should be used to push the NKP bundle to this private registry?
- A. --mirror-url, --mirror-username and --mirror-password
- B. --to-registry, --to-registry-username and --to-registry-password
- C. --registry-mirror-url, --registry-mirror-username and --registry-mirror-password
- D. --registry-url, --registry-username and --registry-password
Answer: B
NEW QUESTION # 69
At a national defense company, protecting sensitive data is their top priority. With the increase in cyber- attacks, they have decided to implement an air-gapped Kubernetes environment to manage their critical applications, ensuring that no information could leak to the outside. The Kubernetes environment has three clusters deployed for their applications with centralized management. What type of licensing is required to enable this environment?
- A. NKP UI
- B. NKP Pro
- C. NKP Starter
- D. NKP Ultimate
Answer: D
Explanation:
The NKPA course specifies that air-gapped deployments and centralized fleet management of multiple clusters are advanced features of NKP, requiring the NKP Ultimate license tier. The Ultimate tier includes support for air-gapped environments (via Air-Gapped Bundles) and fleet management capabilities, such as attaching and managing multiple clusters under a single management plane, which is critical for the national defense company's scenario.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "The NKP Ultimate license tier is required for air-gapped deployments and centralized management of multiple Kubernetes clusters, providing the necessary tools for secure, isolated environments." This ensures the company can deploy and manage their three clusters in an air-gapped setup while maintaining strict data security.
Incorrect Options:
* A. NKP Starter: The Starter tier lacks air-gapped and fleet management features.
* C. NKP Pro: The Pro tier may support some advanced features but not air-gapped deployments or full fleet management.
* D. NKP UI: This is not a license tier; it's a UI component of NKP.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Licensing and Fleet Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Air-Gapped Deployments.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com
NEW QUESTION # 70
In an effort to control cloud cost consumption, auto-scale is configured to meet demands as needed.
What is the behavior for when nodes are scaled down?
- A. Node is changed to a status of Power-Off for stand-by.
- B. Node is changed to a status of Hibernate.
- C. Node is CAPI deleted from its infrastructure provider, effectively removing it from its hypervisor.
- D. Node is paused in Kubernetes and the infrastructure continues to consume the resources at the current level.
Answer: C
NEW QUESTION # 71
A Cloud Engineer wishes to attach existing AKS clusters to a newly deployed NKP management cluster.
What should the engineer consider specific to attaching these types of clusters to NKP?
- A. A separate service account should be created for them because their kubeconfig files are not usable out- of-box by NKP Kommander.
- B. AKS does not have the kubelet installed on them. Therefore the KIB-prep process should be performed on each of the nodes in the AKS clusters prior to attaching them.
- C. AKS nodes do not use containerd as its container runtime. Therefore it should be deployed to each of the nodes in the AKS clusters prior to attaching them.
- D. Cert-manager, which is included in NKP, is deployed by default on AKS clusters.
Answer: A
Explanation:
The NKPA 6.10 documentation specifies that when attaching external clusters like AKS (Azure Kubernetes Service) to an NKP management cluster using Kommander, the default kubeconfig provided by AKS is typically not directly usable because it lacks the necessary service account details and permissions for NKP to properly manage the cluster. Therefore, the recommended and required approach is to create a separate service account in AKS with the necessary permissions and generate a kubeconfig file for this service account.
Key reference:
"When importing external clusters, such as AKS, the default kubeconfig might not contain the correct permissions for NKP Kommander. A custom kubeconfig for a service account with cluster-admin privileges should be created and used to attach the cluster to NKP." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Attaching External Clusters" NCP-CN 6.10 Study Guide - "Managing External Clusters"
=======
NEW QUESTION # 72
Which two statements are true regarding deploying NKP on an Azure Kubernetes Service (AKS) Infrastructure? (Choose two.)
- A. Existing AKS clusters must be attached to the Management cluster.
- B. AKS clusters can be deployed as Management or Pro NKP clusters.
- C. NKP Management cluster with the Kommander component must be installed before installing NKP on AKS cluster.
- D. AKS best practices encourage building customized images.
Answer: A,C
Explanation:
The NKPA course outlines the specifics of integrating Azure Kubernetes Service (AKS) with NKP, focusing on fleet management and the deployment architecture. The correct statements are:
* Existing AKS clusters must be attached to the Management cluster (Option A):NKP does not provision AKS clusters directly because AKS is a managed Kubernetes service. Instead, NKP attaches existing AKS clusters to its management plane for centralized management. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "For AKS integration, existing AKS clusters must be attached to the NKP Management cluster using the Attach Cluster functionality, as NKP does not provision AKS clusters." This involves creating a service account with cluster-admin permissions in the AKS cluster and providing its kubeconfig to NKP.
* NKP Management cluster with the Kommander component must be installed before installing NKP on AKS cluster (Option C):The Kommander component is part of the NKP Management cluster and provides the centralized management plane for fleet management, including AKS clusters. The NKPA course specifies that an NKP Management cluster with Kommander must be deployed before attaching or managing external clusters like AKS. The NCP-CN 6.10 Study Guide notes: "An NKP Management cluster with Kommander must be installed prior to integrating AKS clusters, as Kommander enables the fleet management capabilities for external clusters." Incorrect Options:
* B. AKS best practices encourage building customized images: AKS best practices recommend using the default node images provided by Azure, which are optimized for AKS features like autoscaling and security. Custom images can lead to loss of functionality, as noted in previous questions (e.g., Q91).
* D. AKS clusters can be deployed as Management or Pro NKP clusters: AKS clusters are attached, not deployed, by NKP. Additionally, AKS clusters cannot serve as NKP Management clusters; the Management cluster must be deployed on supported infrastructure like Nutanix AHV, AWS, or vSphere. "Pro NKP clusters" is not a valid term in NKP documentation-Pro refers to a license tier, not a cluster type.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Fleet Management with AKS.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Attaching External Clusters.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com
NEW QUESTION # 73 
A current Nutanix cluster is hosting an NKP cluster and a production Kubernetes cluster named production. Infrastructure administrators recently added three nodes with NVidia GPUs for a new AI initiative, and now a Platform Engineer has been asked to add three workers with the GPUs to the production Kubernetes cluster. Which first step should the engineer take to achieve this task?
- A. Configure Multi-Instance GPU (MIG):textCollapseWrapCopykubectl label nodes ${NODE} nvidia.com/mig.config=all-1g.6gb -overwrite
- B. Create a nodepool of workers with GPU:textCollapseWrapCopynkp create nodepool nutanix -c $CLUSTER_NAME \--vm-image $NAME_OF_GPU_OS_IMAGE_CREATED_BY_NKP_CLI \-o yaml --subnets $NUTANIX_SUBNET_NAME \--prism-element-cluster $NUTANIX_PRISM_ELEMENT_CLUSTER_NAME \$NODEPOOL_NAME
- C. Create a GPU-compatible OS Image with:textCollapseWrapCopynkp create image nutanix --gpu \--gpu-name=${GPU_NAME} \--cluster=${NUTANIX_CLUSTER_NAME} \--endpoint=${NUTANIX_PC_ENDPOINT} \--subnet=${NUTANIX_SUBNET} ubuntu-22.04
- D. Add the GPU Operator to the new workers:textCollapseWrapCopycat <<EOF | kubectl apply -f -kind: Installationapps:nvidia-gpu-operator:enabled: truevalues: |toolkit:nodepool: md-0EOF
Answer: C
NEW QUESTION # 74
A dev team needed to optimize their logging system to be more robust, because the CPU and memory limits were insufficient, which caused delays in log collection and processing during times of high demand.
After a deep performance analysis, they decided to increase the CPU limits from 1 to 4 and the memory from
1000Mi to 4Gi.
Which ConfigMap should the development team run with custom resource requests and limit values for fluentd?
- A. bash
Copy
[nutanix@nkp-boot ~]$ cat <<EOF > configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-operator-logging-overrides
namespace: kommander
data:
values.yaml: |
fluentd
resources
limits
cpu 4
memory 1000Mi
requests
cpu 1
memory 4Gi
EOF - B. bash
Copy
[nutanix@nkp-boot ~]$ cat <<EOF > configmap.yaml
apiVersion v1
kind ConfigMap
metadata
name logging-operator-logging-overrides
namespace kommander
data
values.yaml |
fluentd
resources
limits
cpu 1
memory 1000Mi
requests
cpu 4
memory 4Gi
EOF - C. bash
Copy
[nutanix@nkp-boot ~]$ cat <<EOF > configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-operator-logging-overrides
namespace: kommander
data:
values.yaml: |
fluentd:
resources:
limits:
cpu: 4
memory: 4Gi
requests:
cpu: 4
memory: 4Gi
EOF - D. bash
Copy
[nutanix@nkp-boot ~]$ cat <<EOF > configmap.yaml
apiVersion v1
kind ConfigMap
metadata
name logging-operator-logging-overrides
namespace kommander
data
values.yaml |
fluentd
resources
limits
cpu 4
EOF
values.yaml |
fluentd
resources
limits
cpu 4
memory 4Gi
requests
cpu 1
memory 1000Mi
EOF
Answer: C
Explanation:
As outlined in the NKPA 6.10 documentation under "Customizing Resource Requests and Limits for Logging," to override the default resource values for the logging operator, a ConfigMap named logging- operator-logging-overrides in the kommander namespace is used. The values.yaml in the ConfigMap should precisely define fluentd resource limits and requests in a valid YAML format.
The correct YAML format is:
yaml
Copy
apiVersion: v1
kind: ConfigMap
metadata:
name: logging-operator-logging-overrides
namespace: kommander
data:
values.yaml: |
fluentd:
resources:
limits:
cpu: 4
memory: 4Gi
requests:
cpu: 4
memory: 4Gi
This ensures that the desired CPU and memory resources are correctly applied for the fluentd daemon, avoiding parsing errors and meeting the high-demand logging needs.
Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Configuring Logging Resources" NCP-CN 6.10 Study Guide - "Overriding Fluentd Resources Using ConfigMap"
=======
NEW QUESTION # 75 
An administrator is provisioning an NKP cluster. After the VM creation task, the error shown in the exhibit is produced.
What could be the reason?
- A. Private registry software or version is not the recommended.
- B. NKP Software is not loaded in the registry.
- C. VM does not have the Linux version.
- D. VM doesn't have communication to the registry.
Answer: D
NEW QUESTION # 76
A Platform Engineer needs to create an NKP cluster on vSphere infrastructure, using the vSphere provisioning method. The cluster needs to have 3 worker node pools:
First node pool should consist of 6 worker nodes
Second node pool should consist of 3 worker nodes
Third node pool should consist of 3 worker nodesAdditionally, the worker nodes in the first node pool should be set to 10 CPUs, the second node pool workers should be set to 8 CPUs, and the third node pool workers should be set to 6 CPUs. What is the proper way to create the NKP cluster using the NKP CLI?
- A. First, execute the nkp create cluster vsphere command, including the following parameters:--worker-replicas 6--worker-cpus 10Then, execute the nkp create nodepools vsphere command, including the following parameters:--replicas 3,3--cpus 8,6
- B. First, execute the nkp create cluster vsphere command, including the following parameters:--worker-replicas 6--worker-cpus 10Then, execute the nkp create nodepool vsphere command, including the following parameters:--replicas 3--cpus 6
- C. When executing the nkp create cluster vsphere command, include the following parameters:--node-pools 3--worker-replicas 6,3,3--worker-cpus 10,8,6
- D. First, execute the nkp create cluster vsphere command, including the following parameters:--worker-replicas 6--worker-cpus 10Then, execute the nkp create nodepool vsphere command, including the following parameters:--worker-replicas 3--worker-cpus 8Then, execute the nkp create nodepool vsphere command, including the following parameters:--worker-replicas 3--worker-cpus 6
Answer: D
NEW QUESTION # 77
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?
- A. kubectl get namespaces
- B. kubectl apply -f fluent-bit-overrides.yaml
- C. kubectl get helmreleases -n ${PROJECT_NAMESPACE}
- D. kubectl edit helmreleases -n ${PROJECT_NAMESPACE}
Answer: C
NEW QUESTION # 78
An ecommerce company decides to apply an autoscaling configuration in its NKP cluster due to the fact that on holidays, they experience service drops due to a huge increase of simultaneous traffic.
Which statement best describes the configuration shown in the exhibit?
- A. The autoscaler could increase the number of nodes as needed, but never reduce it below 3.
- B. The autoscaler could increase the number of nodes up to 15, but never reduce the number below 3.
- C. The autoscaler could increase the number of nodes up to 3, but never reduce it below 15.
- D. The autoscaler could have 15 or 3 nodes.
Answer: B
NEW QUESTION # 79
A Platform Engineer has been tasked with building a custom image for the deployment of NKP management and worker nodes. The engineer needs to ensure that the proper package versions are used when creating these images. The security team has only authorized version 1.30.5 of Kubernetes and version 1.7.22 of containerd. Where should the engineer go to verify that this is the version being used when building the custom image?
- A. The custom image's .env file
- B. ansible/group_vars/all/defaults.yaml
- C. config/pulumi/vars/pulumi.kib.config
- D. terraform/vars/default/terraform.tfvars
Answer: B
NEW QUESTION # 80
A Platform Engineer is deploying an NKP workload cluster using the nkp create cluster vsphere command. The cluster will be utilized by the company's code-green team and the engineer has already created a code-green NKP workspace on the NKP management cluster.
After issuing the deploy command, the engineer monitored the build using the nkp describe cluster command and confirmed it completed successfully. However, a few hours later, after logging into the NKP UI, the engineer checked the code-green NKP workspace and saw that the NKP workload cluster was not there.
What is the likely reason the NKP workload cluster is not in the code-green NKP workspace?
- A. The vSphere service account credentials had expired prior to the engineer's attempt to view the cluster in the NKP UI. Once the credentials are refreshed, the vSphere cluster will reappear in the NKP workspace.
- B. The vSphere cluster cannot be displayed in the NKP UI unless its Kubernetes version is within 'N - 1' versions of the NKP management cluster's Kubernetes version.
- C. The engineer did not supply the --namespace code-green parameter as part of the nkp create cluster vsphere command, therefore it was created in the default workspace and needs to be manually attached.
- D. NKP vSphere clusters cannot be assigned NKP workspaces and instead are assigned the default NKP workspace. The cluster can be viewed from this workspace instead.
Answer: C
NEW QUESTION # 81
......
Exam Materials for You to Prepare & Pass NCP-CN Exam: https://skillsoft.braindumpquiz.com/NCP-CN-exam-material.html