CISA domain - 12% of the exam

Information Systems Acquisition, Development and Implementation

Information Systems Acquisition, Development and Implementation is 12% of the CISA exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

35
Practice questions
4
Objectives
26
Medium
9
Hard

Where people go wrong

  • Treating delivery or stability as proof of benefits

    The wrong answers equate a project milestone with benefit delivery: approval of the case, confirmation of delivery after go-live, user acceptance evidence, or technical stability. Benefits realisation is the business owner's ongoing accountability to compare forecast benefits with actuals and trigger corrective action. A post-implementation review, held once the system has stabilised, compares realised benefits, costs and control performance against the approved business case, and technical metrics alone leave benefits untested.

    See it in a sample question
  • Confusing change, release and configuration management

    The wrong answers hand one discipline's job to another. Authorisation, justification and risk rating belong to change management. Release management plans, packages and deploys approved changes as a coordinated unit at a controlled time. Configuration management, through the CMDB, records authorised configuration items and their relationships as the baseline, and root-cause analysis belongs to problem management. For segregation of duties, the change manager authorises and a separate release manager supervises the deployment.

    See it in a sample question
  • Offering the wrong test as the evidence

    Each wrong answer names a real test that answers a different assurance question. Unit testing exercises modules in isolation, and user acceptance testing confirms business acceptability; neither shows that interfaces behave correctly across systems, which is the job of integration testing. User acceptance testing also gives no systematic regression coverage of legacy functionality. Runbook walkthroughs and tabletop exercises check process and recovery procedures; load testing in a production-equivalent environment is the test that shows the infrastructure sustaining peak demand.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleInformation Systems Acquisition, Development and Implementationmedium

Which statement BEST describes the role of benefits realisation within the business case lifecycle for a systems acquisition?

  • ABenefits realisation is finalised at business case approval, when forecast benefits are signed off as the basis for funding the project.
  • BBenefits realisation is an ongoing accountability of the business owner to track forecast benefits against actuals and trigger corrective action. Correct
  • CBenefits realisation is a closure activity performed by the project manager immediately after go-live to confirm the system has been delivered.
  • DBenefits realisation is a contractual obligation transferred to the implementation vendor under the master services agreement at contract award.
Recognise that benefits realisation is an ongoing business-owner accountability to track forecast benefits against actuals across the asset life. The business case is a forecast that is only validated when realised benefits are measured against it over the asset life, and assigning that measurement to the accountable business owner is what stops approved cases from becoming forgotten cases once funding is released.

Why A is wrong: Approval merely commits to a forecast and is the start, not the end, of the benefits realisation lifecycle that runs through and beyond go-live.

Why B is correct: Benefits realisation is the ongoing accountability of the business owner to compare forecast benefits in the case against actuals across the asset life and to trigger corrective action when variances appear, closing the loop on the original investment decision.

Why C is wrong: Post-go-live delivery confirmation is project closure, whereas benefits realisation tracks whether forecast benefits actually accrue over the asset life.

Why D is wrong: Vendors deliver scope rather than business outcomes, so benefits accountability cannot be contractually transferred to them without leaving the investing organisation exposed.

Free sampleInformation Systems Acquisition, Development and Implementationmedium

An IS auditor is reviewing the configuration management process supporting a containerised order-management platform. Which statement BEST describes the role of the configuration management database (CMDB) in this environment?

  • AIt schedules approved changes into release windows and coordinates dependencies between simultaneously deploying teams across the platform.
  • BIt holds the authoritative test results from user acceptance testing and proves that exit criteria for go-live have been satisfied.
  • CIt records authorised configuration items and the relationships between them, providing the baseline against which changes are verified. Correct
  • DIt stores customer master data and reference data so business users can validate the accuracy of converted records after cutover.
Recognise the CMDB as the authoritative record of configuration items and their relationships used to support change and release decisions. Configuration management establishes and maintains the integrity of configuration items across the lifecycle. The CMDB is the authoritative record of those items and their relationships, supporting impact assessment for changes, verification after releases, and accurate incident diagnosis. It is not a scheduler, a test repository or a business-data master, and confusing it with those neighbouring artefacts is a frequent CISA misstep.

Why A is wrong: Scheduling approved changes into release windows is a release management activity. Candidates confuse it with configuration management because both touch the deployment process, but the CMDB does not own scheduling.

Why B is wrong: Test evidence and exit-criteria sign-off sit in test management and readiness review artefacts. Candidates pick this because the CMDB is referenced in readiness packs, but it is not the system of record for test outcomes.

Why C is correct: Correct. The CMDB is the authoritative inventory of configuration items and their relationships, giving change, release and incident processes the trusted baseline they need to assess impact and verify outcomes.

Why D is wrong: Master and reference data sit in business data stores, not the CMDB. Candidates confuse them because both are described as authoritative records, but the CMDB tracks technical configuration items rather than business data.

Free sampleInformation Systems Acquisition, Development and Implementationmedium

During a review of implementation testing for a new claims platform, an IS auditor needs to confirm that the system behaves correctly when integrated with the policy administration system and the general ledger. Which test type BEST satisfies this objective?

  • AUnit testing of individual program modules using developer-written test harnesses before code is checked into the build.
  • BIntegration testing of end-to-end transaction flows across the claims platform, policy administration system and general ledger. Correct
  • CRegression testing of the existing policy administration and general ledger baselines after configuration patches are applied.
  • DUser acceptance testing performed by claims handlers against documented business scenarios in a staging environment.
Identify integration testing as the test type that verifies correct behaviour across interfaces between the new system and surrounding production systems. Integration testing exercises the interfaces, data mappings and end-to-end transaction flows between two or more systems to confirm they exchange information correctly. Unit testing operates within a single module, regression testing protects an existing baseline after change, and UAT confirms business acceptability. When the audit question is whether two systems work together correctly, integration testing supplies the relevant evidence.

Why A is wrong: Unit testing verifies individual modules in isolation. Candidates pick it because it is the earliest test layer, but it does not exercise interactions between the claims platform and surrounding systems.

Why B is correct: Correct. Integration testing verifies that interfaces, data mappings and transaction flows behave correctly when multiple systems work together, which is exactly what the auditor needs evidence of here.

Why C is wrong: Regression testing confirms that previously working functionality has not been broken by a change. Candidates confuse it with cross-system testing, but regression is anchored to a prior baseline, not the new interfaces.

Why D is wrong: UAT confirms the solution meets business needs. Candidates pick it because business users sit close to the integrations, but UAT focuses on business acceptability rather than interface correctness across systems.

Other domains in this exam

See also the CISA cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by ISACA. Original, blueprint-aligned practice material only.