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

Refer to Exhibit:

Using an NKP Ultimate license, a Platform Engineer has created a new workspace and needs to create a new Kubernetes cluster within this workspace. However, the engineer discovers that the Create Cluster option is grayed out, as shown in the exhibit. How should the engineer resolve this issue?

• A. Attach existing clusters instead of creating a new cluster.
• B. Create an Infrastructure provider for the workspace.
• C. Create the cluster only using YAML and not the GUI.
• D. Ensure NKP is upgraded to a minimum version of 2.12.

Which option is enabled with the NKP Pro licensing tier?

• A. Insights
• B. Kubernetes Dashboard
• C. AI OPS
• D. Fleet Management

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-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
• 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: 30d
  ---
  apiVersion: v1
  kind: ConfigMap
  metadata:
  name: logging-analytics-config
  namespace: tenant-innovation
  data:
  values.yaml: |
  loki:
  structuredConfig:
  limits_config:
  retention_period: 7d
• C. 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
• 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: 30h
  ---
  apiVersion: v1
  kind: ConfigMap
  metadata:
  name: logging-analytics-config
  namespace: tenant-analytics
  data:
  values.yaml: |
  loki:
  structuredConfig:
  limits_config:
  retention_period: 7h

A Platform Engineer would like to deploy an NKP Platform Application to all the clusters within an NKP workspace from the command line. What is the command set to use, and what parameters must be specified with it?

• A. The kubectl create appdeployment command set would be utilized. The application ID, as well as the NKP workspace of the clusters, must be provided.
• B. The nkp deploy platform-app command set would be utilized. The application ID, as well as the NKP workspace of the clusters, must be provided.
• C. The nkp deploy app command set would be utilized. The application ID, as well as the NKP workspace of the clusters, must be provided.
• D. The nkp create appdeployment command set would be utilized. The application ID & version, as well as the NKP workspace of the clusters, must be provided.

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?

• A. Detached cluster must also be deleted from NKP: nkp delete cluster -c detached-cluster-name
• B. Forcefully detach EKS cluster: nkp detach cluster -c detached-cluster-name --force
• C. Developers must have some bad configuration in the deployment config files. Ask for revision or call AWS technical support.
• D. 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