Table of Contents
Question
A business analyst at Universal Containers has begun user acceptance testing for a new Experience Cloud implementation with the project team. A major gap for one of the personas was identified in the documented scenarios. What went wrong?
A. Failure to include all stakeholders in the requirements gathering process
B. Failure to perform thorough unit testing during the development process
C. Failure to validate the application against the functional requirements
Answer
A. Failure to include all stakeholders in the requirements gathering process
Explanation
User acceptance testing (UAT) is a phase of software development where the intended users of a system or application test it in a real-world scenario to verify that it meets their needs and expectations. UAT is usually performed after the system has been developed and unit tested by the developers, and before it is deployed to production.
A major gap for one of the personas in the documented scenarios means that there is a significant mismatch between what the system can do and what the user needs or wants it to do. This can result in user dissatisfaction, reduced adoption, or failed implementation.
There are several possible reasons why a major gap for one of the personas was identified in UAT, but based on the options given, I think the most likely answer to your question is A. Failure to include all stakeholders in the requirements gathering process. This is because if some stakeholders were not involved or consulted during the requirements gathering process, their needs and expectations may not have been captured or prioritized correctly. This can lead to missing or incorrect features or functionalities in the system that do not meet the user’s goals or pain points.
The other statements are less likely because:
B. Failure to perform thorough unit testing during the development process: This statement is less likely because unit testing is a type of testing that focuses on verifying that each individual component or module of a system works as expected. Unit testing does not usually involve testing the system from the user’s perspective or validating that it meets the functional requirements.
C. Failure to validate the application against the functional requirements. This statement is less likely because functional requirements are specifications that describe what a system should do or how it should behave. Functional requirements are usually validated during functional testing, which is a type of testing that verifies that each feature or functionality of a system works according to the requirements. Functional testing is typically performed before UAT and can help identify any gaps or defects in the system before it reaches the users.
Reference
Salesforce Certified Business Analyst certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Salesforce Certified Business Analyst exam and earn Salesforce Certified Business Analyst certification.