Question 1hardmultiple choice
Read the full Application Design and Build explanation →CKAD Application Design and Build • Complete Question Bank
Complete CKAD Application Design and Build question bank — all 0 questions with answers and detailed explanations.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Smallest deployable unit running containers
Stable network endpoint for a set of pods
Store non-sensitive configuration data
Request for storage resources
HTTP and HTTPS routing to services
Drag a concept onto its matching description — or click a concept then click the description.
Exposes service on a cluster-internal IP
Exposes service on each node's IP at a static port
Exposes service externally using a cloud load balancer
Maps service to a DNS name
No cluster IP; used for stateful workloads
Consider the following partial Dockerfile: FROM alpine:3.18 AS builder RUN apk add --no-cache curl COPY src /app/src RUN make /app/bin
FROM alpine:3.18 COPY --from=builder /app/bin /app/bin CMD ["/app/bin"] What is the primary benefit of this multi-stage build?
You have a Job that runs a batch process. The Job YAML is as follows:
apiVersion: batch/v1 kind: Job metadata: name: batch-job spec: parallelism: 4 completions: 12 backoffLimit: 2 template: spec: containers: - name: worker image: myapp:latest restartPolicy: Never
If one pod fails after 3 successful completions, and the Job has already completed 7 successes, how many pods will be running at that point? Assume no other failures.