An administrator accidentally closed the commit window/screen before the commit was finished. Which two options could the administrator use to verify the progress or success of that commit task? (Choose two)

• A.Traffic Logs
• B.System Logs
• C.Configuration Logs
• D.Task Manager

Comment: *

Name: *

Email: *

Verification: *

Check the history of deployment

Comment: *

Name: *

Email: *

Verification: *

Check logs of each container that "busyboxpod-{1,2,3}"

• A.kubectl logs busybox -c busybox-container-1
  kubectl logs busybox -c busybox-container-2
  kubectl logs busybox -c busybox-container-3
• B.kubectl logs busybox -c busybox-container-1
  kubectl logs busybox -c busybox-container-3
  kubectl logs busybox -c busybox-container-3

Comment: *

Name: *

Email: *

Verification: *

Create an nginx pod and set an env value as 'var1=val1'. Check the env value existence within the pod

• A.kubectl run nginx --image=nginx --restart=Never --env=var1=val1
  # then
  kubectl exec -it nginx -- env
  # or
  kubectl exec -it nginx -- sh -c 'echo $var1'
  # or
  kubectl describe po nginx | grep val1
  # or
  kubectl run nginx --restart=Never --image=nginx --env=var1=val1
  -it --rm - env
• B.kubectl run nginx --image=nginx --restart=Never --env=var1=val1
  # then
  kubectl exec -it nginx -- env
  # or
  kubectl run nginx --restart=Never --image=nginx --env=var1=val1
  -it --rm -- env

Comment: *

Name: *

Email: *

Verification: *

Create a daemonset named "Prometheus-monitoring" using image=prom/Prometheus which runs in all the nodes in the cluster. Verify the pod running in all the nodes

• A.vim promo-ds.yaml
  apiVersion: apps/v1
  kind: DaemonSet
  metadata:
  name: prometheus-monitoring
  spec:
  selector:
  matchLabels:
  name: prometheus
  template:
  metadata:
  labels:
  name: prometheus
  spec:
  tolerations:
  # remove it if your masters can't run pods
  - key: node-role.kubernetes.io/master
  effect: NoSchedule
  containers:
  - name: prometheus-container
  image: prom/prometheus
  volumeMounts:
  - name: varlog
  mountPath: /var/log
  - name: varlibdockercontainers
  mountPath: /var/lib/docker/containers
  readOnly: true
  volumes:
  - name: varlog
  emptyDir: {}
  - name: varlibdockercontainers
  emptyDir: {}
  kubectl apply -f promo-ds.yaml
  NOTE: Deamonset will get scheduled to "default" namespace, to
  schedule deamonset in specific namespace, then add
  "namespace" field in metadata
  //Verify
  kubectl get ds
  NAME DESIRED CURRENT READY UP-TO-DATE
  AVAILABLE NODE SELECTOR AGE
  prometheus-monitoring 6 6 0 6
  0 <none> 7s
  kubectl get no # To get list of nodes in the cluster
  // There are 6 nodes in the cluster, so a pod gets scheduled to
  each node in the cluster
• B.vim promo-ds.yaml
  apiVersion: apps/v1
  kind: DaemonSet
  metadata:
  name: prometheus-monitoring
  spec:
  selector:
  matchLabels:
  name: prometheus
  template:
  metadata:
  labels:
  name: prometheus
  spec:
  tolerations:
  # remove it if your masters can't run pods
  - key: node-role.kubernetes.io/master
  effect: NoSchedule
  containers:
  - name: prometheus-container
  - name: varlibdockercontainers
  mountPath: /var/lib/docker/containers
  readOnly: true
  volumes:
  - name: varlog
  emptyDir: {}
  - name: varlibdockercontainers
  emptyDir: {}
  kubectl apply -f promo-ds.yaml
  NOTE: Deamonset will get scheduled to "default" namespace, to
  schedule deamonset in specific namespace, then add
  "namespace" field in metadata
  //Verify
  kubectl get ds
  NAME DESIRED CURRENT READY UP-TO-DATE
  AVAILABLE NODE SELECTOR AGE
  prometheus-monitoring 8 8 0 6
  0 <none> 7s
  kubectl get no # To get list of nodes in the cluster
  // There are 6 nodes in the cluster, so a pod gets scheduled to
  each node in the cluster

Comment: *

Name: *

Email: *

Verification: *