Nutanix Certified Professional - Cloud Native v6.10 : NCP-CN-6.10

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?

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

After a finished project, three Kubernetes clusters within a workspace were deleted, so the workspace is empty. Now a Platform Engineer needs to delete the workspace. How should the engineer delete the workspace in NKP?

• A. Run kubectl delete workspace <workspace-name>
• B. Ask a workspace user to delete the workspace. The user has the Delete option in their workspace home page.
• C. From NKP UI, on top menu bar select Global, then select Workspaces in the menu, select the three-dot button for the workspace to delete, and then click Delete.
• D. Run kubectl delete workspace <workspace_name>

Which NKP-supported infrastructure will not receive CAPI components when an NKP cluster is deployed to it?

• A. vSphere
• B. AKS
• C. GCP
• D. Nutanix

A Platform Engineer is deploying NKP into a highly secure vSphere environment. The NKP cluster will be air-gapped, and must also be FIPS compliant. The OS platform to be used for NKP cluster nodes is RHEL.
What must the engineer do to properly prep an OS image and have it be deployed as a FIPS compliant NKP cluster node?

• A. Verify the OS itself has been placed in fips mode.When performing the NKP image build operation, be sure to include the offline fips and fips overrides.When performing the NKP cluster deploy operation, be sure to include the FIPS version references for kubernetes and etcd.
• B. Verify the OS itself has been placed in fips mode.When performing the NKP image build operation, be sure to include the offline fips override.When performing the NKP cluster deploy operation, be sure to include the FIPS version references for kubernetes and etcd.
• C. Verify the OS itself has been placed in fips mode.When performing the NKP cluster deploy operation, be sure to include the FIPS version references for kubernetes, kubectl and etcd.
• D. Verify the OS itself has been placed in fips mode.When performing the NKP image build operation, be sure to include the offline fips and fips overrides.When performing the NKP cluster deploy operation, be sure to include the FIPS version references for kubernetes, kubectl and etcd.

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. bashCopy
  [nutanix@nkp-boot ~]$ cat <<EOF > configmap.yamlapiVersion v1kind ConfigMapmetadataname logging-operator-logging-overridesnamespace kommanderdatavalues.yaml
  |fluentdresourceslimitscpu 1memory 1000Mirequestscpu 4memory 4GiEOF
• B. bashCopy
  [nutanix@nkp-boot ~]$ cat <<EOF > configmap.yamlapiVersion: v1kind:
  ConfigMapmetadata:name:
  logging-operator-logging-overridesnamespace: kommanderdata:values.yaml:
  |fluentd:resources:limits:cpu: 4memory: 4Girequests:cpu: 4memory: 4GiEOF
• C. bashCopy
  [nutanix@nkp-boot ~]$ cat <<EOF > configmap.yamlapiVersion v1kind ConfigMapmetadataname logging-operator-logging-overridesnamespace kommanderdatavalues.yaml
  |fluentdresourceslimitscpu 4EOFvalues.yaml |fluentdresourceslimitscpu 4memory 4Girequestscpu
  1memory 1000MiEOF
• D. bashCopy
  [nutanix@nkp-boot ~]$ cat <<EOF > configmap.yamlapiVersion: v1kind:
  ConfigMapmetadata:name:
  logging-operator-logging-overridesnamespace: kommanderdata:values.yaml:
  |fluentdresourceslimitscpu 4memory 1000Mirequestscpu 1memory 4GiEOF