- A city government is preparing to go live with a payroll system in the final SDLC phase and is using a controlled waterfall methodology with formal acceptance. UAT included parallel payroll runs for two pay periods; totals matched overall, but testers found that overtime premiums are calculated incorrectly for a specific union contract when employees work split shifts. The project sponsor wants to proceed because only one department uses that contract. How should the IT team address this issue before going live?
Answer: 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.
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.
- A telecommunications company is completing the SDLC for a customer self-service portal using Agile with a formal release readiness checklist. UAT indicates that password reset emails are delivered, but the reset link remains valid for 72 hours, contrary to the security requirement of 30 minutes. The product team argues that longer validity reduces support calls. What potential risk identified during testing requires immediate attention?
Answer: A security risk, because extended reset-link validity increases the window for unauthorized account access and violates stated security requirements.
This question assesses security risk identification in UAT for Agile SDLCs, focusing on requirement adherence. Key facts include reset links valid for 72 hours versus 30 minutes required, with arguments for longer validity. Option A aligns with best practices by recognizing increased unauthorized access risks. Option B is incorrect as performance is not the concern; option C is wrong because training does not mitigate validity; option D is irrelevant as duplicates are unrelated. In security defects, enforce requirements over convenience. Use threat modeling to prioritize fixes.
- A regional hospital is preparing to go live with a medication administration record (MAR) module and is in the final SDLC deployment readiness review under a controlled change management methodology. UAT by nurses passed routine administration workflows, but testers identified that allergy alerts do not display for medications ordered through a specific order set used in the emergency department. The vendor proposes a workaround: nurses should open the full chart view before administration. What potential risk identified during testing requires immediate attention?
Answer: A patient safety risk, because missing allergy alerts can lead to adverse events and should be remediated and re-tested before go-live.
This question assesses risk prioritization in UAT for healthcare systems, focusing on patient safety defects. Key facts include passing workflows but missing allergy alerts in specific order sets, with a workaround proposed. Option A aligns with best practices by identifying safety risks and requiring fixes to prevent adverse events. Option B is incorrect as alerts affect care, not just reporting; option C is wrong because usability downplays clinical impact; option D is irrelevant as latency is not the issue. In safety-critical defects, mandate remediation and re-testing. Use failure mode analysis for healthcare IT risks.
- A bank is completing the SDLC for a mobile app update using Agile delivery with a formal production change advisory board (CAB) approval. UAT was executed by a pilot group and showed intermittent login failures after password resets; the issue is not consistently reproducible, and the vendor suggests monitoring logs in production to gather more data. The release includes new authentication flows and is scheduled for a marketing launch. How should the IT team address this issue before going live?
Answer: 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.
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.
- A mid-sized retailer is in the final SDLC phase (implementation) for a cloud-based inventory management system developed using Agile with two-week sprints and a formal change control process. During user acceptance testing (UAT), business users executed end-to-end scenarios (receiving, picking, shipping, returns) and found that 6 of 80 test cases failed, including a defect that occasionally misstates available-to-promise quantities when two warehouses update stock within the same minute. The project plan targets go-live in five business days, and the vendor proposes documenting the issue as a known defect and fixing it in the first post–go-live patch. Based on the UAT results, what is the most appropriate action?
Answer: Defer go-live until the concurrency-related defect is remediated and successfully re-tested in UAT, because it affects core inventory accuracy and downstream order fulfillment.
This question tests the concept of evaluating UAT defects for go-live readiness in an Agile SDLC, focusing on whether critical issues impacting core business functions should delay deployment. The key facts include a concurrency defect that misstates inventory quantities during simultaneous updates, affecting accuracy and order fulfillment, with a high overall UAT pass rate but a targeted go-live in five days. Option B aligns with best practices in IT project management by prioritizing remediation of high-impact defects to ensure system reliability and minimize operational disruptions post-deployment. Option A is incorrect because enhanced training does not resolve the underlying technical defect, violating principles of defect triage that require fixes for critical issues; option C is wrong as moving to SIT ignores UAT's role in validating business scenarios, per SDLC stage gates; option D is inappropriate as accepting vendor commitments without fixes exposes the business to immediate risks, contrary to risk management frameworks. In similar scenarios, apply a defect severity matrix to classify issues based on business impact and require re-testing for resolution. Always involve stakeholders in go-live decisions to balance schedule pressures with quality assurance.
- A global distributor is at the end of the SDLC for a warehouse scanning solution developed using Agile and integrated with legacy systems. UAT results are mixed: scanning and receiving workflows passed, but cycle count adjustments occasionally post to the wrong GL account due to a mapping table default. The warehouse team is ready, but finance has not signed off. Based on the user acceptance testing results, what is the most appropriate action?
Answer: Defer go-live until the GL mapping defect is corrected and finance completes UAT validation and provides formal sign-off.
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.
- A manufacturing company is preparing to go live with an ERP procurement module in the final SDLC phase (cutover and deployment) using a traditional waterfall approach with formal stage gates. UAT included role-based testing by buyers and approvers, and the team achieved sign-off; however, a late UAT cycle revealed that delegated approval limits are not enforced for temporary approvers during vacations. The project sponsor wants to proceed and "monitor approvals closely" for the first month. How should the IT team address this issue before going live?
Answer: Treat the issue as a high-risk control gap, remediate approval-limit enforcement, and perform targeted UAT regression on delegated approval scenarios before cutover.
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.
- A public sector agency is at the end of the SDLC for an online permitting portal using a waterfall methodology with a formal acceptance phase. UAT included accessibility checks by business users, and testers reported that certain form error messages are not read by screen readers, preventing visually impaired users from completing submissions. The agency's go-live is scheduled to align with a public communication campaign. What potential risk identified during testing requires immediate attention?
Answer: A compliance and service delivery risk, because accessibility failures can prevent equal access and may violate applicable accessibility requirements.
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.
- A subscription software company is preparing a major billing platform release and is in the final release readiness review under an Agile methodology with a defined "definition of done." UAT passed for standard invoicing, but a defect remains open where refunds processed on the last day of the month are posted to the next accounting period in certain time zones. Finance indicates this could affect period-end close and revenue reporting. Based on the UAT results, what is the most appropriate action?
Answer: Defer go-live until the defect is fixed and re-tested in UAT, because it impacts financial reporting accuracy and period-end controls.
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.
- A nonprofit is in the final SDLC stage for a donor management system implemented with a vendor using a waterfall approach and formal acceptance sign-off. UAT scripts were executed, but only by the fundraising team; finance and data privacy stakeholders did not participate. The system includes automated tax receipt generation and donor communication preferences. Which criteria should be prioritized to determine go-live readiness?
Answer: Stakeholder acceptance across impacted business functions, including validation of tax receipt accuracy and communication preference controls, with documented UAT sign-off.
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.
- A utilities company is preparing to deploy a customer outage notification system and is at the UAT completion gate in a phased rollout SDLC. UAT uncovered that customers who opt out of SMS still receive messages if they previously opted in and then changed preferences within 24 hours of an outage event. The team considers this a low impact defect because it affects a narrow timing window. What potential risk identified during testing requires immediate attention?
Answer: A privacy and consent management risk, because messaging users who opted out can violate customer preferences and applicable communication rules.
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.
- A logistics company is completing a transportation management system and is in the UAT and go-live readiness checkpoint under a DevOps-oriented SDLC with automated deployments and manual approval gates. UAT results show all functional scenarios passed, but users report that the new route-planning screen is confusing and increases time-to-complete by about 20% compared with the legacy system. Leadership wants to proceed to meet a contract start date. Which criteria should be prioritized to determine go-live readiness?
Answer: User experience and operational efficiency for key workflows, ensuring the new process does not materially degrade service levels at go-live.
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.
- A regional grocer is at the final go-live decision for a point-of-sale (POS) upgrade using a pilot-and-rollout methodology. UAT in pilot stores passed sales and returns, but testers found that age-restricted item prompts can be bypassed when scanning multiple items quickly, allowing completion of a sale without age verification. The vendor suggests adding a store policy reminder at registers. Which criteria should be prioritized to determine go-live readiness?
Answer: Whether the system enforces legally required controls in high-risk workflows (e.g., age verification), with defects resolved and re-tested before broader rollout.
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.
- A retail bank is at the final go-live decision point for a branch teller system replacement using a phased rollout methodology with parallel run in selected branches. UAT in a pilot branch passed most scenarios, but cash drawer balancing reports do not match transaction totals when a transaction is reversed after end-of-day processing. Operations proposes going live and manually adjusting the report for rare reversals. Based on the user acceptance testing results, what is the most appropriate action?
Answer: 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.
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.
- A financial services firm is at the end of the SDLC (deployment readiness) for a loan origination platform developed under Scrum with a separate release management gate. UAT was executed by loan officers using production-like data; all critical paths passed, but testers discovered that the system allows a loan to be submitted without attaching a required income verification document if the user saves the application as a draft first. The team is considering go-live with this defect logged as "medium" because it occurs only in a specific sequence. What potential risk identified during testing requires immediate attention?
Answer: A compliance and control failure risk, because the workflow can bypass a required documentation control and may lead to noncompliant loan processing.
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.
- A pharmaceutical distributor is finalizing a new order-to-cash system using waterfall with a defined UAT exit checklist. UAT passed core order entry and invoicing, but users discovered that credit holds are not applied to orders created via the EDI interface, only to orders entered manually. The team suggests go-live because most high-value customers place orders manually through account reps. Which criteria should be prioritized to determine go-live readiness?
Answer: Whether all channels that create orders (manual and EDI) enforce critical credit control rules, with successful UAT evidence and business sign-off for control effectiveness.
This question examines go-live criteria in waterfall SDLCs, ensuring consistent controls across interfaces. Key facts include credit holds not applying to EDI orders, with most customers manual, suggesting proceed. Option B aligns with best practices by prioritizing control enforcement and sign-off for risk mitigation. Option A is incorrect as connectivity does not cover business rules; option C is wrong because usability is secondary to controls; option D is inadequate as defect counts ignore specifics. For interfaces, test end-to-end controls in UAT. Use risk-based criteria for readiness.
- A university is in the final SDLC stage for a new student information system built using Agile with incremental releases. UAT was conducted by registrars using a test script library, but several departments reported they could not validate end-to-end scenarios because test data did not include students with multiple concurrent program enrollments. The team is considering go-live based on successful execution of available test scripts. Based on the user acceptance testing results, what is the most appropriate action?
Answer: Expand UAT to include representative test data and execute end-to-end scenarios for complex enrollment cases before final go-live approval.
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.
- A media company is in the final SDLC phase for a digital subscription platform built using Agile with a release train. UAT passed purchase and cancellation flows, but testers reported inconsistent tax calculations for customers in one jurisdiction when a promotional discount is applied. The business suggests launching anyway because the issue affects less than 2% of transactions. Based on the UAT results, what is the most appropriate action?
Answer: 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.
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.
- A healthcare provider is completing the deployment phase of a new patient scheduling system built using a hybrid SDLC (waterfall requirements and design, Agile configuration). UAT included scripted tests and a small set of exploratory tests by clinic staff; most defects were minor, but users reported that appointment reminders sometimes display the wrong clinic address for patients who recently changed primary location. The go-live decision is scheduled for tomorrow, and leadership is focused on meeting the regulatory reporting timeline. Which criteria should be prioritized to determine go-live readiness?
Answer: 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.
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.
- A travel company is in the final SDLC stage for a reservation system using Agile with a release readiness review. UAT passed booking flows, but testers reported that cancellation confirmations are sometimes not generated when a booking includes both flight and hotel components. Customer service warns this could increase disputes and chargebacks. What potential risk identified during testing requires immediate attention?
Answer: A financial and customer dispute risk, because missing confirmations can lead to chargebacks and operational rework, impacting revenue and customer trust.
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.
