CPA Isc Quiz: User Acceptance Testing Go Live Readiness

What this quiz covers

This quiz focuses on User Acceptance Testing Go Live Readiness, giving you a quick way to practice the rules, question types, and explanations that matter most for CPA Isc.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

Question 1

1. Proceed with go-live and issue manual adjustments only for affected employees, since the overall parallel run totals matched.
2. Remediate the union-specific overtime calculation, re-run targeted parallel payroll for affected scenarios, and obtain sign-off from payroll and the impacted department before go-live. (correct answer)
3. Reclassify the defect as low severity because it affects a single department and can be corrected after go-live.
4. Close UAT and shift focus to load testing, since payroll accuracy is primarily a performance concern at scale.

Explanation: This question evaluates addressing payroll accuracy defects in waterfall SDLCs, focusing on targeted re-testing. Key facts include overall parallel matches but overtime errors for specific contracts, with sponsor pushing proceed. Option B aligns with best practices by remediating and re-running parallels for assurance. Option A is incorrect as manual adjustments are error-prone; option C is wrong because severity is not low; option D is misguided as accuracy is not performance. For payroll, mandate accuracy across scenarios. Implement parallel runs as UAT gates.

Question 2

1. A financial and customer dispute risk, because missing confirmations can lead to chargebacks and operational rework, impacting revenue and customer trust. (correct answer)
2. A hardware risk, because confirmations depend on printer drivers at customer service desks.
3. A minor content risk, because confirmations are informational and do not affect actual cancellations in the system.
4. A project staffing risk, because customer service involvement increases training requirements.

Explanation: This question assesses risk identification in UAT for Agile SDLCs, emphasizing financial and customer impacts. Key facts include missing confirmations for multi-component cancellations, potentially increasing disputes. Option A aligns with best practices by recognizing revenue and trust risks. Option B is incorrect as hardware is unrelated; option C is wrong because confirmations affect disputes, not just info; option D is misguided as staffing is secondary. In confirmation defects, prioritize to avoid rework. Assess customer impact in risk frameworks.

Question 3

1. Proceed with go-live and use daily exception reports as a compensating control, since UAT sign-off has already been obtained.
2. Reclassify the defect as low severity because it affects only a small subset of users and can be corrected in a later release.
3. Implement a temporary manual policy requiring finance to review all delegated approvals, and defer system remediation until after stabilization.
4. Treat the issue as a high-risk control gap, remediate approval-limit enforcement, and perform targeted UAT regression on delegated approval scenarios before cutover. (correct answer)

Explanation: This question evaluates addressing control gaps identified late in UAT within a waterfall SDLC, focusing on risk-based decisions before cutover. Key facts include a defect in delegated approval limits not being enforced, discovered post-sign-off, with the sponsor suggesting monitoring instead of fixes. Option D aligns with IT project management best practices by treating it as a high-risk gap and requiring remediation and regression testing to maintain internal controls. Option A is incorrect as exception reports are insufficient compensating controls for systemic issues, per governance standards; option B is wrong because reclassifying severity downplays the control risk, violating defect prioritization; option C is inadequate as manual policies introduce human error, contrary to automation principles in ERP. For similar issues, use a risk register to evaluate defects and mandate re-testing. Ensure stage gates include control validation to prevent post-go-live surprises.

Question 4

1. Only successful execution of UAT scripts, because cutover rehearsal is an operations activity and can be performed after go-live.
2. Completion of cutover rehearsal and operational readiness, because go-live risk includes data migration, integrations, and rollback capability beyond UAT script results. (correct answer)
3. Business owner sign-off alone, because sign-off implies acceptance of all readiness risks.
4. The total number of defects found in UAT, because fewer defects indicates lower cutover risk.

Explanation: This question examines comprehensive readiness criteria in waterfall SDLCs, beyond UAT to include operational aspects. Key facts include meeting most criteria but skipping cutover rehearsal due to pressure. Option B aligns with best practices by prioritizing rehearsals for migration and rollback, reducing go-live risks. Option A is incorrect as cutover is essential for operations, per deployment planning; option C is wrong because sign-off alone does not cover all risks; option D is inadequate as defect counts ignore operational readiness. For deployments, integrate rehearsals into exit criteria. Develop contingency plans based on rehearsal outcomes.

Question 5

1. User experience and operational efficiency for key workflows, ensuring the new process does not materially degrade service levels at go-live. (correct answer)
2. Whether the deployment pipeline can complete in under 10 minutes, since rapid releases offset any usability concerns.
3. Whether system documentation is fully updated, since UAT results already confirm the system is acceptable.
4. Whether the number of UAT defects is lower than the prior project, regardless of impact on user productivity.

Explanation: This question examines go-live readiness in a DevOps SDLC, prioritizing user experience and efficiency over schedule or non-functional metrics. Key facts include functional passes but a 20% increase in task time due to confusing interfaces, with pressure to meet contract dates. Option A aligns with best practices by focusing on operational efficiency to avoid service degradation, ensuring sustainable adoption. Option B is incorrect as deployment speed does not offset usability issues, per user-centric design principles; option C is wrong because documentation alone does not address efficiency, violating holistic readiness; option D is inadequate as defect counts ignore impact, contrary to impact-based evaluation. For similar cases, incorporate usability metrics into readiness criteria. Use feedback loops to iterate on user experience pre-deployment.

Question 6

1. Proceed with go-live because the issue occurs after end-of-day and does not affect real-time customer transactions.
2. Proceed with go-live if the pilot branch manager signs off, since pilot sign-off is sufficient for enterprise deployment.
3. Defer go-live until the reversal and end-of-day reconciliation logic is corrected and re-tested, because it affects cash controls and financial accuracy. (correct answer)
4. Move the issue to performance testing because reconciliation reports are batch processes and not part of UAT scope.

Explanation: This question tests UAT defect resolution in phased SDLCs, deciding on deferral for financial controls. Key facts include mismatched balancing reports for reversals post-end-of-day, with manual adjustment proposed. Option C aligns with best practices by deferring for fixes to ensure accuracy and controls. Option A is incorrect as timing does not negate impact; option B is wrong because pilot sign-off is insufficient for enterprise; option D is misguided as reconciliation is functional, not performance. For control defects, require full resolution pre-rollout. Validate end-of-day processes in pilot UAT.

Question 7

1. Proceed with go-live because role-based access is an IT security control validated during penetration testing, not UAT.
2. Conduct targeted UAT using unique role-based test accounts to validate access and segregation of duties, and require remediation of any access issues before go-live approval. (correct answer)
3. Rely on the vendor's standard roles and proceed, since shared accounts demonstrate that users can complete tasks efficiently.
4. Defer the access review until the first internal audit after go-live to avoid delaying the schedule.

Explanation: This question evaluates ensuring role-based validation in UAT for waterfall SDLCs, addressing incomplete testing. Key facts include script execution but shared accounts skipping access checks, with go-live soon. Option B aligns with best practices by requiring targeted UAT for access and duties segregation. Option A is incorrect as access is a UAT concern for security; option C is wrong because vendor roles may not fit needs; option D is inadequate as deferring to audit delays controls. For access issues, include role-specific scenarios in UAT. Enforce segregation of duties in readiness reviews.

Question 8

1. Proceed with go-live because the defect rate is low, and correct customer tax amounts through refunds after the next release.
2. Defer go-live or exclude the affected jurisdiction until tax logic is corrected and re-tested, because incorrect tax calculation can create compliance and financial exposure. (correct answer)
3. Close UAT and rely on vendor assurance that tax engines are always compliant by design.
4. Proceed with go-live and classify the issue as a cosmetic defect because the tax is displayed only on the receipt.

Explanation: This question tests handling compliance defects in UAT for Agile SDLCs, evaluating deferral for financial exposure. Key facts include inconsistent tax calculations with discounts in one jurisdiction, affecting few transactions, with a launch suggestion. Option B aligns with best practices by deferring to avoid compliance risks and ensure accuracy. Option A is incorrect as refunds introduce rework, per efficiency principles; option C is wrong because vendor assurances do not guarantee compliance; option D is misguided as tax issues are not cosmetic. For tax-related defects, prioritize legal compliance in readiness. Conduct jurisdiction-specific testing in UAT.

Question 9

1. A compliance and control failure risk, because the workflow can bypass a required documentation control and may lead to noncompliant loan processing. (correct answer)
2. A user adoption risk, because loan officers may prefer the legacy system if a draft feature exists in the new platform.
3. A performance risk, because saving drafts could increase database storage and slow down reporting.
4. A vendor lock-in risk, because the platform uses proprietary document storage formats.

Explanation: This question assesses risk identification in UAT for deployment readiness in a Scrum SDLC, specifically compliance risks from workflow bypasses in regulated environments. The key facts involve a defect allowing loan submission without required documents via a draft save, classified as medium despite occurring in a specific sequence, with all critical paths passing. Option A aligns with best practices by recognizing this as a compliance failure that could lead to noncompliant processing, ensuring controls are enforced pre-go-live. Option B is incorrect as it misclassifies the issue as user adoption rather than a control gap, ignoring regulatory compliance principles; option C is wrong because performance is not the primary concern here, per risk assessment frameworks; option D is irrelevant as vendor lock-in does not relate to the defect, violating focused defect analysis. In analogous cases, conduct risk assessments during UAT to prioritize compliance over convenience. Implement change gates that require remediation of control failures before release.

Question 10

1. Whether all test cases were executed, regardless of severity, to demonstrate complete UAT coverage.
2. Whether the defect backlog is below a numeric threshold set at project kickoff, even if high-severity issues remain open.
3. Whether critical business workflows and patient-facing communications are accurate, with high-severity defects remediated and re-tested, and sign-off obtained from process owners. (correct answer)
4. Whether performance testing results meet targets, since functional defects can be corrected after go-live without impacting operations.

Explanation: This question examines go-live readiness criteria in a hybrid SDLC, emphasizing the need to prioritize critical workflows and defect remediation over timelines or non-essential metrics. Key facts include a defect in appointment reminders displaying incorrect addresses for patients who changed locations, with most defects minor but this one affecting patient-facing communications in a healthcare context under regulatory pressures. Option C aligns with IT project management best practices by ensuring high-severity defects in core processes are fixed and signed off, promoting patient safety and compliance. Option A is incorrect as complete test coverage without severity consideration ignores risk-based testing principles; option B is wrong because a numeric defect threshold overlooks unresolved high-severity issues, per quality assurance standards; option D is misguided as it prioritizes performance over functional accuracy, violating the principle that critical defects must be resolved pre-deployment. For similar situations, use a readiness checklist that weights business impact and stakeholder sign-off. Establish clear exit criteria for UAT to guide go-live decisions objectively.

Question 11

1. Stakeholder acceptance across impacted business functions, including validation of tax receipt accuracy and communication preference controls, with documented UAT sign-off. (correct answer)
2. Whether the vendor's implementation checklist is complete, since vendor certification replaces internal UAT participation.
3. Whether the number of UAT participants meets the minimum headcount target, regardless of their functional roles.
4. Whether all minor UI enhancements requested during UAT have been implemented before go-live.

Explanation: This question examines go-live readiness in waterfall SDLCs, emphasizing broad stakeholder involvement in UAT. Key facts include limited UAT participation excluding finance and privacy, despite script execution, for a system with tax and preference features. Option A aligns with best practices by requiring cross-functional acceptance to ensure comprehensive validation. Option B is incorrect as vendor checklists do not substitute internal validation, per accountability principles; option C is wrong because headcount ignores role relevance; option D is inadequate as minor UI changes are secondary to core functions. For comparable projects, mandate diverse stakeholder sign-off in readiness. Use RACI matrices to define UAT participants.

Question 12

1. Proceed with go-live because missing test data is an expected UAT limitation and can be addressed through post–go-live monitoring.
2. Expand UAT to include representative test data and execute end-to-end scenarios for complex enrollment cases before final go-live approval. (correct answer)
3. Close UAT and rely on unit testing evidence, since unit tests provide better coverage than user-driven scenarios.
4. Replace UAT with a penetration test to confirm the system is secure enough for production use.

Explanation: This question tests the importance of comprehensive test data in UAT for Agile SDLCs, ensuring end-to-end validation before go-live. Key facts involve incomplete test data preventing validation of complex enrollment scenarios, despite successful script execution, with consideration for go-live anyway. Option B aligns with best practices by expanding UAT to cover representative data, promoting thorough acceptance and reducing deployment risks. Option A is incorrect as accepting UAT limitations ignores data realism principles in testing; option C is wrong because unit testing does not substitute for user-driven validation, per SDLC phases; option D is misguided as penetration testing addresses security, not functional completeness. In comparable scenarios, define UAT scope to include diverse data sets for realism. Adopt a framework requiring full scenario coverage before readiness approval.

Question 13

1. A reputational risk only, since accessibility issues do not affect the underlying permit workflow logic.
2. A compliance and service delivery risk, because accessibility failures can prevent equal access and may violate applicable accessibility requirements. (correct answer)
3. A data conversion risk, because screen readers may alter form field values during submission.
4. A network capacity risk, because assistive technology increases bandwidth consumption during peak usage.

Explanation: This question assesses risk prioritization in UAT for waterfall SDLCs, focusing on accessibility compliance in public-facing systems. Key facts include screen reader failures for error messages, preventing completions, with go-live tied to a campaign. Option B aligns with best practices by identifying compliance and service risks, ensuring equal access and legal adherence. Option A is incorrect as it downplays accessibility to reputational only, ignoring legal mandates; option C is wrong because data conversion is unrelated, per targeted risk analysis; option D is irrelevant as network capacity does not stem from the defect. In like situations, integrate accessibility testing into UAT mandates. Apply a compliance checklist to flag and remediate barriers before launch.

Question 14

1. Proceed with go-live because offline functionality is a technical feature and can be validated after deployment by IT support.
2. Expand UAT to include offline and sync scenarios with representative users and data, and confirm operational support procedures before retiring the legacy app. (correct answer)
3. Proceed with go-live and require consultants to enter time only when connected to the network until a later enhancement.
4. Close UAT and move directly to code freeze, since additional testing could introduce new defects.

Explanation: This question tests expanding UAT scope in phased SDLCs for critical features like offline support. Key facts include untested offline sync, common for users, with legacy retirement planned. Option B aligns with best practices by including scenarios and support confirmation. Option A is incorrect as offline is user acceptance; option C is wrong because restrictions limit functionality; option D is inadequate as code freeze ignores testing. For mobile features, test real-world use cases. Ensure operational readiness before legacy decommissioning.

Question 15

1. Whether cashier training materials are complete, since policy reminders reduce the likelihood of bypassing prompts.
2. Whether the system enforces legally required controls in high-risk workflows (e.g., age verification), with defects resolved and re-tested before broader rollout. (correct answer)
3. Whether pilot store sales volumes are stable, since control issues can be evaluated after rollout.
4. Whether UAT defect counts are trending downward across sprints, regardless of the nature of remaining defects.

Explanation: This question examines go-live readiness in pilot methodologies, prioritizing legal controls in high-risk workflows. Key facts include bypassable age prompts during quick scans, with policy reminders suggested. Option B aligns with best practices by ensuring enforcement and re-testing for compliance. Option A is incorrect as training is secondary to system controls; option C is wrong because sales stability ignores risks; option D is inadequate as trends ignore specific defects. For regulated workflows, enforce controls in readiness. Integrate compliance testing into pilots.

Question 16

1. Go live as planned and instruct finance to manually reclassify the entries at month-end until the next release.
2. Defer go-live until the defect is fixed and re-tested in UAT, because it impacts financial reporting accuracy and period-end controls. (correct answer)
3. Proceed with go-live if performance and security testing are complete, since UAT is not intended to validate accounting period logic.
4. Proceed with go-live and accept the risk because the issue occurs only once per month and affects a limited set of transactions.

Explanation: This question evaluates handling financial accuracy defects in UAT for Agile SDLCs, deciding on deferral versus workarounds. Key facts include a defect posting refunds to the wrong period in certain time zones, impacting reporting, with a suggestion to proceed. Option B aligns with best practices by deferring go-live for fixes and re-testing to ensure financial integrity. Option A is incorrect as manual reclassification introduces errors, per control reliability principles; option C is wrong because UAT validates such logic, not just performance; option D is inadequate as accepting monthly risks violates accuracy standards. For analogous defects, prioritize financial controls in readiness assessments. Use regression testing to confirm fixes without introducing new issues.

Question 17

1. Proceed with go-live and rely on production monitoring, since intermittent issues are best diagnosed under real user load.
2. Treat the issue as a potential critical defect, expand UAT with targeted test cases and logging in a staging environment, and require resolution or a validated workaround before CAB approval. (correct answer)
3. Move the issue to a future backlog item because UAT cannot reliably reproduce it and the marketing date is fixed.
4. Replace UAT with code review evidence, since authentication issues are primarily developer concerns rather than user acceptance concerns.

Explanation: This question tests addressing intermittent defects in UAT for Agile SDLCs with CAB approval, ensuring resolution before release. Key facts include non-reproducible login failures post-reset, with vendor suggesting production monitoring. Option B aligns with best practices by expanding UAT for diagnosis and requiring fixes, minimizing security risks. Option A is incorrect as production monitoring exposes users unnecessarily, per pre-deployment validation; option C is wrong because deferring ignores impact, violating release gates; option D is misguided as code reviews do not replace user testing. In similar intermittent issues, enhance logging and targeted testing. Establish criteria for reproducibility before CAB approval.

Question 18

1. A privacy and consent management risk, because messaging users who opted out can violate customer preferences and applicable communication rules. (correct answer)
2. A data retention risk, because SMS logs may be stored longer than email logs.
3. A scalability risk, because opt-out logic increases CPU usage during peak outages.
4. A training risk, because customers may not understand how to opt out properly.

Explanation: This question assesses risk identification in UAT for phased SDLCs, focusing on privacy compliance in notifications. Key facts include opt-out failures within 24 hours of events, classified as low impact despite the narrow window. Option A aligns with best practices by recognizing privacy risks and potential violations, ensuring consent enforcement. Option B is incorrect as retention is unrelated to the defect; option C is wrong because scalability does not arise here; option D is misguided as training does not fix systemic issues. In similar privacy defects, prioritize remediation per data protection laws. Integrate consent testing into UAT scripts for compliance.

Question 19

1. Proceed with go-live because warehouse operations are the primary users and finance can reconcile discrepancies after go-live.
2. Proceed with go-live if the vendor confirms the issue is limited to test data and not present in production.
3. Defer go-live until the GL mapping defect is corrected and finance completes UAT validation and provides formal sign-off. (correct answer)
4. Close UAT and move directly to disaster recovery testing, since accounting mapping is better validated during recovery exercises.

Explanation: This question tests UAT sign-off requirements in Agile SDLCs with integrations, ensuring all stakeholders validate before go-live. Key facts include passing warehouse flows but GL mapping defects, with finance not signing off. Option C aligns with best practices by deferring for fixes and sign-off to maintain financial accuracy. Option A is incorrect as reconciliations are inefficient, per integration testing principles; option B is wrong because vendor assurances do not replace validation; option D is misguided as disaster recovery does not address functional defects. For integrated systems, require end-to-end UAT with stakeholder approval. Use defect impact analysis to guide deferral decisions.

Question 20

1. Proceed with go-live and document the limitation, since attachment size is a usability concern rather than a functional defect.
2. Treat it as a high-priority customer-impact defect, implement a fix or an explicit validation/error message, and re-test the external customer workflow in UAT before release. (correct answer)
3. Move the issue to performance testing because large attachments primarily affect system throughput, not user acceptance.
4. Proceed with go-live and rely on the service desk to manually request attachments via email when failures occur.

Explanation: This question evaluates handling customer-impacting defects in DevOps SDLCs, deciding on fixes versus documentation. Key facts include silent failures for large attachments externally, with a suggestion for help notes. Option B aligns with best practices by prioritizing fixes and re-testing to enhance customer experience. Option A is incorrect as size limits affect functionality, not just usability; option C is wrong because performance testing is separate; option D is inadequate as manual processes increase support load. In customer-facing issues, assess impact on satisfaction pre-release. Implement validation rules to prevent silent failures.