CISA Information Systems Operations and Business Resilience: 754 practice questions
12 of the 754 Information Systems Operations and Business Resilience questions in the Certsqill CISA bank, shown in full below. Each one carries an explanation for every option, not just the correct one — the wrong answers are where the marks go.
Preparing for CISA? Take the free 5-min readiness check →
1. An auditor-verified inventory matched to observed: Which evidence most strongly supports whether technology co
- A vendor brochure describing recommended infrastructure monitoring capabilities for banks.Generic vendor information does not evidence the bank’s implemented controls.
- A monthly uptime dashboard showing all critical servers exceeded target availability.Availability results do not establish complete component inventory or dependency control.
- A signed statement from the infrastructure director confirming inventory accuracy.Management representation is less persuasive than independently corroborated operational evidence.
- An auditor-verified inventory matched to observed components and recorded dependencies. ✓Verification links recorded components, ownership, and dependencies to actual technology.
Verified inventory evidence directly connects technology components with ownership and dependencies.
2. Undocumented sanitization of retired devices: Which control gap is most consequential?
- Failure to record retirement dates for devices with documented sanitization and license removal.Retirement dates are recorded, making this concern unsupported by evidence.
- Undocumented sanitization of retired devices. ✓Patient data could remain recoverable despite otherwise completed retirement activities.
- Incomplete documentation of license removal evidence.License evidence is complete, so this does not represent the stated gap.
- Missing ownership records for devices already retired and removed from service.Ownership records are stated as complete for the retired devices.
Missing sanitization evidence creates the greatest residual exposure for retained patient data.
3. Examine dependency handling: What should the auditor do next to evaluate automated production controls?
- Conclude scheduling controls are effective based on successful sampled runs.Successful runs do not test dependencies, restarts, or duplicate prevention.
- Examine dependency handling, restart controls, and duplicate prevention. ✓These procedures address critical batch risks not covered by completed testing.
- Replace the approved schedule with a manually supervised payroll process.Manual replacement is not justified without establishing a control deficiency.
- Ask management to accept the risk of untested batch failure scenarios.The auditor should obtain evidence rather than direct management risk acceptance.
Next testing should address dependencies, restarts, and duplicate processing risks.
4. Recommend reconciliation and error handling in addition: How should the auditor evaluate this response?
- Accept it because encryption protects transmitted data.Encryption protects confidentiality but does not demonstrate completeness or accuracy.
- Recommend reconciliation and error handling in addition to encryption. ✓Independent reconciliation addresses missing, altered, sequenced, or duplicate records.
- Require disabling the interface until management implements encryption.Encryption already exists, while the unresolved gap concerns reconciliation.
- Conclude delivery messages prove every meter reading reached billing accurately.Delivery messages do not prove record completeness, accuracy, or duplicate prevention.
Encryption does not establish completeness; reconciliation and error handling remain necessary.
5. The population has control deficiencies requiring: How should the auditor interpret these results?
- The population has control deficiencies requiring proportionate oversight. ✓Results indicate insufficient safeguards over inventory, access, versioning, and formula integrity.
- Formal IT inventory is unnecessary because business users maintain these spreadsheets.Business-user tools still require proportionate inventory and control oversight.
- Ownership alone makes the spreadsheets acceptable.Ownership does not address versioning, access, or formula reliability risks.
- The results represent documentation weaknesses without substantive control concerns.Shared editing and unreviewed formulas can impair integrity and processing reliability.
Ownership exists, but testing shows broader shadow-IT governance weaknesses affecting integrity.
6. Design appears suitable: What conclusion is best supported?
- Capacity controls are ineffective by design because thresholds exist.Thresholds and assigned responsibility may constitute an appropriate control design.
- Replace threshold monitoring immediately with load testing.Load testing may supplement monitoring but does not resolve missing review evidence.
- Design appears suitable; operation is unproven. ✓Defined thresholds support design, while missing review evidence prevents confirming operation.
- Availability is effective because testing found no outage.No outage does not demonstrate that capacity monitoring operated effectively.
Thresholds support design, but missing alert reviews prevent confirming operating effectiveness.
7. Require problem analysis and tracked corrective actions: What recommendation is most appropriate?
- Focus only on reducing the documented restoration times.Faster restoration does not address the repeated underlying failure pattern.
- Close the incidents because service was restored within targets.Meeting restoration targets does not eliminate the need for problem management.
- Transfer outage-risk acceptance to the auditor until recurrence stops.Management owns risk acceptance; auditors evaluate and recommend improvements.
- Require problem analysis and tracked corrective actions for recurring outages. ✓Repeated incidents require investigation of underlying causes beyond restoring service.
Recurring outages require problem management, not merely incident restoration and communication.
8. The conclusion is limited to servers: What limitation should the auditor report?
- The auditor should implement network-device patching before concluding.Auditors evaluate and recommend; management owns implementation of patch controls.
- The conclusion is limited to servers; enterprise-wide patch assurance is unsupported. ✓Excluded devices and unassessed compensating controls restrict the assurance conclusion.
- The server sample proves network devices receive equivalent patch governance.Evidence from servers cannot establish controls over excluded network devices.
- Patch controls are ineffective because rollback evidence was retained.Rollback evidence is a control strength, not evidence of ineffectiveness.
Evidence supports sampled servers only; excluded network devices prevent enterprise-wide assurance.
9. Management sets requirements: During the audit, who holds decision rights for defining logging requirements an
- The auditor determines retention after comparing provider logging practices.Auditors independently evaluate controls but do not select management’s requirements.
- The provider and auditor jointly approve requirements and accept residual logging risk.Risk acceptance remains management’s decision, not a shared auditor-provider decision.
- The provider alone decides log retention and review requirements.Operational delegation does not transfer management’s accountability for control requirements.
- Management sets requirements; the provider operates logs under the contract. ✓Management owns requirements and risk; the provider performs contracted operational activities.
Management owns logging requirements; the provider operates them under contractual direction.
10. Prioritize measurable customer-impacting targets: Which priority best reduces significant operational risk fir
- Document exclusions for all internal services first.Exclusions matter, but customer-impacting performance currently presents greater operational risk.
- Prioritize measurable customer-impacting targets. ✓This addresses the clearest material exposure before lower-risk catalog harmonization work.
- Assign owners throughout the merged catalog before measuring performance.Ownership is necessary, but measurable customer-impacting exposure requires earlier attention.
- Standardize every service target immediately.Broad standardization may consume capacity without reducing the highest business exposure.
Prioritize measurable customer-impacting commitments before lower-risk catalog harmonization.
11. Require independent review of privileged database activity: Which recommendation is best?
- Ask the auditor to approve each emergency database change after completion.Auditor approval compromises independence and does not establish management’s operating control.
- Allow unrestricted DBA access because emergencies require speed.Emergency needs do not justify unrestricted, unaudited privileged access.
- Remove all emergency database access from administrators.Eliminating access may impair necessary recovery without addressing controlled emergency use.
- Require independent review of privileged database activity. ✓Independent review compensates for unavailable segregation during emergency privileged access.
Independent review provides a compensating check over emergency privileged activity.
12. Yes; approved BIA results support priorities: Is that conclusion adequately supported?
- No; every process must have identical recovery objectives.Recovery requirements appropriately differ according to business impact and criticality.
- Yes; auditors may define priorities from management’s BIA.The evidence supports management’s conclusion; auditors do not define business priorities.
- Yes; approved BIA results support priorities. ✓Approved BIA evidence directly supports priorities based on impacts, dependencies, and requirements.
- No; only technical recovery testing supports priorities.Business-owned BIA evidence can establish recovery priorities before technical testing.
Approved BIA evidence supports priorities through documented impacts, dependencies, and recovery requirements.
742 more Information Systems Operations and Business Resilience questions
The remaining 742 questions in this domain are part of the full CISA bank — 2900 questions, every option explained. Start with the free five-minute check and see your score per domain.
Test your CISA readiness — freeOther CISA domains
- Protection of Information Assets — 754 questions →
- Information Systems Auditing Process — 522 questions →
- Governance and Management of IT — 522 questions →
- Information Systems Acquisition, Development and Implementation — 348 questions →
- All 2900 CISA questions →
- CISA certification: requirements, cost and exam format →