CKAD EXAM 2

1 / 10

Question:

You are tasked with deploying a multi-container pod that hosts a web server and a sidecar container responsible for logging. The pod must meet the following requirements:

It must run in the production namespace (already created).
The main container should use the nginx:latest image and expose port 80.
The sidecar container should use the busybox image with the 1.28 tag and run a command that writes logs to /var/log/log.txt every 10 seconds.
The pod should have the name webserver-logger.
The sidecar container must have resource limits set to 100m CPU and 50Mi memory.

Which of the following YAML manifests will correctly define the pod with the specified requirements?

apiVersion: v1
kind: Pod
metadata:
  name: webserver-logger
  namespace: production
spec:
  containers:
  - name: webserver
    image: nginx:latest
    ports:
    - containerPort: 80
  - name: logger
    image: busybox:1.28
    command: ["sh", "-c", "while true; do echo 'Logging' >> /var/log/log.txt; sleep 10; done"]
    resources:
      limits:
        cpu: "100m"
        memory: "50Mi"
    volumeMounts:
    - mountPath: /var/log
      name: log-volume
  volumes:
  - name: log-volume
    emptyDir: {}

apiVersion: v1
kind: Pod
metadata:
  name: webserver-logger
  namespace: production
spec:
  containers:
  - name: webserver
    image: nginx:latest
    ports:
    - containerPort: 80
  - name: logger
    image: busybox:1.28
    command: ["sh", "-c", "while true; do echo 'Logging' >> /var/log/log.txt; sleep 10; done"]
    resources:
      requests:
        cpu: "100m"
        memory: "50Mi"
    volumeMounts:
    - mountPath: /var/log
      name: log-volume
  volumes:
  - name: log-volume
    emptyDir: {}

apiVersion: v1
kind: Pod
metadata:
  name: webserver-logger
  namespace: production
spec:
  containers:
  - name: webserver
    image: nginx:latest
    ports:
    - containerPort: 80
  - name: logger
    image: busybox:1.28
    command: ["sh", "-c", "while true; do echo 'Logging' >> /var/log/log.txt; sleep 10; done"]
    resources:
      limits:
        cpu: "50m"
        memory: "25Mi"
    volumeMounts:
    - mountPath: /var/log
      name: log-volume
  volumes:
  - name: log-volume
    emptyDir: {}

apiVersion: v1
kind: Pod
metadata:
  name: webserver-logger
  namespace: production
spec:
  containers:
  - name: webserver
    image: nginx:latest
    ports:
    - containerPort: 80
  - name: logger
    image: busybox:1.28
    command: ["sh", "-c", "while true; do echo 'Logging' >> /var/log/log.txt; sleep 10; done"]
    resources:
      limits:
        cpu: "200m"
        memory: "100Mi"
    volumeMounts:
    - mountPath: /var/log
      name: log-volume
  volumes:
  - name: log-volume
    emptyDir: {}

2 / 10

Question

You are assigned to configure a Kubernetes environment for a database application with specific reliability and security requirements. The database should meet the following requirements:

The application must use PostgreSQL 13 in a highly available setup.
The application must have two replicas running for high availability.
Data persistence must be implemented using Persistent Volumes.
The database must be deployed in a secure namespace called db-secure.
Secrets must be used for sensitive information (database username and password).
The database deployment must expose port 5432 only within the cluster using a ClusterIP service.

Which of the following YAML manifests correctly meets all the stated requirements?

apiVersion: apps/v1
kind: Deployment
metadata:
  name: postgres-deployment
  namespace: db-secure
spec:
  replicas: 2
  selector:
    matchLabels:
      app: postgres
  template:
    metadata:
      labels:
        app: postgres
    spec:
      containers:
      - name: postgres
        image: postgres:13
        ports:
        - containerPort: 5432
        env:
        - name: POSTGRES_USER
          valueFrom:
            secretKeyRef:
              name: postgres-secret
              key: username
        - name: POSTGRES_PASSWORD
          valueFrom:
            secretKeyRef:
              name: postgres-secret
              key: password
        volumeMounts:
        - mountPath: /var/lib/postgresql/data
          name: postgres-storage
      volumes:
      - name: postgres-storage
        persistentVolumeClaim:
          claimName: postgres-pv-claim
  --- apiVersion: v1
kind: Service
metadata:
  name: postgres-service
  namespace: db-secure
spec:
  selector:
    app: postgres
  ports:
  - port: 5432
    targetPort: 5432
  clusterIP: ClusterIP

apiVersion: apps/v1
kind: Deployment
metadata:
  name: postgres-deployment
  namespace: db-secure
spec:
  replicas: 2
  selector:
    matchLabels:
      app: postgres
  template:
    metadata:
      labels:
        app: postgres
    spec:
      containers:
      - name: postgres
        image: postgres:13
        ports:
        - containerPort: 5432
        envFrom:
        - secretRef:
            name: postgres-secret
        volumeMounts:
        - mountPath: /var/lib/postgresql/data
          name: postgres-storage
      volumes:
      - name: postgres-storage
        persistentVolumeClaim:
          claimName: postgres-pv-claim
  --- apiVersion: v1
kind: Service
metadata:
  name: postgres-service
  namespace: db-secure
spec:
  selector:
    app: postgres
  ports:
  - port: 5432
    targetPort: 5432
  clusterIP: ClusterIP

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: postgres-statefulset
  namespace: db-secure
spec:
  serviceName: postgres-statefulset
  replicas: 2
  selector:
    matchLabels:
      app: postgres
  template:
    metadata:
      labels:
        app: postgres
    spec:
      containers:
      - name: postgres
        image: postgres:13
        ports:
        - containerPort: 5432
        env:
        - name: POSTGRES_USER
          valueFrom:
            secretKeyRef:
              name: postgres-secret
              key: username
        - name: POSTGRES_PASSWORD
          valueFrom:
            secretKeyRef:
              name: postgres-secret
              key: password
        volumeMounts:
        - mountPath: /var/lib/postgresql/data
          name: postgres-storage
      volumes:
      - name: postgres-storage
        persistentVolumeClaim:
          claimName: postgres-pv-claim
  --- apiVersion: v1
kind: Service
metadata:
  name: postgres-service
  namespace: db-secure
spec:
  selector:
    app: postgres
  ports:
  - port: 5432
    targetPort: 5432
  clusterIP: ClusterIP

apiVersion: apps/v1
kind: Deployment
metadata:
  name: postgres-deployment
  namespace: db-secure
spec:
  replicas: 2
  selector:
    matchLabels:
      app: postgres
  template:
    metadata:
      labels:
        app: postgres
    spec:
      containers:
      - name: postgres
        image: postgres:13
        ports:
        - containerPort: 5432
        env:
        - name: POSTGRES_USER
          value: admin
        - name: POSTGRES_PASSWORD
          value: admin123
        volumeMounts:
        - mountPath: /var/lib/postgresql/data
          name: postgres-storage
      volumes:
      - name: postgres-storage
        persistentVolumeClaim:
          claimName: postgres-pv-claim
  --- apiVersion: v1
kind: Service
metadata:
  name: postgres-service
  namespace: db-secure
spec:
  selector:
    app: postgres
  ports:
  - port: 5432
    targetPort: 5432
  clusterIP: ClusterIP

3 / 10

You are assigned to configure a Kubernetes deployment for a simple web application with specific requirements. The application should meet the following criteria:

The web application should run in the default namespace.
The deployment must use the nginx:latest image.
It should run 3 replicas for high availability.
The application must expose port 80 for HTTP traffic.
Health checks must be implemented to ensure availability by using a liveness probe. The liveness probe should check if the application responds on port 80 every 10 seconds.
Resource limits must be applied to prevent resource starvation, with requests set to 100m CPU and 256Mi memory and limits set to 200m CPU and 512Mi memory.

Which of the following YAML manifests will meet the specified requirements?

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-nginx-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80
        resources:
          requests:
            cpu: 100m
            memory: 256Mi
          limits:
            cpu: 200m
            memory: 512Mi
        livenessProbe:
          httpGet:
            path: /
            port: 80
          initialDelaySeconds: 5
          periodSeconds: 10

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-nginx-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80
        resources:
          requests:
            cpu: 100m
            memory: 256Mi
          limits:
            cpu: 200m
            memory: 512Mi
        livenessProbe:
          tcpSocket:
            port: 80
          initialDelaySeconds: 10
          periodSeconds: 10

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-nginx-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80
        resources:
          requests:
            cpu: 100m
            memory: 256Mi
        livenessProbe:
          exec:
            command: ["sh", "-c", "curl -f http://localhost || exit 1"]
          initialDelaySeconds: 5
          periodSeconds: 15

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-nginx-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80
        livenessProbe:
          httpGet:
            path: /health
            port: 80
        resources:
          limits:
            memory: 512Mi
            cpu: 200m

4 / 10

Question

You need to create a Kubernetes ConfigMap to store configuration settings for a web application. The application expects the following key-value pairs:

APP_ENV=production
APP_DEBUG=false
APP_PORT=8080

Which of the following YAML manifests will correctly create a ConfigMap with these settings?

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  APP_ENV: "production"
  APP_DEBUG: "false"
  APP_PORT: "8080"

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-settings
  namespace: default
data:
  - APP_ENV=production
  - APP_DEBUG=false
  - APP_PORT=8080

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  "APP_ENV": production
  "APP_DEBUG": false
  "APP_PORT": 8080

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  APP_ENV: production
  APP_DEBUG: false
  APP_PORT: 8080

5 / 10

Question

You need to create a Kubernetes ConfigMap to store configuration settings for a web application. The application expects the following key-value pairs:

APP_ENV=production
APP_DEBUG=false
APP_PORT=8080

Which of the following YAML manifests will correctly create a ConfigMap with these settings?

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  APP_ENV: "production"
  APP_DEBUG: "false"
  APP_PORT: "8080"

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-settings
  namespace: default
data:
  - APP_ENV=production
  - APP_DEBUG=false
  - APP_PORT=8080

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  "APP_ENV": production
  "APP_DEBUG": false
  "APP_PORT": 8080

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  APP_ENV: production
  APP_DEBUG: false
  APP_PORT: 8080

6 / 10

Question

You are deploying a new application in a Kubernetes cluster and need to ensure that its configuration is version-controlled and easily reusable. You decide to use a ConfigMap to store non-sensitive configuration data like application settings and environment variables.

You want to create a ConfigMap with the following properties:

Name: app-config
Namespace: default
Contains the following data:
- APP_ENV=production
- APP_LOG_LEVEL=debug

Which of the following YAML manifests will correctly create this ConfigMap?

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  APP_ENV: "production"
  APP_LOG_LEVEL: "debug"

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  APP_ENV=production
  APP_LOG_LEVEL=debug

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  - APP_ENV=production
  - APP_LOG_LEVEL=debug

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
  namespace: default
data:
  APP_ENV: production
  APP_LOG_LEVEL: debug

7 / 10

Question

You are managing a Kubernetes cluster with multiple namespaces. You need to ensure that only certain users can deploy, delete, or edit specific applications in the finance namespace, while other users are restricted from making unauthorized changes.

You decide to use Role-Based Access Control (RBAC) for fine-grained access control. Based on the requirement, you need to create a Role and a RoleBinding to ensure that only members of the finance-team group can create, delete, and update deployments in the finance namespace.

Which of the following YAML manifests will accomplish this requirement?

<pre><code>apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: deployment-role namespace: finance rules: – apiGroups: ["apps"] resources: ["deployments"] verbs: ["*"] — apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: deployment-rolebinding namespace: finance subjects: – kind: Group name: finance-team apiGroup: rbac.authorization.k8s.io roleRef: kind: Role name: deployment-role apiGroup: rbac.authorization.k8s.io</code></pre>

<pre><code>apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: deployment-role namespace: finance rules: – apiGroups: ["apps"] resources: ["deployments"] verbs: ["create", "update", "delete"] — apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: deployment-rolebinding namespace: finance subjects: – kind: Group name: finance-team apiGroup: rbac.authorization.k8s.io roleRef: kind: Role name: deployment-role apiGroup: rbac.authorization.k8s.io</code></pre>

<pre><code>apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: deployment-clusterrole rules: – apiGroups: ["apps"] resources: ["deployments"] verbs: ["create", "delete", "update"] — apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: deployment-clusterrolebinding subjects: – kind: Group name: finance-team apiGroup: rbac.authorization.k8s.io roleRef: kind: ClusterRole name: deployment-clusterrole apiGroup: rbac.authorization.k8s.io</code></pre>

<pre><code>apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: deployment-role namespace: finance rules: – apiGroups: ["apps"] resources: ["deployments"] verbs: ["create"] – apiGroups: ["apps"] resources: ["deployments"] verbs: ["update"] – apiGroups: ["apps"] resources: ["deployments"] verbs: ["delete"] — apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: deployment-rolebinding namespace: finance subjects: – kind: Group name: finance-team apiGroup: rbac.authorization.k8s.io roleRef: kind: Role name: deployment-role apiGroup: rbac.authorization.k8s.io</code></pre>

8 / 10

Question

You are configuring a Kubernetes Ingress resource to expose a web application that runs on service web-service in the default namespace. The application listens on port 80, and you need to ensure it can be accessed using the domain name example.com.

Which of the following manifests will correctly configure an Ingress to meet these requirements?

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-ingress
  namespace: default
spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: web-service
            port:
              number: 80

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-ingress
  namespace: default
spec:
  rule:
    host: example.com
    http:
      paths:
      - path: /
        pathType: ImplementationSpecific
        backend:
          service:
            name: web-service
            port:
              number: 80

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-ingress
  namespace: default
spec:
  rules:
    - host: example.com
      http:
        paths:
          - path: /web
            pathType: Prefix
            backend:
              service:
                name: web-service
                port:
                  number: 80

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-ingress
  namespace: default
spec:
  rules:
  - http:
      paths:
      - path: example.com
        pathType: Prefix
        backend:
          service:
            name: web-service
            port:
              number: 80

9 / 10

Question

You are responsible for configuring Resource Requests and Limits for a stateful database application running on Kubernetes. The database application requires the following:

Minimum CPU request of 500m.
Minimum memory request of 1Gi.
CPU limit of 1 core.
Memory limit of 2Gi.

You must ensure that the application can scale properly without risking overconsumption of cluster resources.

Which of the following YAML manifests correctly configures a StatefulSet to meet these resource requirements?

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: database-statefulset
  namespace: default
spec:
  serviceName: database-service
  replicas: 2
  selector:
    matchLabels:
      app: database
  template:
    metadata:
      labels:
        app: database
    spec:
      containers:
      - name: database-container
        image: database:latest
        resources:
          requests:
            cpu: "500m"
            memory: "1Gi"
          limits:
            cpu: "1"
            memory: "2Gi"

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: database-statefulset
  namespace: default
spec:
  serviceName: database-service
  replicas: 2
  selector:
    matchLabels:
      app: database
  template:
    metadata:
      labels:
        app: database
    spec:
      containers:
      - name: database-container
        image: database:latest
        resources:
          limits:
            cpu: "1"
            memory: "2Gi"
          requests:
            cpu: "500m"
            memory: "1Gi"

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: database-statefulset
  namespace: default
spec:
  serviceName: database-service
  replicas: 2
  selector:
    matchLabels:
      app: database
  template:
    metadata:
      labels:
        app: database
    spec:
      containers:
      - name: database-container
        image: database:latest
        resources:
          requests:
            cpu: "1000m"
            memory: "2Gi"
          limits:
            cpu: "1m"
            memory: "1Gi"

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: database-statefulset
  namespace: default
spec:
  serviceName: database-service
  replicas: 2
  selector:
    matchLabels:
      app: database
  template:
    metadata:
      labels:
        app: database
    spec:
      containers:
      - name: database-container
        image: database:latest
        resources:
          requests:
            cpu: "500m"
            memory: "1Gi"
          limits:
            cpu: "500m"
            memory: "1Gi"

10 / 10

You are tasked with configuring a Kubernetes Deployment for a Node.js application. The application must meet the following requirements:

It should have 3 replicas running at all times.
It should use the image node:14.
The application should listen on port 3000.
A liveness probe should be defined to check that the application is alive by hitting /healthz.
The application must restart if it becomes unresponsive.

Which of the following manifests will meet the specified requirements?

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nodejs-app-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nodejs-app
  template:
    metadata:
      labels:
        app: nodejs-app
    spec:
      containers:
      - name: nodejs-container
        image: node:14
        ports:
        - containerPort: 3000
        livenessProbe:
          httpGet:
            path: /healthz
            port: 3000
          initialDelaySeconds: 5
          periodSeconds: 10

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nodejs-app-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nodejs-app
  template:
    metadata:
      labels:
        app: nodejs-app
    spec:
      containers:
      - name: nodejs-container
        image: node:14
        ports:
        - containerPort: 3000
        livenessProbe:
          httpGet:
            path: /healthz
            port: 3000
          timeoutSeconds: 2

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nodejs-app-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nodejs-app
  template:
    metadata:
      labels:
        app: nodejs-app
    spec:
      containers:
      - name: nodejs-container
        image: node:14
        ports:
        - containerPort: 3000
        livenessProbe:
          exec:
            command: ["curl", "-f", "http://localhost:3000/healthz"]
          initialDelaySeconds: 10
          periodSeconds: 15

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nodejs-app-deployment
  namespace: default
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nodejs-app
  template:
    metadata:
      labels:
        app: nodejs-app
    spec:
      containers:
      - name: nodejs-container
        image: node:14
        ports:
        - containerPort: 3000
        livenessProbe:
          httpGet:
            path: /healthz
            port: 3000
          failureThreshold: 5

Your score is

The average score is 0%

Correct Answer: A

Explanation:

Why Other Options Are Incorrect:

Correct Answer: A

Explanation:

Why Other Options Are Incorrect:

Question

Correct Answer: C

Explanation:

Why Other Options Are Incorrect:

Correct Answer: C

Explanation:

Why Other Options Are Incorrect:

Correct Answer: A

Explanation:

Why Other Options Are Incorrect:

Correct Answer: A

Explanation:

Why Other Options Are Incorrect:

Question

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect

Question

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect

Question

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect

Question

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect

Question

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect

Question

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect

Correct Answer: A

Why Other Options Are Incorrect