CAD (Certified Agile Developer) Exam — Questions and Answers

Question 1: A team member is blocked by an external dependency. According to Agile, who should resolve this impediment?

The Scrum Master should work to remove the impediment (Correct answer)
The Product Owner should escalate it to senior management
The entire team must stop work until the impediment is cleared
The team member must resolve it independently without bothering others

Correct answer: The Scrum Master should work to remove the impediment

Removing impediments is a core responsibility of the Scrum Master, who serves the team by clearing obstacles to progress.

Question 2: In continuous integration, how does automated static code analysis contribute to code quality?

It replaces the need for manual testing entirely
It measures the speed of the deployment pipeline
It automatically fixes all detected issues without developer intervention
It detects potential bugs, code smells, and style violations early in the development cycle before code is merged (Correct answer)

Correct answer: It detects potential bugs, code smells, and style violations early in the development cycle before code is merged

Static analysis tools scan code for potential issues during the CI pipeline, catching problems before they reach production.

Question 3: What does the concept of 'psychological safety' contribute to agile team collaboration?

It guarantees that retrospectives remain confidential from management
It allows team members to speak up, take risks, and admit mistakes without fear of punishment (Correct answer)
It requires senior developers to mentor junior ones during pairing sessions
It ensures all team members feel safe from layoffs

Correct answer: It allows team members to speak up, take risks, and admit mistakes without fear of punishment

Psychological safety enables honest communication and experimentation, which are foundational to continuous improvement in agile.

Question 4: In a CI/CD pipeline, what is the purpose of a smoke test executed immediately after deployment?

To quickly verify that critical application paths are functional in the new environment (Correct answer)
To check the syntax of the pipeline configuration file
To validate that all unit tests pass before the build starts
To perform exhaustive load testing under peak traffic conditions

Correct answer: To quickly verify that critical application paths are functional in the new environment

Smoke tests are lightweight checks run right after deployment to confirm the application's core functionality is working.

Question 5: What is 'code smell' in the context of Agile software quality?

A runtime exception caused by null references
A surface indication in the code that usually corresponds to a deeper design problem (Correct answer)
A deprecated API that has been officially removed
A syntax error that prevents compilation

Correct answer: A surface indication in the code that usually corresponds to a deeper design problem

Code smells are patterns in code that suggest the presence of deeper structural or design issues, even though the code may function correctly.

Question 6: A class uses switch statements based on the type of an object in multiple places. Which refactoring pattern resolves this?

Introduce Null Object
Consolidate Duplicate Conditional Fragments
Replace Conditional with Polymorphism (Correct answer)
Replace Type Code with Subclasses

Correct answer: Replace Conditional with Polymorphism

Replace Conditional with Polymorphism moves each branch of a type-based switch into an overridden method in a subclass, leveraging OOP dispatch.

Question 7: Which scenario best illustrates the Agile value 'Individuals and interactions over processes and tools'?

Management installs automated reporting tools to monitor team activity
The team follows a rigid process checklist for every code review
The team spends three weeks selecting the perfect project management tool before starting
Two developers resolve a design conflict through a quick conversation rather than filing formal change requests (Correct answer)

Correct answer: Two developers resolve a design conflict through a quick conversation rather than filing formal change requests

Choosing direct human conversation over formal bureaucratic processes exemplifies the first manifesto value in practice.

Question 8: What is a 'test double' in TDD terminology?

A generic term for objects that stand in for real dependencies in tests (Correct answer)
A duplicate test used for comparison
Running each test twice to check for flakiness
A test that covers two related behaviors

Correct answer: A generic term for objects that stand in for real dependencies in tests

Test doubles (mocks, stubs, fakes, spies, dummies) replace real collaborators to isolate the unit under test.

Question 9: In Agile, what is the primary reason for conducting a retrospective?

To plan the next iteration's work items
To inspect and adapt the team's process for continuous improvement (Correct answer)
To review and approve code changes
To demo completed features to stakeholders

Correct answer: To inspect and adapt the team's process for continuous improvement

Retrospectives allow the team to reflect on their process and identify improvements for future iterations.

Question 10: An Agile team's workflow automatically triggers a build and runs all unit and integration tests upon every commit to the main branch. If all tests pass, the application is packaged and stored in an artifact repository. To move this package to the production environment, a release manager must manually initiate the deployment. What level of automation has this team primarily achieved?

Continuous Delivery
Ad-hoc Integration
Continuous Deployment
Continuous Integration (Correct answer)

Correct answer: Continuous Integration

The team has successfully implemented Continuous Integration because every commit is automatically built and tested, creating a verified artifact. They have not achieved Continuous Delivery, which would imply that the artifact is also automatically deployed to a production-like environment, making the final release a simple business decision. Continuous Deployment would involve automatically deploying to production without any manual gate.

Question 11: A team consistently completes fewer story points than planned each sprint. The retrospective finds no blockers. What should the team examine FIRST?

Whether the release roadmap needs to be publicly shared
Whether their estimation technique is accurately sizing stories (Correct answer)
Whether the Scrum Master is attending daily standups
Whether the sprint duration is too long

Correct answer: Whether their estimation technique is accurately sizing stories

Persistent under-delivery without external blockers usually points to inaccurate estimation; recalibrating story point sizing aligns plans with actual team capacity.

Question 12: What agile practice directly prevents the buildup of technical debt by requiring all new code to meet quality standards before merging?

Sprint Planning
Definition of Done (DoD) (Correct answer)
Backlog Refinement
Sprint Retrospective

Correct answer: Definition of Done (DoD)

The Definition of Done includes code quality criteria (tests, reviews, refactoring) that must be met before any work item is considered complete.

Question 13: When comparing Scrum and SAFe, which event in SAFe is most analogous to Scrum's Sprint Review?

PI Planning
Solution Demo
Inspect and Adapt workshop
System Demo (Correct answer)

Correct answer: System Demo

The SAFe System Demo, held at the end of each iteration, serves as the ART-level equivalent of Scrum's Sprint Review, demonstrating integrated working software to stakeholders.

Question 14: How does the Agile mindset view changes to requirements late in the development process?

Reject them to protect the current sprint scope
Welcome them as a competitive advantage for the customer (Correct answer)
Accept them only if the timeline extends
Document them for the next release cycle

Correct answer: Welcome them as a competitive advantage for the customer

Agile processes harness change for the customer's competitive advantage, even late in development.

Question 15: Which of the following Agile methodologies is characterized by its strong emphasis on technical engineering practices such as pair programming, continuous integration, and collective code ownership?

Lean
Scrum
Extreme Programming (XP) (Correct answer)
Kanban

Correct answer: Extreme Programming (XP)

Extreme Programming (XP) is distinguished from other Agile frameworks by its intense focus on technical excellence and specific engineering practices. Core practices like pair programming, Test-Driven Development (TDD), continuous integration, and collective code ownership are central to the XP methodology to produce high-quality software.

Question 16: A team member consistently dominates sprint retrospectives, preventing others from sharing feedback. What should the Scrum Master do first?

Escalate the issue to management immediately
Use structured facilitation techniques like round-robin or silent writing (Correct answer)
Exclude the team member from future retrospectives
Cancel retrospectives until behavior improves

Correct answer: Use structured facilitation techniques like round-robin or silent writing

Structured facilitation techniques ensure all voices are heard without singling out the dominant member.

Question 17: Which of the following is a primary goal of code refactoring in an agile environment?

To achieve 100% code coverage with unit tests.
To reduce the number of user stories in the backlog.
To eliminate the need for a dedicated QA team.
To reduce technical debt and improve maintainability. (Correct answer)

Correct answer: To reduce technical debt and improve maintainability.

Refactoring is a key practice for managing and reducing technical debt. By continuously improving the internal code structure, teams make the software easier to maintain, adapt, and extend in future sprints, which is crucial for agility.

Question 18: A product owner frequently changes sprint goals mid-sprint, disrupting the team. What should the Scrum Master do?

Allow all changes since the product owner has authority over the backlog
Shield the team by educating the product owner on sprint commitment and scope protection (Correct answer)
Have the team ignore the product owner's requests
Remove the product owner from sprint planning meetings

Correct answer: Shield the team by educating the product owner on sprint commitment and scope protection

The Scrum Master protects the team from mid-sprint disruptions by coaching the product owner on agile boundaries.

Question 19: What type of environment does the Agile mindset recommend providing to motivated individuals?

Comprehensive training before any project involvement
Strict deadlines and detailed task assignments
The environment and support they need, then trust them to get the job done (Correct answer)
Constant oversight with daily status reports

Correct answer: The environment and support they need, then trust them to get the job done

Agile principles state that projects should be built around motivated individuals who are given the environment, support, and trust they need.

Question 20: A team is estimating a complex integration story. Three developers estimate 8 points while two estimate 13 points. What should happen next in Planning Poker?

The scrum master decides the final estimate
Use the majority estimate of 8 points
Average the estimates to get 10 points
The highest and lowest estimators explain their reasoning, then the team re-estimates (Correct answer)

Correct answer: The highest and lowest estimators explain their reasoning, then the team re-estimates

When estimates diverge in Planning Poker, the outliers discuss their reasoning to surface hidden assumptions before the team votes again.

Question 21: Which practice helps ensure that automated tests in a CI pipeline remain trustworthy?

Writing tests only for new features, not bug fixes
Eliminating flaky tests and ensuring each test produces deterministic results (Correct answer)
Running tests only on weekends to reduce server load
Allowing tests to pass intermittently without investigation

Correct answer: Eliminating flaky tests and ensuring each test produces deterministic results

Flaky tests erode confidence in the CI pipeline, so teams must fix or remove non-deterministic tests to keep the suite reliable.

Question 22: What role does 'trust' play in Agile teams according to the Manifesto principle on self-organization?

The best architectures emerge from self-organizing teams that are trusted to make decisions (Correct answer)
Management must verify all team decisions daily
Only senior developers can be trusted with architectural decisions
Trust is irrelevant; processes enforce quality

Correct answer: The best architectures emerge from self-organizing teams that are trusted to make decisions

Principle 11 states that the best architectures, requirements, and designs emerge from self-organizing teams, implying management must trust teams with decision-making authority.

Question 23: What is 'code coverage' and what is its limitation as a CI quality gate?

The ratio of passing to failing tests; limited by network speed
The percentage of source lines executed by tests; high coverage does not guarantee tests verify correct behavior (Correct answer)
The number of features covered by the product backlog
The percentage of user stories tested manually; unreliable for automated pipelines

Correct answer: The percentage of source lines executed by tests; high coverage does not guarantee tests verify correct behavior

Code coverage measures which lines are executed, but tests can achieve 100% coverage while still missing wrong logic or edge cases.

Question 24: An agile team has members across three time zones. Which approach best supports effective daily standups?

Always scheduling at the time most convenient for the majority
Having each time zone hold its own separate standup
Rotating the standup time so the burden of off-hours meetings is shared equally (Correct answer)
Replacing standups with email status reports

Correct answer: Rotating the standup time so the burden of off-hours meetings is shared equally

Rotating meeting times demonstrates respect for all team members and distributes the inconvenience of off-hours participation fairly across the distributed team.

Question 25: What is the main benefit of conducting sprint retrospectives for development practices?

To plan the next sprint's backlog
To continuously improve the team's processes and practices (Correct answer)
To present completed work to stakeholders
To blame team members for missed deadlines

Correct answer: To continuously improve the team's processes and practices

Retrospectives enable teams to inspect and adapt their processes for continuous improvement.

Question 26: What is the primary purpose of a team working agreement in Agile collaborative development?

To document individual performance metrics for reviews
To establish norms and expectations for how the team will work together (Correct answer)
To replace the sprint backlog with a shared task list
To serve as a contract between the team and the product owner

Correct answer: To establish norms and expectations for how the team will work together

A working agreement captures team norms — communication, code standards, meeting rules — that guide collaboration.

Question 27: A CI pipeline runs static code analysis. What is the primary benefit?

It generates user acceptance test cases
It catches code quality issues, security vulnerabilities, and style violations automatically before merge (Correct answer)
It measures application performance under load
It replaces the need for unit tests

Correct answer: It catches code quality issues, security vulnerabilities, and style violations automatically before merge

Static analysis tools scan code without executing it, catching bugs, code smells, and security issues early in the pipeline.

Question 28: Which Agile framework explicitly defines three main roles: Driver, Navigator, and Supporter?

Feature-Driven Development
Scrum
Dynamic Systems Development Method (DSDM) (Correct answer)
Crystal Clear

Correct answer: Dynamic Systems Development Method (DSDM)

DSDM defines specific roles including Business Sponsor, Business Visionary, and Solution Developer, with governance-focused roles that guide and support delivery.

Question 29: What is the recommended approach when a TDD practitioner discovers a bug in production code?

Rewrite the entire module using TDD from scratch
Fix the bug immediately and then run existing tests
Add the bug to the backlog and address it in the next sprint
Write a failing test that reproduces the bug before writing the fix (Correct answer)

Correct answer: Write a failing test that reproduces the bug before writing the fix

Writing a failing test first ensures the bug is captured as a regression test, preventing it from reoccurring after the fix is applied.

Question 30: Which statement best reflects the Agile mindset regarding failure?

Failure should be hidden from stakeholders to maintain confidence
Failure is a learning opportunity that drives continuous improvement (Correct answer)
Failure is unacceptable and those responsible must be identified
Failure must be avoided at all costs through rigorous planning

Correct answer: Failure is a learning opportunity that drives continuous improvement

Agile teams treat failures as learning opportunities, using retrospectives and inspect-and-adapt cycles to improve continuously.

Question 31: In a CI/CD workflow, what does 'trunk-based development' emphasize?

Maintaining long-lived feature branches for stability
Developers committing to a single shared branch frequently (Correct answer)
Avoiding merges until the end of a sprint
Using separate repositories for each team

Correct answer: Developers committing to a single shared branch frequently

Trunk-based development encourages frequent commits to a single main branch to reduce merge conflicts and enable continuous integration.

Question 32: In a CI/CD workflow, what does the term 'pipeline as code' refer to?

Writing application code that self-deploys without any pipeline
Storing pipeline logs inside the application database
Using a graphical drag-and-drop tool to design the pipeline
Defining build, test, and deploy stages in a version-controlled configuration file (Correct answer)

Correct answer: Defining build, test, and deploy stages in a version-controlled configuration file

Pipeline as code means the entire CI/CD pipeline definition lives in a versioned file (e.g., Jenkinsfile, .gitlab-ci.yml) alongside the source code.

Question 33: A team wants to deploy code for a large, multi-sprint feature to production continuously without making it visible to end-users until it is complete. Which technique BEST supports this practice in a Continuous Delivery environment?

Commenting out all the incomplete code before each deployment and uncommenting it later.
Creating a long-lived feature branch that will only be merged into the mainline upon completion.
Deploying the new code to a separate, isolated staging server but not to the production server.
Using feature toggles (or flags) to keep the incomplete functionality hidden in the production environment. (Correct answer)

Correct answer: Using feature toggles (or flags) to keep the incomplete functionality hidden in the production environment.

Feature toggles (also known as feature flags) are a powerful technique used to decouple deployment from release. They allow teams to wrap new, incomplete features in conditional logic, enabling the code to be deployed to production but remain inactive or hidden from users. This supports continuous integration of all code to the mainline while giving the business control over when a feature is released to customers.

Question 34: What does the Agile mindset consider the primary measure of progress?

Number of features deployed
Completed story points
Test coverage percentage
Working software (Correct answer)

Correct answer: Working software

The Agile Manifesto explicitly states that working software is the primary measure of progress.

Question 35: What is meant by 'Agile Principle 12'—the team regularly reflects and adjusts behavior?

Teams must rewrite their working agreements monthly
Annual performance reviews replace retrospectives in mature Agile teams
At regular intervals the team reflects on how to become more effective and adjusts accordingly (Correct answer)
Project managers review team performance and enforce improvements

Correct answer: At regular intervals the team reflects on how to become more effective and adjusts accordingly

Principle 12 is the foundation for retrospectives: the team itself reflects on effectiveness and autonomously tunes its behavior, not management imposing changes.

Question 36: What does code coverage measure in the context of TDD?

The proportion of production code lines executed by automated tests (Correct answer)
The ratio of passing tests to total tests
The percentage of user stories tested in a sprint
The number of defects found per test run

Correct answer: The proportion of production code lines executed by automated tests

Code coverage measures what percentage of production source lines, branches, or paths are exercised by the existing automated test suite.

Question 37: A team wants to reduce the 'hero developer' anti-pattern where one person saves every sprint. What practice helps most?

Cross-train team members and cap individual contributions through pairing and rotation (Correct answer)
Reduce sprint scope to eliminate the need for heroics
Give the hero developer a formal leadership title to match their role
Hire more developers so the hero has backup

Correct answer: Cross-train team members and cap individual contributions through pairing and rotation

Cross-training and pairing spread capability so no single developer becomes the indispensable rescuer every sprint.

Question 38: How does feature flagging support continuous delivery practices?

By replacing the need for a staging environment
By preventing developers from committing code until a feature is complete
By allowing incomplete features to be merged and deployed without being visible to users (Correct answer)
By automatically generating release notes for each deployment

Correct answer: By allowing incomplete features to be merged and deployed without being visible to users

Feature flags decouple deployment from release, allowing teams to merge and deploy incomplete features safely while controlling their visibility.

Question 39: What is the primary purpose of a Sprint Review in Scrum?

To document all bugs found during the Sprint
To plan the next Sprint backlog in detail
To evaluate individual team member performance
To inspect the increment and adapt the Product Backlog based on stakeholder feedback (Correct answer)

Correct answer: To inspect the increment and adapt the Product Backlog based on stakeholder feedback

The Sprint Review is a collaboration session where the team demonstrates the increment and stakeholders provide feedback to inform future work.

Question 40: What is the 'Strangler Fig' pattern used for in Agile refactoring?

Gradually replacing a legacy system by incrementally building new functionality around it (Correct answer)
Duplicating the entire codebase before making changes
Removing all legacy code in a single sprint
Adding a wrapper class around every legacy module

Correct answer: Gradually replacing a legacy system by incrementally building new functionality around it

The Strangler Fig pattern incrementally replaces parts of a legacy system with new implementations until the old system can be completely decommissioned.

Question 41: A team's velocity has been 40, 42, 38, and 41 over the last four sprints. The Product Owner asks when 200 points of remaining work will be completed. What is the BEST response?

It is impossible to provide any estimate whatsoever
Commit to delivering in 4 sprints to motivate the team
Exactly 5 sprints from now
Approximately 5 sprints, based on the team's average velocity of about 40 points per sprint (Correct answer)

Correct answer: Approximately 5 sprints, based on the team's average velocity of about 40 points per sprint

Using the average velocity of approximately 40 points per sprint gives a reasonable forecast of about 5 sprints for 200 points of work.

Question 42: Why is feedback essential in Agile collaboration?

To avoid user involvement
To ensure continuous improvement (Correct answer)
To focus solely on development tasks
To delay product delivery

Correct answer: To ensure continuous improvement

Frequent feedback ensures continuous improvement, allowing teams to adapt and refine their work based on stakeholder and team input.

Question 43: How frequently should business people and developers work together according to Agile principles?

Daily throughout the project (Correct answer)
At milestone reviews
Weekly status meetings are sufficient
During sprint planning only

Correct answer: Daily throughout the project

Principle 4 states that business people and developers must work together daily throughout the project.

Question 44: Why should refactoring be performed in small, incremental steps rather than large-scale rewrites?

To avoid the need for version control
To ensure only one developer works on the code at a time
To maintain a working system at all times and reduce the risk of introducing defects (Correct answer)
To eliminate the need for automated testing

Correct answer: To maintain a working system at all times and reduce the risk of introducing defects

Small incremental refactoring steps keep the system functional throughout the process, making it easier to identify and fix any issues that arise.

Question 45: What is 'velocity' in the context of Scrum?

The speed at which developers type code
The number of defects fixed per iteration
The sum of story points completed by a team in a sprint (Correct answer)
The rate at which the product backlog grows

Correct answer: The sum of story points completed by a team in a sprint

Velocity is the total story points a team completes in a sprint, used to forecast how much work can be taken in future sprints.

Question 46: Which behavior BEST reflects a Scrum Master acting as a servant-leader?

Approving or rejecting backlog items based on technical feasibility
Assigning tasks to team members based on their skill assessments
Setting the sprint goal based on stakeholder priorities
Removing organizational impediments so the team can work without obstruction (Correct answer)

Correct answer: Removing organizational impediments so the team can work without obstruction

A servant-leader Scrum Master prioritizes the team's needs, removing obstacles rather than directing or controlling work.

Question 47: During sprint planning, the team commits to more work than their historical velocity suggests they can complete. What Agile risk does this create?

Unused capacity that wastes sprint time
Overcommitment leading to incomplete sprint goals and reduced team morale (Correct answer)
Scope creep from the product owner
Violation of the WIP limit causing Kanban board overflow

Correct answer: Overcommitment leading to incomplete sprint goals and reduced team morale

Consistently overcommitting leads to unfinished sprint goals, erodes stakeholder trust, and demoralizes the team when they fail to meet self-imposed targets.

Question 48: In SAFe's portfolio level, what is the primary function of an 'Epic' owner?

Writing user stories within an Epic
Championing a portfolio Epic through the Kanban system and coordinating its analysis and approval (Correct answer)
Facilitating PI Planning events for the portfolio
Assigning Epics to Agile Release Trains

Correct answer: Championing a portfolio Epic through the Kanban system and coordinating its analysis and approval

An Epic owner is responsible for championing a portfolio Epic, collaborating with stakeholders, and driving it through the portfolio Kanban to ensure it gets properly analyzed and prioritized.

Question 49: Which factor should NOT influence story point estimation?

Technical complexity of the implementation
Amount of effort required relative to other stories
The number of hours a specific developer would take to complete it (Correct answer)
Uncertainty and risk involved in the work

Correct answer: The number of hours a specific developer would take to complete it

Story points measure relative complexity, effort, and uncertainty — not the hours a specific individual would need, which varies by person.

Question 50: Which practice is most aligned with maintaining code quality in an agile team?

Assigning a dedicated refactoring team separate from the feature team
Performing a full code review sprint every quarter
Integrating refactoring into every sprint alongside feature development (Correct answer)
Waiting until technical debt accumulates before addressing it

Correct answer: Integrating refactoring into every sprint alongside feature development

Agile teams treat refactoring as a continuous activity woven into every sprint, preventing technical debt from accumulating.

Question 51: In Agile, who is responsible for writing automated acceptance tests?

Only the QA team
The whole team collaboratively — developers, testers, and product owners (Correct answer)
An external testing vendor
Only the developer who wrote the feature

Correct answer: The whole team collaboratively — developers, testers, and product owners

Acceptance test authorship is a shared activity in Agile, ensuring tests reflect business intent and technical correctness.

Question 52: A team notices that their cycle time has increased over the past three sprints. Which investigation approach is MOST aligned with agile principles?

Reduce the number of story points accepted each sprint automatically
Stop measuring cycle time to avoid team stress
Hold a retrospective to identify process inefficiencies or bottlenecks causing the increase (Correct answer)
Blame the most recently added team member for the slowdown

Correct answer: Hold a retrospective to identify process inefficiencies or bottlenecks causing the increase

Agile's inspect-and-adapt cycle means using metrics to surface problems, then collaboratively diagnosing and fixing root causes in retrospectives.

Question 53: What distinguishes Behavior-Driven Development (BDD) from Test-Driven Development (TDD)?

BDD is done after coding; TDD is done before
BDD uses natural language specifications shared with stakeholders; TDD uses code-level tests written by developers (Correct answer)
BDD focuses on system performance, TDD on unit correctness
BDD replaces unit tests; TDD replaces integration tests

Correct answer: BDD uses natural language specifications shared with stakeholders; TDD uses code-level tests written by developers

BDD extends TDD by expressing tests in human-readable language (e.g., Gherkin) to align developers, testers, and business stakeholders.

Question 54: A manager new to Agile is concerned that the team is not producing enough detailed design documentation upfront before starting to code. An Agile mindset would suggest that...

The best architectures, requirements, and designs emerge from self-organizing teams as they work, rather than from a large upfront design phase. (Correct answer)
Documentation is not an Agile practice and should be eliminated entirely.
Only the senior developer is responsible for creating and maintaining documentation.
The team should create a comprehensive documentation suite for all features before implementation to satisfy the manager.

Correct answer: The best architectures, requirements, and designs emerge from self-organizing teams as they work, rather than from a large upfront design phase.

A key Agile principle is that 'The best architectures, requirements, and designs emerge from self-organizing teams.' This supports the idea of emergent design. The Agile value 'Working software over comprehensive documentation' also applies, prioritizing the creation of a functional product over extensive preliminary paperwork. While documentation isn't eliminated, it's created in a just-in-time, lightweight manner.

Question 55: What is a 'Definition of Done' (DoD) in Agile?

The final sign-off document approved by the Product Owner at project end
A legal document defining project acceptance criteria
A shared understanding of criteria a Product Backlog item must meet to be considered complete (Correct answer)
A checklist each developer creates for their own tasks

Correct answer: A shared understanding of criteria a Product Backlog item must meet to be considered complete

The DoD is a transparent, agreed-upon checklist ensuring all team members have the same understanding of what 'complete' means for any increment.

Question 56: A team practicing Scrumban decides to trigger a planning session 'on demand' rather than on a fixed schedule. Which Kanban concept enables this approach?

Fixed sprint boundaries
Daily standups
Velocity-based capacity planning
Replenishment meetings triggered when the backlog falls below a threshold (Correct answer)

Correct answer: Replenishment meetings triggered when the backlog falls below a threshold

Scrumban uses Kanban's demand-driven replenishment: planning sessions are triggered when the ready backlog drops below a defined threshold, not on a fixed calendar schedule.

Question 57: During a retrospective, two team members have a heated disagreement about coding standards. What should the facilitator do first?

Acknowledge both perspectives and redirect the conversation toward finding a shared solution (Correct answer)
Escalate the conflict to the product owner
Ask the team to vote on who is correct
End the retrospective immediately

Correct answer: Acknowledge both perspectives and redirect the conversation toward finding a shared solution

Acknowledging both viewpoints de-escalates tension and refocuses the team on collaborative problem-solving rather than personal positions.

Question 58: A product owner wants to change the sprint goal two days into a two-week sprint. What should the Scrum Master advise?

Extend the sprint duration to accommodate the new goal
Add the change to the current sprint backlog without discussion
Accept all changes immediately to demonstrate agility
Cancel the sprint if the goal is fundamentally invalidated, otherwise protect the sprint (Correct answer)

Correct answer: Cancel the sprint if the goal is fundamentally invalidated, otherwise protect the sprint

Sprint goals should be stable; the Scrum Master protects the team from scope changes mid-sprint, though cancellation is valid when the goal itself becomes obsolete.

Question 59: In Agile, what is a 'test pyramid' used to represent?

The stages of test planning in a sprint
The hierarchy of test managers in an organization
The priority order in which defects should be fixed
The recommended distribution of test types: many unit tests, fewer integration tests, fewest UI/end-to-end tests (Correct answer)

Correct answer: The recommended distribution of test types: many unit tests, fewer integration tests, fewest UI/end-to-end tests

The test pyramid model recommends having a large base of fast unit tests, a middle layer of integration tests, and only a small number of slow end-to-end tests at the top.

Question 60: Which of the following best describes the 'Arrange-Act-Assert' pattern in TDD?

A deployment strategy for test environments
A pattern where you set up preconditions, execute the action, and verify the outcome (Correct answer)
A method for prioritizing which tests to write first
A project management framework for agile teams

Correct answer: A pattern where you set up preconditions, execute the action, and verify the outcome

Arrange-Act-Assert (AAA) structures each test by setting up the test data, performing the action under test, and then verifying the expected result.

Question 61: In Agile, what does 'failing fast' mean in practice?

Releasing products before they are fully tested
Accepting project failure as an inevitable outcome
Identifying and surfacing problems early through short feedback cycles (Correct answer)
Skipping code reviews to increase development speed

Correct answer: Identifying and surfacing problems early through short feedback cycles

'Failing fast' means designing short feedback loops so that bad assumptions, defects, or wrong directions are discovered quickly and cheaply, before significant investment is made.

Question 62: Which code quality metric measures the percentage of code executed during automated tests?

Cohesion
Code coverage (Correct answer)
Coupling
Cyclomatic complexity

Correct answer: Code coverage

Code coverage measures the proportion of source code that is exercised by the test suite, typically expressed as a percentage.

Question 63: Which value from the Agile Manifesto prioritizes adaptability over rigid planning?

Responding to change over following a plan (Correct answer)
Customer collaboration over contract negotiation
Working software over comprehensive documentation
Individuals and interactions over processes and tools

Correct answer: Responding to change over following a plan

Responding to change over following a plan directly addresses the need for adaptability in Agile development.

Question 64: During a Sprint Planning meeting, the Product Owner presents the highest priority items from the Product Backlog. What is the primary responsibility of the developers on the team at this stage?

To select the amount of work they believe they can complete and create a plan to deliver it. (Correct answer)
To create the high-level product roadmap for the next three to six months.
To re-prioritize the Product Backlog based on technical feasibility.
To accept the work from the previous sprint and demonstrate it to stakeholders.

Correct answer: To select the amount of work they believe they can complete and create a plan to deliver it.

In Sprint Planning, after the Product Owner explains the sprint goal and candidate backlog items, the developers are responsible for forecasting how many of those items they can turn into a completed increment. [24, 28] They select the work and create their own plan, the Sprint Backlog, for how they will accomplish it. [28] Demonstrating work occurs at the Sprint Review, creating a roadmap is a longer-term activity, and prioritizing the Product Backlog is the Product Owner's responsibility.

Question 65: What does a 'red' phase in TDD indicate?

Refactoring broke an existing test
The code has a runtime error
A newly written test is failing because the feature doesn't exist yet (Correct answer)
The build pipeline has failed

Correct answer: A newly written test is failing because the feature doesn't exist yet

In TDD, 'red' means the test was just written and fails because the production code implementing that behavior has not yet been created.

Question 66: What is the concept of 'yesterday's weather' in agile planning?

A technique for estimating technical debt
A risk assessment method based on historical defect rates
A retrospective technique for reviewing past sprint failures
Using the team's most recent sprint velocity as the best predictor for the next sprint (Correct answer)

Correct answer: Using the team's most recent sprint velocity as the best predictor for the next sprint

Yesterday's weather assumes the team's recent past performance is the most reliable indicator of near-future capacity.

Question 67: Which metric best indicates the health of a CI pipeline over time?

Total lines of code added
Number of pull requests merged
Number of commits per day
Mean time to restore a broken build (Correct answer)

Correct answer: Mean time to restore a broken build

Mean time to restore (MTTR) reflects how quickly the team responds to and resolves build failures.

Question 68: Which scenario best demonstrates the Agile principle of face-to-face conversation as the most efficient method of conveying information?

Sending a detailed email thread about a complex architectural decision
Creating a comprehensive Confluence page documenting all API contracts
Recording a video walkthrough of the codebase for future reference
Scheduling a 15-minute whiteboard session to resolve a design disagreement (Correct answer)

Correct answer: Scheduling a 15-minute whiteboard session to resolve a design disagreement

A brief whiteboard session enables real-time dialogue, immediate clarification, and rapid consensus on complex technical decisions.

Question 69: Lead time in agile development is defined as:

The time from item creation in the backlog to its delivery (Correct answer)
The average effort in hours per story point
The number of days before a release freeze
The time a developer spends in code review

Correct answer: The time from item creation in the backlog to its delivery

Lead time captures the full customer perspective: from when a request is made (item created) to when it is fulfilled (delivered).

Question 70: A team is practicing TDD and finds that a new requirement makes 20 existing tests fail. The correct response is to:

Understand why they fail, update tests to reflect the new requirement, then fix production code (Correct answer)
Hard-code exceptions in production code to re-pass the old tests
Disable TDD for this requirement and revert to coding first
Delete the failing tests immediately

Correct answer: Understand why they fail, update tests to reflect the new requirement, then fix production code

Failing tests signal a behavioral change; you should deliberately update tests to match the new intended behavior first.

Question 71: In the context of Agile development, what does 'technical debt' most accurately describe?

The total cost of software licenses used by the development team
The amount of time spent on writing documentation
The budget allocated for infrastructure upgrades
The implied cost of future rework caused by choosing an expedient solution over a better approach (Correct answer)

Correct answer: The implied cost of future rework caused by choosing an expedient solution over a better approach

Technical debt represents the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution.

Question 72: What is the purpose of a spike in Agile development?

To conduct time-boxed research or experimentation to reduce uncertainty (Correct answer)
To skip testing for experimental features
To assign extra work to senior developers
To increase the team's velocity artificially

Correct answer: To conduct time-boxed research or experimentation to reduce uncertainty

A spike is a time-boxed investigation used to gain knowledge and reduce uncertainty before committing to implementation.

Question 73: What does the 'Boy Scout Rule' recommend regarding code quality?

Only refactor code during dedicated refactoring sprints
Always leave the code cleaner than you found it (Correct answer)
Write comprehensive documentation before making any changes
Never modify code that is already working

Correct answer: Always leave the code cleaner than you found it

The Boy Scout Rule encourages developers to make small improvements to code quality whenever they work in an area, gradually improving the overall codebase.

Question 74: Which metric best indicates healthy collaboration within an agile development team?

Total lines of code produced per sprint
Number of individual commits per developer
Cycle time from development to deployment decreasing over successive sprints (Correct answer)
Number of meetings held per week

Correct answer: Cycle time from development to deployment decreasing over successive sprints

Decreasing cycle time reflects improved handoffs, communication, and collective problem-solving, which are direct outcomes of effective team collaboration.

Question 75: What is the primary purpose of practicing 'collective code ownership' within an Agile development team?

To increase the team's adaptability and reduce knowledge silos by ensuring anyone can work on any part of the codebase. (Correct answer)
To ensure that the most senior developer reviews and approves all code changes.
To enforce a single, mandated coding standard across the entire organization.
To eliminate individual accountability for bugs and defects.

Correct answer: To increase the team's adaptability and reduce knowledge silos by ensuring anyone can work on any part of the codebase.

Collective code ownership empowers every team member to contribute to any part of the codebase as needed. This shared responsibility prevents knowledge silos, reduces dependencies on specific individuals (improving the 'bus factor'), and increases the team's overall flexibility and speed.

Question 76: Which practice helps prevent TDD tests from becoming tightly coupled to implementation details?

Mocking every dependency in every test case
Writing tests that verify return values and observable behavior rather than internal method calls (Correct answer)
Using code coverage tools to ensure every line is tested
Writing tests after the implementation is complete

Correct answer: Writing tests that verify return values and observable behavior rather than internal method calls

Testing observable behavior and outputs rather than internal implementation details keeps tests resilient to refactoring and focused on what actually matters.

Question 77: What is the role of the Product Owner in an Agile team?

Handle all coding tasks
Manage team schedules
Prioritize the backlog and define product vision (Correct answer)
Write technical documentation

Correct answer: Prioritize the backlog and define product vision

The Product Owner is responsible for defining the product vision, prioritizing the backlog, and ensuring the team delivers value to the business.

Question 78: A team is using the Red-Green-Refactor technique. They have just written the minimum amount of code required to make a failing test pass. What is the immediate next step?

Deploy the working code to a staging environment for QA testing.
Write the next failing test for another piece of functionality.
Look for opportunities to improve the code's design and eliminate duplication. (Correct answer)
Merge the code into the main branch to get feedback.

Correct answer: Look for opportunities to improve the code's design and eliminate duplication.

The Red-Green-Refactor cycle, which is fundamental to Test-Driven Development (TDD), has three distinct steps. After writing code to make the test pass (the 'Green' step), the next immediate step is 'Refactor'. This is the phase where the developer improves the internal structure of the code they just wrote, such as removing duplication or improving clarity, while ensuring all tests remain green.

Question 79: In XP, what does the 'sustainable pace' practice mean for a development team?

Teams should slow down during releases to avoid defects
Teams should always work at maximum speed to deliver as much as possible
Teams should work at a pace they can maintain indefinitely without burning out (Correct answer)
Teams should work overtime only during the last week of each iteration

Correct answer: Teams should work at a pace they can maintain indefinitely without burning out

Sustainable pace (formerly 'no overtime') holds that teams should work at a pace that can be maintained long-term, preserving quality and team health.

Question 80: From a collaboration and team dynamics perspective, which of the following is a key benefit of pair programming?

It guarantees that the final code will have zero defects.
It doubles the number of lines of code written per hour.
It facilitates real-time knowledge sharing and creates a shared understanding of the solution. (Correct answer)
It allows senior developers to delegate all difficult tasks to junior developers.

Correct answer: It facilitates real-time knowledge sharing and creates a shared understanding of the solution.

While pair programming can improve code quality, its primary collaborative benefit is the continuous knowledge transfer between the pair. This builds shared context, spreads expertise throughout the team, and often leads to better-designed solutions through constant discussion and review.

Question 81: What does the Agile mindset say about motivated individuals on a team?

Teams should be managed closely to stay on schedule regardless of motivation
Motivation is the responsibility of HR, not the Agile framework
Individual motivation matters less than adherence to team processes
Motivated individuals should be given the environment and support they need and trusted to get the job done (Correct answer)

Correct answer: Motivated individuals should be given the environment and support they need and trusted to get the job done

Agile Principle 5 directs teams to be built around motivated individuals, giving them the environment and support needed while trusting them to deliver.

Question 82: The Agile Manifesto was created in 2001 by a group of software practitioners who called themselves what?

Software Craftsmen
Agile Alliance
Organizational Anarchists
No specific group name was adopted at the signing (Correct answer)

Correct answer: No specific group name was adopted at the signing

The 17 signatories did not adopt a formal group name at the meeting; the Agile Alliance was formed afterward as a separate organization.

Question 83: What is the primary purpose of establishing team coding standards in collaborative agile development?

To reduce cognitive load when reading code written by different team members (Correct answer)
To make automated testing easier to implement
To speed up the onboarding of new static analysis tools
To ensure the tech lead's preferred style is followed

Correct answer: To reduce cognitive load when reading code written by different team members

Consistent coding standards reduce the cognitive overhead of switching between code written by different authors, enabling smoother collaboration and faster reviews.

Question 84: Which type of team structure is MOST aligned with agile principles for product development?

Matrix teams where specialists report to functional managers
Functional teams grouped by technology layer (frontend, backend, QA)
Cross-functional teams that can deliver complete features end-to-end (Correct answer)
Centers of excellence that share specialized resources across projects

Correct answer: Cross-functional teams that can deliver complete features end-to-end

Cross-functional teams minimize handoffs and dependencies, enabling faster end-to-end delivery aligned with agile flow.

Question 85: What is the primary risk of having a CI pipeline with a test suite that takes over 60 minutes to complete?

Build servers will use less memory over time
Code quality metrics will improve without additional effort
Developers avoid integrating frequently, defeating the purpose of CI (Correct answer)
The application will automatically become more secure

Correct answer: Developers avoid integrating frequently, defeating the purpose of CI

Slow test suites discourage frequent commits and delay feedback, which undermines the core benefit of Continuous Integration.

Question 86: What is the Agile approach to handling changing requirements mid-sprint?

Evaluate impact with the team and negotiate scope with the Product Owner (Correct answer)
Reject all changes until the next sprint planning
Extend the sprint deadline to accommodate changes
Accept every change immediately without discussion

Correct answer: Evaluate impact with the team and negotiate scope with the Product Owner

Agile teams evaluate the impact of changes and work with the Product Owner to adjust scope while protecting the sprint goal.

Question 87: What is a key difference between Scrum and Disciplined Agile Delivery (DAD)?

DAD is a hybrid toolkit that lets teams choose from multiple Agile approaches based on context (Correct answer)
Scrum provides more prescriptive lifecycle guidance than DAD
DAD eliminates the need for any iterative development cycles
DAD mandates pair programming for all development work

Correct answer: DAD is a hybrid toolkit that lets teams choose from multiple Agile approaches based on context

DAD is a process-decision toolkit that provides guidance on choosing strategies from Scrum, Kanban, XP, and other methods based on the team's specific situation.

Question 88: What is the most significant risk when an Agile team avoids constructive conflict?

The team converges on safe but suboptimal technical decisions (Correct answer)
Meetings become shorter and more efficient
Stakeholder satisfaction improves because of consistent delivery
Team velocity increases due to fewer disagreements

Correct answer: The team converges on safe but suboptimal technical decisions

Avoiding constructive conflict leads to groupthink where teams settle for mediocre solutions instead of challenging each other toward better outcomes.

Question 89: Which communication channel is generally MOST effective for complex problem-solving in agile teams?

Comprehensive written documentation
Ticketing system comments
Email threads with detailed attachments
Face-to-face or video conversation (Correct answer)

Correct answer: Face-to-face or video conversation

Agile Manifesto principles favor face-to-face conversation as the most efficient and effective communication method.

Question 90: In the context of an Agile mindset, what does the principle 'Simplicity—the art of maximizing the amount of work not done—is essential' mean for a developer?

Developers should always choose the easiest and quickest coding solution, even if it is of low quality.
The project should have as few features as possible to be completed quickly.
Developers should avoid complex tasks and delegate them to others.
The team should focus on delivering the simplest solution that meets the immediate requirements, avoiding over-engineering and building features that are not currently needed. (Correct answer)

Correct answer: The team should focus on delivering the simplest solution that meets the immediate requirements, avoiding over-engineering and building features that are not currently needed.

This principle is about focusing on the essential work required to deliver value now, rather than building complex, speculative features that might not be needed (a concept also known as YAGNI - 'You Ain't Gonna Need It'). It encourages developers to find the simplest, most direct path to solve a problem and meet the acceptance criteria, which enhances agility and reduces waste.

Question 91: What does 'Continuous Testing' add to a standard TDD workflow?

Tests are re-run automatically on every file save, giving near-instant feedback (Correct answer)
It enables testing without a CI server
It adds performance benchmarks to every test run
It replaces the manual Red-Green-Refactor cycle with AI

Correct answer: Tests are re-run automatically on every file save, giving near-instant feedback

Continuous testing tools watch the file system and re-execute relevant tests on save, tightening the feedback loop further.

Question 92: To accelerate feedback loops and simplify their branching strategy, an Agile team adopts a practice where developers commit their work directly into the shared 'main' branch multiple times per day. To prevent incomplete features from impacting users, they use feature flags. This practice is known as:

Feature-Driven Development (FDD)
Polyrepo Development
Trunk-Based Development (Correct answer)
GitFlow

Correct answer: Trunk-Based Development

Trunk-Based Development is a source-control model where developers collaborate on code in a single branch called the 'trunk' (or 'main'). They avoid long-lived feature branches and integrate their work frequently, which is a key enabler for CI/CD. GitFlow, in contrast, uses multiple long-lived branches and is more complex.

Question 93: A development team has completed four sprints with the following story point totals: 25, 28, 22, and 25. What is the team's calculated velocity, and what is its primary purpose in Agile planning?

25 points per sprint, used to forecast how much work the team can likely complete in future sprints. (Correct answer)
28 points per sprint, used as a performance target for the next sprint.
100 points, used to measure the total value delivered to the customer.
25 points per sprint, used to compare the team's performance against other teams.

Correct answer: 25 points per sprint, used to forecast how much work the team can likely complete in future sprints.

Velocity is the average amount of work a team completes in a sprint, measured in story points or other units. [1, 4] The average of (25 + 28 + 22 + 25) / 4 is 25. Its primary purpose is as a planning and forecasting tool to help the team predict how many backlog items they can realistically take on in upcoming sprints. [1, 2, 3] It is not meant for comparing teams or as a strict performance target to be exceeded. [2]

Question 94: What is 'shift-left testing' in Agile development?

Running regression tests only at sprint end
Shifting QA work to a separate team
Moving testing activities earlier in the development lifecycle (Correct answer)
Assigning testing responsibilities to left-handed team members

Correct answer: Moving testing activities earlier in the development lifecycle

Shift-left means catching defects as early as possible—during design and coding—rather than in late-stage QA phases.

Question 95: In a cross-functional Agile team, the QA engineer and developers frequently clash over the definition of done. What is the best resolution?

Let the Product Owner define the acceptance criteria unilaterally
Escalate the disagreement to management for a binding decision
Have the team collaboratively create and agree on a shared definition of done (Correct answer)
Separate QA into their own sprint cycle to reduce friction

Correct answer: Have the team collaboratively create and agree on a shared definition of done

A collaboratively defined definition of done ensures shared ownership, mutual understanding, and consistent quality expectations across all roles.

Question 96: What is the key difference between Continuous Delivery and Continuous Deployment?

They are identical practices with different names
Continuous Deployment requires manual approval; Continuous Delivery is fully automated
Continuous Delivery applies only to mobile apps
Continuous Delivery requires manual approval before production; Continuous Deployment releases automatically (Correct answer)

Correct answer: Continuous Delivery requires manual approval before production; Continuous Deployment releases automatically

Continuous Delivery ensures code is always release-ready but requires a human decision to deploy; Continuous Deployment removes that gate.

Question 97: Which practice ensures that every code commit to the main branch automatically triggers a full build and test suite?

Feature Branching
Blue-Green Deployment
Continuous Deployment
Continuous Integration (Correct answer)

Correct answer: Continuous Integration

Continuous Integration requires that each commit is automatically built and tested to detect integration errors early.

Question 98: When a Scrum team realizes mid-sprint that a user story is much larger than estimated, what is the recommended Agile response?

Ask the Product Owner to reduce the acceptance criteria permanently
Extend the sprint deadline to finish the story
Remove the story and close it as won't do
Split the story and carry over the remaining work to the next sprint (Correct answer)

Correct answer: Split the story and carry over the remaining work to the next sprint

Splitting the story and carrying unfinished work to the next sprint preserves sprint timeboxing while ensuring valuable scope is not permanently dropped.

Question 99: What is the 'Strangler Fig' pattern used for in the context of refactoring?

Removing dead code incrementally
Strangling infinite loops in legacy code
Gradually replacing a legacy system by routing new functionality through a new system (Correct answer)
Wrapping external APIs with adapters

Correct answer: Gradually replacing a legacy system by routing new functionality through a new system

The Strangler Fig pattern incrementally migrates a legacy system by routing traffic to new code while keeping the old system alive until it can be retired.

Question 100: In Agile, 'velocity' is best described as:

A metric that compares team output to industry benchmarks
The number of bugs fixed per Sprint
The amount of work a team completes in a Sprint, used for forecasting (Correct answer)
The speed at which a developer writes code per hour

Correct answer: The amount of work a team completes in a Sprint, used for forecasting

Velocity measures work completed (in story points or similar units) per Sprint and is used to forecast future capacity.

CAD (Certified Agile Developer) Exam

The CAD (Certified Agile Developer) Exam exam validates essential knowledge and skills required for certification or licensure in this field.

100

Questions

120 min

Time Limit

70%

To Pass

Checking for saved progress...

Exam Rules

You can skip questions and return to them later
Flag questions for review before submitting
No feedback shown until you submit the entire exam
Unanswered questions count as wrong — answer everything
10 pretest questions are mixed in and don't affect your score
Timer auto-submits when time runs out
Your progress is auto-saved every 30 seconds