CERTIFIED-BUSINESS-ANALYST Online Practice Questions and Answers

Correct Answer: B

Correct Answer: B

This answer states that getting approval and signoff on the requirements is the next step for the BA to take before build can begin. Approval and signoff on the requirements means that the stakeholders agree that the requirements are

accurate, complete, and feasible, and that they authorize the development team to start building the solution. Approval and signoff on the requirements helps to avoid scope creep, rework, and miscommunication.

References:

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/prepare-for-the-salesforce-business-analyst-certification-exam

Correct Answer: C

Correct Answer: C

The step that business analyst should take next after receiving urgent high-priority change request middle sprint add change request backlog prioritized next sprint backlog list user stories features enhancements bugs fixes need done project backlog prioritized based importance urgency value risk etc adding change request backlog prioritized next sprint helps maintain scope integrity current sprint avoid disrupting ongoing work respect sprint goal commitment. De-prioritizing some user stories and adding change request current sprint not step that business analyst should take next after receiving urgent high-priority change request middle sprint de-prioritizing some user stories adding change request current sprint helps accommodate new requirement but compromises existing work disrupts sprint goal commitment de-prioritizing some user stories adding change request current sprint should only done exceptional cases after consulting whole team stakeholders sponsors. Beginning working change request soon team has capacity not step that business analyst should take next after receiving urgent high-priority change request middle sprint beginning working change request soon team has capacity helps address new requirement but compromises existing work disrupts sprint goal commitment beginning working change request soon team has capacity should only done exceptional cases after consulting whole team stakeholders sponsors. References: https://trailhead.salesforce.com/en/content/learn/modules/agile-project-management/agile-project-management-scrum

Correct Answer: B

The business analyst should move this item to the definition of done. The definition of done is a set of criteria that must be met before a user story or sprint can be considered complete or ready for release. The definition of done helps to ensure quality, consistency, and transparency across the project team. The step "Code Review by Technical Architect" is not part of the acceptance criteria for a specific user story, but rather a general requirement that applies to all user stories or sprints. References: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/write-user-stories

Correct Answer: C

One benefit of creating user stories that the business analyst can share with the executive sponsor is that it saves time when prioritizing and implementing functionality. User stories are short and simple descriptions of a feature or functionality from the perspective of an end user or customer. User stories help to capture the value and benefits of a solution, rather than the technical details or specifications. User stories also help to facilitate communication and collaboration among stakeholders, developers, and testers. User stories can save time when prioritizing and implementing functionality because they can be easily ranked or ordered based on their importance, urgency, dependency, or impact. User stories can also save time when implementing functionality because they can be easily translated into development tasks, acceptance criteria, and test cases. References: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/write-user-stories

Correct Answer: B

This answer states that using who, what, and why is what each user story should include for optimizing a very manual process in its Salesforce org. Who refers to the persona, which is a fictional representation of a typical user or stakeholder who will use or benefit from a feature or a functionality. What refers to the goal, which is what the user or stakeholder wants to accomplish with the feature or functionality. Why refers to the value, which is why the user or stakeholder wants to accomplish the goal, and how they will measure success. Using who, what, and why can help the BA to write effective user stories that capture and prioritize the requirements, and align them with the stakeholder value and expectations. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

Correct Answer: C

This answer states that scheduling a storyboarding session is what the BA should do to help stakeholders visualize how Marketing Cloud uses insights to create journeys, when timelines are too tight to present a demo, and approval from stakeholders is needed soon in order to keep the project on track. A storyboarding session is a technique that involves creating and presenting a series of sketches or images that illustrate how a user interacts with a system or a feature. A storyboarding session can help the BA to show stakeholders how Marketing Cloud uses insights to create journeys by depicting the steps, actions, and outcomes of the process in a visual and engaging way. A storyboarding session can also help the BA to elicit feedback, validate requirements, and obtain approval from stakeholders in a timely manner.

Correct Answer: A

The option that captures this requirement is "Make the template user-friendly and accessible only by members of the account team." This option clearly states what needs to be done (make the template user-friendly and accessible) and who

it is for (members of the account team). The other options are either incomplete or irrelevant. Option B does not specify what needs to be done or who it is for. Option C does not specify what needs to be done or why it is important.

References:

https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-requirements/understand-requirements

Correct Answer: B

Another important item that the BA should look for in the UAT plan is timelines. Timelines are schedules that specify when each testing activity or task should start and end, and who is responsible for completing them. Timelines help to ensure that testing is conducted in an efficient and timely manner, avoid delays or conflicts in testing resources or availability, and meet the project deadlines and expectations. The other options are either irrelevant or incomplete. Option A does not relate to the UAT plan, but rather to the project budget or scope. Option C does not specify what process maps are needed or how they are used in testing. References: https://trailhead.salesforce.com/en/content/learn/modules/businessanalysis-testing/plan-user-acceptance-testing

Correct Answer: A

A user story is a short description of a feature or functionality from the perspective of an end user. It follows the format "As a , I want , so that ". The who is the user role or persona who will benefit from the feature or functionality. The what is the feature or functionality that the user wants or needs. The why is the benefit or value that the user will get from the feature or functionality. The when and where are not part of a user story format because they are usually captured in other documents or artifacts, such as acceptance criteria or wireframes. References: 1 https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/user-stories

Correct Answer: A

This answer states that change request log is what the BA should use to help them organize and prioritize requests for changes to Salesforce during UAT after receiving numerous emails from stakeholders who formally signed off on requirements. Change request log is a document or a file that records and tracks requests for changes to a project or a product, such as adding, modifying, or removing a feature or a functionality. Change request log is what the BA should use to help them organize and prioritize requests for changes to Salesforce during UAT because it helps the BA to manage and monitor the requests for changes, and to evaluate and approve or reject them based on their impact, urgency, or feasibility.

References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

Correct Answer: A

A challenge is an element of the storytelling process for UX that describes a hurdle that makes it difficult for your heroes to succeed on their journeys. A monster is an element of the storytelling process for UX that describes a person or thing that causes problems for your heroes. A victory is an element of the storytelling process for UX that describes a successful outcome for your heroes. A helper is an element of the storytelling process for UX that describes a person or thing that assists your heroes along their journeys. References: https://trailhead.salesforce.com/content/learn/modules/ux-design-fundamentals/understand-the-storytelling-process

Correct Answer: A

The step that the BA should include in the business flowchart is to capture decision steps and different outcomes. Decision steps are points in the process where a choice or condition needs to be evaluated, and different outcomes are possible depending on the result of the evaluation. Capturing decision steps and different outcomes helps to show the logic and flow of the process, and account for different scenarios or exceptions that may occur. The other options are either irrelevant or incomplete. Option B does not relate to the business flowchart, but rather to the data model or integration design. Option C does not specify what limits to set or how to document them. References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process-mapping/create-a-process-map

Correct Answer: C

This answer suggests adjusting the goal of the user story to be independent as a way to improve this user story for updating its customer portal built on Experience Cloud. The goal of a user story is what the user or stakeholder wants to accomplish, why they want to accomplish it, and how they will measure success. The goal of a user story should be independent, meaning that it does not depend on or overlap with other user stories. This user story has a goal that is too broad and complex, as it includes multiple features or functionalities (chat with a support agent, view account, see orders, ask questions) in one user story. Adjusting the goal of the user story to be independent can help to break down this user story into smaller and simpler user stories that can be completed in one sprint. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements