Free Nutanix NCP-CN Exam Questions (page: 3)

[Perform Day 2 Operations]
A development Kubernetes cluster deployed with NKP is having performance issues. The Cloud Engineer commented that worker VMs are consuming a lot of CPU and RAM. The Platform Engineer took a look at the CPU and RAM statistics with Grafana and confirmed that the worker VMs are running out of CPU and memory. The Kubernetes cluster has 4 workers with 8 vCPUs and 32 GB RAM.
What could the Platform Engineer do?

  1. Call tech support to take a look at the infrastructure and investigate.
  2. Ask developers to lower the number of application replicas.
  3. Add more CPU and memory to workers with nkp scale --cpu 16 --memory 64 --cluster-name ${CLUSTER_NAME}
  4. Add one more worker with nkp scale nodepools ${NODEPOOL_NAME} --replicas=5 --cluster- name=${CLUSTER_NAME} -n ${CLUSTER_WORKSPACE}

Answer(s): D



[Prepare the Environment for an NKP Deployment]
A Platform Engineer is preparing machine images for NKP through the NIB or KIB process.
What is the purpose of doing this?

  1. Hardening an OS image with client-supplied hardening scripts
  2. Creating a custom user account for NKP admins to ensure access to NKP nodes
  3. Tagging the image to be used specifically for NKP
  4. Creating a CAPI-compliant image for use as NKP cluster nodes

Answer(s): D



[Perform Day 2 Operations]
A development team decided to employ an efficient monitoring system with Grafana-logging, which was successfully implemented as can be seen in the following output:
AppDeployment "kommander-default-workspace/grafana-logging" created in namespace "kommander-default-workspace".
Which command did the team execute to complete this task?

  1. nkp create appdeployment grafana-logging --app grafana-logging-6.57.4 --workspace default- workspace
  2. export WORKSPACE_NAMESPACE=kommander-default-workspaceappdeploymentnkp create package-bundle grafana-logging
  3. kubectl get appdeployment -n kommander-default-workspace
  4. kubectl get helmreleases grafana-logging -n kommander-default-workspace -w

Answer(s): A



[Conduct NKP Fleet Management]
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?

  1. Forcefully detach EKS cluster: nkp detach cluster -c detached-cluster-name --force
  2. Detached cluster must also be deleted from NKP: nkp delete cluster -c detached-cluster-name
  3. Developers must have some bad configuration in the deployment config files. Ask for revision or call AWS technical support.
  4. Detached cluster's Flux installation must be manually disconnected from the management Git repository: kubectl -n kommmander-flux patch gitrepo management -p '{"spec":{"suspend":true}}' -- type merge

Answer(s): D






Post your Comments and Discuss Nutanix NCP-CN exam prep with other Community members:

NCP-CN Exam Discussions & Posts