Need for End-User Testing in Packaged Software?
Short answer
B Acquiring packaged software reduces end-user testing requirements compared to in-house development because vendors perform foundational quality assurance upfront.
Question
Key Takeaways
Tests your understanding of procurement trade-offs, with the common trap being the confusion between vendor quality assurance and the complete elimination of end-user validation.
Acquiring packaged software reduces the end-user testing burden compared to custom development, as vendors handle foundational quality assurance before delivery. Community consensus aligns with option B, recognizing that outsourcing shifts but does not erase acceptance testing obligations.
Common mistake: Option D (unchanged) is frequently selected under the assumption that User Acceptance Testing scales identically across both sourcing models, overlooking the significant reduction in core functionality validation provided by the vendor.
Expert Analysis
Why the Answer Is Correct
Acquiring packaged software significantly reduces the end-user testing burden because the vendor has already conducted extensive unit and system testing. ISACA guidelines emphasize that outsourcing development shifts foundational validation responsibilities away from internal teams, allowing end users to focus solely on business-fit verification rather than rebuilding test cases from scratch.
Why the Other Options Are Wrong
Option A is incorrect because purchasing software eliminates custom coding phases, which inherently lowers total testing volume rather than increasing it. Option C fails because acceptance testing remains mandatory to verify integration, security configurations, and workflow alignment. Option D is a frequent trap, assuming User Acceptance Testing scales identically across both models, while ignoring the substantial baseline testing already completed by the vendor.
Community Comment Notes
The voting split between options B and D reflects ongoing debate among candidates regarding audit standards. Comment [1] argues for option D by emphasizing that thorough end-user validation is still required post-acquisition. Conversely, comment [2] correctly identifies that vendor-pretested functionality naturally reduces the overall testing scope, aligning with official CISA review material expectations.
Exam Strategy
When evaluating IT procurement scenarios, always distinguish between vendor-provided quality assurance and mandatory business acceptance testing. Remember that while packaged solutions streamline development, your audit checklist must still account for configuration validation and integration testing before go-live.
Frequently Asked Questions
Why isn't end-user testing completely eliminated?
Is testing effort truly unchanged for packaged software?
Community Votes
50% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
veli_117 👍 1 Answered DAlthough acquired systems are tested by the vendor prior to distribution, these systems and any subsequent changes should be tested thoroughly by the end user and the system maintenance staff.
-
MJORGER 👍 1 Answered BB. reduced When a business acquires a software package, it’s typically already been tested extensively by the vendor, so the need for end-user testing is generally reduced.
-
Sibsankar 👍 1A is right
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All CISA Questions
Access 400 questions with complete answers and detailed explanations.
View Full CISA Practice Test →