NCP-CN Practice Questions

A.  

docker load -i konvoy-bootstrap-image-.tar

B.  

docker image tag konvoy-bootstrap-image-.tar version docker.io/konvoy-bootstrap version

C.  

nkp push bundle --bundle konvoy-bootstrap-image-.tar --to-registry=

D.  

nkp load image -f konvoy-bootstrap-image-.tar --to-registry=

A.  

Access the NKP UI

Switch to the victory-finance NKP namespace

Click on the Applications menu panel and select Velero

Edit the Velero application configuration at the cluster level for the specific NKP managed cluster (not all clusters in that NKP workspace)

Set the backup frequency to four times daily

B.  

Install the Velero CLI

Use the Velero CLI to create a backup schedule that includes the following parameters:

  - Backup name

  - Kubernetes namespace to backup

  - Backup frequency (every six hours)

  - Managed NKP cluster’s kubeconfig

C.  

Install the Velero CLI

Use the Velero CLI to create a backup schedule that includes the following parameters:

  - Backup name

  - NKP workspace to backup

  - Backup frequency (every six hours)

  - Managed NKP cluster’s kubeconfig

D.  

Access the NKP UI

Switch to the victory-finance-apps NKP workspace

Click on the Applications menu panel and select Velero

Edit the Velero application configuration at the cluster level for the specific NKP managed cluster (not all clusters in that NKP workspace)

Set the backup frequency to four times daily

A.  

Private registry license is included with NKP.

B.  

NKP requires specific registry versions.

C.  

NKP cannot connect to public clouds.

D.  

Private registry provides security and privacy.

A.  

Create an 'R&D' NKP workspace

Create an 'R&D' infrastructure provider in this workspace

Create an 'R&D' NKP group for the R&D team members and assign admin-level roles within

Deploy the NKP clusters into the 'R&D' workspace

B.  

Create an 'R&D' NKP connector and infrastructure provider

Create an 'R&D' NKP group and assign it admin-level roles

Assign the 'R&D' NKP group to the 'R&D' NKP connector

Deploy the NKP clusters into the 'R&D' workspace

C.  

Create an 'R&D' NKP workspace and project within this workspace

Create an NKP infrastructure provider in the 'R&D' NKP project

Create an 'R&D' NKP group for the R&D team members and assign admin-level roles within this project

Deploy the NKP clusters into the 'R&D' workspace

D.  

Create an 'R&D' NKP connector and infrastructure provider

Create an 'R&D' NKP group and assign it admin-level roles

Assign the 'R&D' NKP group to the 'R&D' NKP infrastructure provider

Deploy the NKP clusters into the 'R&D' workspace

A.  

kubectl get namespaces

B.  

kubectl get helmreleases -n ${PROJECT_NAMESPACE}

C.  

kubectl edit helmreleases -n ${PROJECT_NAMESPACE}

D.  

kubectl apply -f fluent-bit-overrides.yaml

A.  

From the Cluster selection, select Add Cluster.

B.  

From the workspace selection dropdown list in the top menu bar, select Create Workspace.

C.  

From the workspace selection dropdown list in the top menu bar, select Add Workspace.

D.  

From the Administration selection dropdown list in Infrastructure Providers, select Add Infrastructure Provider.

A.  

nkp create appdeployment grafana-logging --app grafana-logging-6.57.4 --workspace default-workspace

B.  

export WORKSPACE_NAMESPACE=kommander-default-workspace

appdeployment

nkp create package-bundle grafana-logging

C.  

kubectl get appdeployment -n kommander-default-workspace

D.  

kubectl get helmreleases grafana-logging -n kommander-default-workspace -w

A.  

Call tech support to take a look at the infrastructure and investigate.

B.  

Ask developers to lower the number of application replicas.

C.  

Add more CPU and memory to workers with nkp scale --cpu 16 --memory 64 --cluster-name ${CLUSTER_NAME}

D.  

Add one more worker with nkp scale nodepools ${NODEPOOL_NAME} --replicas=5 --cluster-name=${CLUSTER_NAME} -n ${CLUSTER_WORKSPACE}

A.  

Enable Gatekeeper and create a connector to the user base’s identity provider.

B.  

Disable native NKP authentication, enable Traefik, and create a connector to the user base’s identity provider.

C.  

Create a MetalLB connector to the user base’s identity provider.

D.  

Create a Dex connector to the user base’s identity provider.

A.  

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.

B.  

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.

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.