CLF-C02 Cloud Concepts Practice Question
A company is designing a microservices architecture on AWS. According to the AWS Well-Architected Framework's Operational Excellence pillar, which practice best supports the ability to safely make frequent, small changes to production?
⚠ Common exam trap
Watch out — candidates often confuse 'operational excellence' with 'security' or 'cost optimization' and choose manual approval (Option C) thinking it adds safety, but the Well-Architected Framework explicitly advocates for automation over manual gates to enable safe, high-velocity changes.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Making frequent, small, reversible changes through automated CI/CD pipelines
The Operational Excellence pillar emphasizes the ability to make frequent, small, reversible changes to reduce the blast radius of failures and enable rapid recovery. Automated CI/CD pipelines enforce consistent deployment practices, allowing teams to safely iterate on production with minimal risk. This approach aligns with the principle of 'perform operations as code' and supports the 'make frequent, small, reversible changes' design principle.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Performing large batch deployments monthly to minimize change frequency
Why it's wrong here
Batching huge deployments into monthly windows concentrates risk: the blast radius of any failure expands to touch weeks of accumulated work, making root-cause isolation difficult and rollbacks risky because many interdependent changes must be reverted together. This contradicts the Operational Excellence principle of small, low-risk increments, where each release is narrow enough to validate safely.
- ✓
Making frequent, small, reversible changes through automated CI/CD pipelines
Why this is correct
Frequent, small, reversible changes implemented through automated CI/CD pipelines are the prescribed approach under the Operational Excellence pillar because they limit the potential impact of any single release, speed up rollback by reverting a small delta, and create natural, incremental checkpoints for feedback. Automation also removes human variability from deployment execution, so each change follows identical, reliable steps and failures can be detected and corrected quickly.
- ✗
Requiring manual approval for every code change
Why it's wrong here
Requiring manual approval for every code change introduces a human bottleneck that slows delivery and, paradoxically, increases risk because system updates become less timely and emergency fixes wait in queues. The recommended model uses automated quality gates (tests, scans, policy checks) within a CI/CD pipeline, with manual sign-off reserved for only the most privileged or high-impact production releases, not as a blanket mandate.
- ✗
Deploying all microservices simultaneously in coordinated releases
Why it's wrong here
Coordinating all microservices releases as one synchronized unit greatly amplifies the blast radius: a defect in any single service can take down the entire deployment, and when services have independent lifecycles, trying to wrap them in a single release forces brittle coupling and complicates rollback because you cannot revert one service without reverting others. Internal, independent deployability is a core microservices tenet—each service should be deployable on its own cadence through its own pipeline.
Quick reference
AAA Protocol Comparison
| Protocol | Port(s) | Encryption | Transport | Primary Use |
|---|---|---|---|---|
| RADIUS | 1812 / 1813 | Password only | UDP | Network access control |
| TACACS+ | 49 | Full packet | TCP | Device administration |
| Diameter | 3868 | Full session | TCP / SCTP | Carrier / mobile networks |
| 802.1X | — | EAP-based | Layer 2 | Port-based access control |
TACACS+ encrypts the entire packet; RADIUS only encrypts the password field — a key exam distinction.
Go deeper
Related to this question
About these practice questions
This CLF-C02 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CLF-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CLF-C02 exam.