Linux Foundation CKAテストエンジン練習テスト問題、試験問題集 [Q15-Q39]

Share

Linux Foundation CKAテストエンジン練習テスト問題、試験問題集

100%無料CKA日常練習試験には68問があります


認定されたKubernetes Administrator(CKA)プログラム認定試験は、Kubernetesクラスターを管理、展開、トラブルシューティングする個人のスキルを検証する業界で認識された資格情報です。 Kubernetesは、コンテナ化されたアプリケーションを管理するための好ましい選択肢となっているオープンソースのコンテナオーケストレーションシステムです。 Linux Foundationは、このテクノロジーの専門家の知識と経験を検証するためのCKAプログラムを提供しています。


Linux Foundation Certified Kubernetes Administrator(CKA)Program Examは、Kubernetesクラスタを管理する能力と知識を検証するプロフェッショナル認定資格です。Kubernetesは、コンテナ化されたアプリケーションの展開、スケーリング、管理を自動化するオープンソースのコンテナオーケストレーションプラットフォームです。コンテナ化された環境でのアプリケーションの展開と管理を簡素化するため、産業界で広く使用されています。CKA認定は、インフラストラクチャを管理するためにKubernetesの専門家を探している企業にとって高く求められる認定資格です。

 

質問 # 15
Print all pod name and all image name and write it to a file
name "/opt/pod-details.txt"

正解:

解説:
kubectl get pods -o=custom-columns='Pod Name:metadata.name','Image:spec.containers[*].image' > /opt/pod-details.txt


質問 # 16
List all persistent volumes sorted bycapacity, saving the fullkubectloutput to
/opt/KUCC00102/volume_list. Usekubectl 's own functionality forsorting the output, and do not manipulate it any further.

正解:

解説:
See the solution below.
Explanation
solution


質問 # 17
Allow traffic from all the pods in "web" namespace and from pods
with label "type=monitoring" to the pods matching label "app: db"

  • A. kubectl create namespace web
    kubectl label namespace/web app=web
    vim web-allow-all-ns-monitoring.yaml
    apiVersion: networking.k8s.io/v1
    kind: NetworkPolicy
    metadata:
    name: web-allow-all-ns-monitoring
    namespace: default
    spec:
    podSelector:
    podSelector:
    matchLabels:
    type: monitoring
    k kubectl apply -f web-allow-all-ns-monitoring.yaml
  • B. kubectl create namespace web
    kubectl label namespace/web app=web
    vim web-allow-all-ns-monitoring.yaml
    apiVersion: networking.k8s.io/v1
    kind: NetworkPolicy
    metadata:
    name: web-allow-all-ns-monitoring
    namespace: default
    spec:
    podSelector:
    matchLabels:
    app: db
    ingress:
    - from:
    - namespaceSelector:
    matchLabels:
    app: web
    podSelector:
    matchLabels:
    type: monitoring
    k kubectl apply -f web-allow-all-ns-monitoring.yaml

正解:B


質問 # 18
What file type upload is supported as part of the basic WildFire service?

  • A. BAT
  • B. PE
  • C. ELF
  • D. VBS

正解:B


質問 # 19
Clean the cluster by deleting deployment and hpa you just created

正解:

解説:
kubectl delete deploy webapp kubectl delete hpa webapp


質問 # 20
Scale the deployment webserver to

正解:

解説:
See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\14 B.JPG


質問 # 21
Create a pod as follows:
* Name:mongo
* Using Image:mongo
* In anew Kubernetes namespacenamed:my-website

正解:

解説:
See the solution below.
Explanation
solution


質問 # 22
Schedule a pod as follows:
Name: nginx-kusc00101
Image: nginx
Node selector: disk=ssd

正解:

解説:
See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\6 B.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\6 C.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\6 D.JPG


質問 # 23
Create a pod with image nginx called nginx and allow traffic on port 80

正解:

解説:
See the solution below.
Explanation
kubectlrun nginx --image=nginx --restart=Never --port=80


質問 # 24
From the pod label name=cpu-utilizer, find pods running high CPU workloads and write the name of the pod consuming most CPU to the file /opt/KUTR00102/KUTR00102.txt (which already exists).

正解:

解説:
See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\16 B.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\16 C.JPG


質問 # 25
Create a pod as follows:
Name: mongo
Using Image: mongo
In a new Kubernetes namespace named: my-website

正解:

解説:
See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\9 B.JPG


質問 # 26
Create a pod that echo "hello world" and then exists. Have the pod deleted automatically when it's completed

正解:

解説:
kubectl run busybox --image=busybox -it --rm --restart=Never -- /bin/sh -c 'echo hello world' kubectl get po # You shouldn't see pod with the name "busybox"


質問 # 27
Given a partially-functioning Kubernetes cluster, identify symptoms of failure on the cluster.
Determine the node, the failing service, and take actions to bring up the failed service and restore the health of the cluster. Ensure that any changes are made permanently.
You can ssh to the relevant I nodes (
[student@node-1] $ ssh <nodename
You can assume elevated privileges on any node in the cluster with the following command:
[student@nodename] $ | sudo -i

正解:

解説:
See the solution below.
Explanation
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\23 C.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\23 D.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\23 E.JPG


質問 # 28
List all the pods sorted by name

正解:

解説:
See the solution below.
Explanation
kubectl get pods --sort-by=.metadata.name


質問 # 29
List "nginx-dev" and "nginx-prod" pod and delete those pods

正解:

解説:
kubect1 get pods -o wide
kubectl delete po "nginx-dev" kubectl delete po "nginx-prod"


質問 # 30
Create a deployment spec file that will:
* Launch 7 replicas of the nginx Image with the labelapp_runtime_stage=dev
* deployment name: kual00201
Save a copy of this spec file to /opt/KUAL00201/spec_deployment.yaml
(or /opt/KUAL00201/spec_deployment.json).
When you are done, clean up (delete) any new Kubernetes API object that you produced during this task.

正解:

解説:
See the solution below.
Explanation
solution


質問 # 31
Fix a node that shows as non-ready

  • A. Kubectl get nodes
    // Check which node shows a not ready
    kubectl describe nodes "node-name"
    // Login to the node which shows as not ready and check the
    systemctl start kubelet / docker
    // Verify
    ps -auxxww | grep -i "process-name"
    kubectl get nodes
  • B. Kubectl get nodes
    // Check which node shows a not ready
    kubectl describe nodes "node-name"
    // Login to the node which shows as not ready and check the
    process for kubelet, docker , kube-proxy.
    // systemctl status kubelet (or) ps -aux | grep -i "processname"
    // If the process is not started, then start using
    systemctl start kubelet / docker
    // Verify
    ps -auxxww | grep -i "process-name"
    kubectl get nodes

正解:B


質問 # 32
Check to see how many worker nodes are ready (not including nodes taintedNoSchedule) and write the number to/opt/KUCC00104/kucc00104.txt.

正解:

解説:
See the solution below.
Explanation
solution


質問 # 33
Create the service as type NodePort with the port 32767 for the nginx pod with the pod selector app: my-nginx

正解:

解説:
kubectl run nginx --image=nginx --restart=Never -- labels=app=nginx --port=80 --dry-run -o yaml > nginx-pod.yaml


質問 # 34
Create a Kubernetes secret as follows:
Name: super-secret
password: bob
Create a pod named pod-secrets-via-file, using the redis Image, which mounts a secret named super-secret at /secrets.
Create a second pod named pod-secrets-via-env, using the redis Image, which exports password as CONFIDENTIAL

正解:

解説:
solution



質問 # 35
Delete persistent volume and persistent volume claim

正解:

解説:
kubectl delete pvc task-pv-claim kubectl delete pv task-pv-volume // Verify Kubectl get pv,pvc


質問 # 36
Check the rollout history and make sure everything is ok after the update

  • A. kubectl rollout history deploy webapp
    kubectl get deploy webapp --show-labels
    kubectl get rs -l app=webapp
    kubectl get po -l app=webapp
  • B. kubectl rollout history deploy webapp
    kubectl get deploy webapp --show-labels
    kubectl get rs -
    kubectl get po -l app=webapp

正解:A


質問 # 37
Score: 4%

Task
Scale the deployment presentation to 6 pods.

正解:

解説:
Solution:
kubectl get deployment
kubectl scale deployment.apps/presentation --replicas=6


質問 # 38
Score: 7%

Task
Given an existing Kubernetes cluster running version 1.20.0, upgrade all of the Kubernetes control plane and node components on the master node only to version 1.20.1.
Be sure to drain the master node before upgrading it and uncordon it after the upgrade.

You are also expected to upgrade kubelet and kubectl on the master node.

正解:

解説:
SOLUTION:
[student@node-1] > ssh ek8s
kubectl cordon k8s-master
kubectl drain k8s-master --delete-local-data --ignore-daemonsets --force apt-get install kubeadm=1.20.1-00 kubelet=1.20.1-00 kubectl=1.20.1-00 --disableexcludes=kubernetes kubeadm upgrade apply 1.20.1 --etcd-upgrade=false systemctl daemon-reload systemctl restart kubelet kubectl uncordon k8s-master


質問 # 39
......

有効な問題最新版を試そうCKAテスト解釈CKA有効な試験ガイド:https://jp.fast2test.com/CKA-premium-file.html

CKA試験資料Linux Foundation学習ガイド:https://drive.google.com/open?id=1RvDZG4jdQlvfTKLS3XkRqfreTJhliFv1


弊社を連絡する

我々は12時間以内ですべてのお問い合わせを答えます。

我々の働いている時間: ( GMT 0:00-15:00 )
月曜日から土曜日まで

サポート: 現在連絡 

English Deutsch 繁体中文 한국어