Question 84 of 509

Quick Answer

The answer is including security stories in the product backlog, as this control ensures security is integrated directly into each sprint rather than treated as a separate phase. By placing security tasks as explicit backlog items, the team must estimate, prioritize, and complete them within the same iteration as functional work, operationalizing the "shift left" principle where controls are applied at the earliest possible point in development. On the Certified Information Systems Auditor CISA exam, this question tests your understanding of how agile governance differs from traditional waterfall controls—a common trap is choosing a separate security review gate or a post-release audit, which violates agile’s iterative nature. Remember that in agile, if security isn’t in the backlog, it simply won’t be done. Memory tip: think "Backlog or Bust"—if a security requirement isn’t a story, it’s not a priority.

CISA Practice Question: Information Systems Acquisition, Development and Implementation

This CISA practice question tests your understanding of information systems acquisition, development and implementation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

An organization is adopting agile development methodology. Which control is MOST critical to ensure security is integrated?

Question 1hardmultiple choice
Full question →

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

Including security stories in the product backlog

In agile development, security must be continuously integrated into each iteration. Including security stories in the product backlog ensures that security tasks are prioritized, estimated, and addressed during each sprint, making security an inherent part of the development lifecycle rather than an afterthought. This aligns with the principle of 'shifting left' on security, where controls are applied as early as possible.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Penetration testing before release

    Why it's wrong here

    Penetration testing is a point-in-time check, not continuous.

  • Including security stories in the product backlog

    Why this is correct

    Security stories ensure security is addressed in each iteration.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Code reviews after each sprint

    Why it's wrong here

    Code reviews are good but not the most critical for integrating security.

  • Security requirements defined at project initiation

    Why it's wrong here

    Security requirements should be iteratively refined in agile.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often choose 'Security requirements defined at project initiation' (Option D) because it sounds like early planning, but in agile, requirements must be continuously refined and added to the backlog, not locked in at the start.

Detailed technical explanation

How to think about this question

In agile frameworks like Scrum, the product backlog is a living artifact where all work—including security tasks—is captured as user stories. Security stories often follow the 'AS A... I WANT... SO THAT...' format and include acceptance criteria for specific controls (e.g., input validation, encryption at rest). This approach enables the team to estimate effort, assign story points, and track security work in the same velocity metrics as functional features, ensuring security is not deprioritized. Real-world scenarios include using tools like OWASP ASVS to derive security stories and integrating them into backlog grooming sessions.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the CISA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related CISA practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free CISA practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this CISA question test?

Information Systems Acquisition, Development and Implementation — This question tests Information Systems Acquisition, Development and Implementation — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Including security stories in the product backlog — In agile development, security must be continuously integrated into each iteration. Including security stories in the product backlog ensures that security tasks are prioritized, estimated, and addressed during each sprint, making security an inherent part of the development lifecycle rather than an afterthought. This aligns with the principle of 'shifting left' on security, where controls are applied as early as possible.

What should I do if I get this CISA question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This CISA practice question is part of Courseiva's free ISACA 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 CISA exam.