KCNA Cloud Native Patterns 3 — Questions and Answers
Question 1: Which cloud native pattern involves deploying infrastructure and configuration through version-controlled code rather than manual processes?
- GitOps (Correct answer)
- Infrastructure as Code
- Immutable Infrastructure
- Blue-Green Deployment
Correct answer: GitOps
GitOps uses Git as the single source of truth for declarative infrastructure and application state, with automated reconciliation.
Question 2: In a microservices architecture, what is the Saga pattern used for?
- Managing distributed transactions across multiple services (Correct answer)
- Routing traffic between service replicas
- Aggregating logs from multiple services
- Scaling services based on message queue depth
Correct answer: Managing distributed transactions across multiple services
The Saga pattern coordinates distributed transactions by breaking them into a sequence of local transactions with compensating actions for rollback.
Question 3: What is the key characteristic of Immutable Infrastructure?
- Servers are never modified after deployment; changes require new deployments (Correct answer)
- Infrastructure is defined in code and checked into version control
- Infrastructure automatically scales based on demand
- Containers share the host OS kernel
Correct answer: Servers are never modified after deployment; changes require new deployments
Immutable Infrastructure means deployed artifacts are never changed in place; any update requires replacing the artifact with a new version.
Question 4: Which deployment pattern minimizes downtime by running two identical production environments and switching traffic between them?
- Blue-Green Deployment (Correct answer)
- Canary Deployment
- Rolling Update
- Recreate Deployment
Correct answer: Blue-Green Deployment
Blue-Green Deployment maintains two identical environments and switches traffic from one to the other, enabling instant rollback if issues arise.
Question 5: In the Backends for Frontends (BFF) pattern, what is the purpose of creating separate backends for different client types?
- To tailor API responses and logic specifically for each client's needs (Correct answer)
- To provide a single caching layer for all client types
- To enforce consistent authentication across all clients
- To aggregate metrics from all client types in one place
Correct answer: To tailor API responses and logic specifically for each client's needs
BFF creates dedicated backend services for each client type (mobile, web, etc.) allowing each to be optimized independently without compromising others.
Question 6: What does the Canary Deployment pattern allow teams to do?
- Roll out changes to a small subset of users before full release (Correct answer)
- Deploy two versions simultaneously and switch instantly
- Automatically roll back deployments that fail health checks
- Deploy updates to all instances at the same time
Correct answer: Roll out changes to a small subset of users before full release
Canary Deployment gradually shifts traffic to the new version, limiting blast radius by exposing only a fraction of users to the change initially.
Question 7: In cloud native observability, what are the three pillars commonly referred to?
- Logs, Metrics, and Traces (Correct answer)
- Availability, Latency, and Throughput
- CPU, Memory, and Network
- Alerting, Dashboarding, and Incident Response
Correct answer: Logs, Metrics, and Traces
The three pillars of observability are logs (events), metrics (measurements over time), and traces (request flow across services).
KCNA Cloud Native Patterns 3
Which cloud native pattern involves deploying infrastructure and configuration through version-controlled code rather than manual processes?