Create PersistentVolume named task-pv-volume with storage 10Gi, access modes ReadWriteMany, storageClassName manual, and volume at /mnt/data and Create a PersistentVolumeClaim of at least 3Gi storage and access mode ReadWriteOnce and verify

• A.vim task-pv-volume.yaml
  apiVersion: v1
  kind: PersistentVolume
  metadata:
  name: task-pv-volume
  labels:
  type: local
  spec:
  storageClassName: manual
  capacity:
  storage: 10Gi
  accessModes:
  - ReadWriteMany
  hostPath:
  path: "/mnt/data"
  kubectl apply -f task-pv-volume.yaml
  //Verify
  kubectl get pv
  vim task-pvc-volume.yaml
  apiVersion: v1
  - ReadWriteMany
  resources:
  requests:
  storage: 3Gi
  kubectl apply -f task-pvc-volume.yaml
  //Verify
  Kuk kubectl get pvc
• B.vim task-pv-volume.yaml
  apiVersion: v1
  kind: PersistentVolume
  metadata:
  name: task-pv-volume
  labels:
  type: local
  spec:
  storageClassName: manual
  capacity:
  storage: 10Gi
  accessModes:
  - ReadWriteMany
  hostPath:
  path: "/mnt/data"
  kubectl apply -f task-pv-volume.yaml
  //Verify
  kubectl get pv
  vim task-pvc-volume.yaml
  apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
  name: task-pv-claim
  spec:
  storageClassName: manual
  accessModes:
  - ReadWriteMany
  resources:
  requests:
  storage: 3Gi
  kubectl apply -f task-pvc-volume.yaml
  //Verify
  Kuk kubectl get pvc

Comment: *

Name: *

Email: *

Verification: *

Remove taint added to node "worker-2"

Comment: *

Name: *

Email: *

Verification: *

What are the differences between using a service versus using an application for Security Policy match?

• A.Use of a "service" enables the firewall to take action after enough packets allow for App-ID identification
• B.There are no differences between "service" or "application." Use of an "application simplifies configuration by allowing use of a friendly application name instead of port numbers.
• C.Use of a "service" enables the firewall to take immediate action with the first observed packet based on port numbers. Use of an application allows the firewall to take action after enough packets allow for App-ID identification regardless of the ports being used
• D.Use of a "service" enables the firewall to take immediate action with the first observed packet based on port numbers. Use of an "application allows the firewall to take immediate action if the port being used is a member of the application standard port list

Comment: *

Name: *

Email: *

Verification: *

Create a pod that having 3 containers in it? (Multi-Container)

• A.image=nginx, image=redis, image=consul
  Name nginx container as "nginx-container"
  Name redis container as "redis-container"
  Name consul container as "consul-container"
  Create a pod manifest file for a container and append container
  section for rest of the images
  kubectl run multi-container --generator=run-pod/v1 --image=nginx --
  dry-run -o yaml > multi-container.yaml
  # then
  vim multi-container.yaml
  apiVersion: v1
  kind: Pod
  metadata:
  labels:
  run: multi-container
  name: multi-container
  spec:
  containers:
  - image: nginx
  name: nginx-container
  - image: redis
  name: redis-container
  - image: consul
  name: consul-container
  restartPolicy: Always
• B.image=nginx, image=redis, image=consul
  Name nginx container as "nginx-container"
  Name redis container as "redis-container"
  Name consul container as "consul-container"
  Create a pod manifest file for a container and append container
  section for rest of the images
  kubectl run multi-container --generator=run-pod/v1 --image=nginx --
  dry-run -o yaml > multi-container.yaml
  # then
  vim multi-container.yaml
  labels:
  run: multi-container
  name: multi-container
  spec:
  containers:
  - image: nginx
  name: nginx-container
  - image: redis
  name: consul-container
  restartPolicy: Always

Comment: *

Name: *

Email: *

Verification: *

Check the Image version of nginx-dev pod using jsonpath

Comment: *

Name: *

Email: *

Verification: *