Kubernetes Container Orchestration Cloud Native Patterns 5

Question 1

Which cloud native pattern describes deploying a new version alongside the old version and gradually shifting traffic from old to new?

Accepted Answer

Canary Release

Answer

A Canary Release routes a small percentage of traffic to the new version first, allowing validation before full rollout.

Question 2

In a Blue-Green deployment on Kubernetes, how is traffic switched from the old (blue) version to the new (green) version?

Accepted Answer

By updating the Service selector to point to the green Deployment's pods

Answer

Switching the Kubernetes Service's label selector from blue pods to green pods instantly redirects all traffic to the new version.

Question 3

What Kubernetes feature enables the 'Anti-Affinity' cloud native pattern to improve resilience?

Accepted Answer

podAntiAffinity rules that spread replicas across nodes or zones

Answer

podAntiAffinity rules instruct the scheduler to place pod replicas on different nodes or zones, preventing a single failure from taking down all replicas.

Question 4

The 'Twelve-Factor App' methodology's 'Config' factor states that configuration should be stored in:

Accepted Answer

Environment variables injected at runtime, not in the codebase

Answer

Factor III of the Twelve-Factor App requires config to be separated from code and injected via environment variables, enabling the same build to run in any environment.

Question 5

Which cloud native pattern ensures that an operation produces the same result whether applied once or multiple times?

Accepted Answer

Idempotency

Answer

Idempotency guarantees that repeating the same operation has no additional effect beyond the first application, which is critical for safe retries in distributed systems.

Kubernetes Container Orchestration Practice Test

Kubernetes Container Orchestration Practice Test

Kubernetes Container Orchestration Cloud Native Patterns 5