Salesforce Certified Business Analyst Practice Test - Questions Answers, Page 8
List of questions
Question 71

The business analyst at Universal Containers is helping the team transition from workflow rules to flows. The work has been built and it is time to kick off user acceptance testing (UAT).
What is the goal of UAT?
Explanation:
The goal of user acceptance testing (UAT) is to ensure what was originally requested is being delivered by the development team. UAT is the final phase of testing before a solution is released to production. UAT involves users or stakeholders who validate that the solution meets their needs and expectations, based on the user stories and acceptance criteria. UAT helps to verify that the solution is fit for purpose and ready for launch.
Reference: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/user-acceptance-testing
Question 72

Northern Trail Outfitters is Updating Its customer portal built on Experience Cloud. The team has drafted a user story:
'As a customer, I want to be able to chat with a support agent and view my account, see my orders, and ask questions via the customer port.
What should a business analyst do to improve this user story?
Explanation:
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.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements
Question 73

The Salesforce project team at Cloud Kicks is about to start a project that crosses sales and service teams. The business analyst (BA) has been tasked with writing user stories with the teams in a workshop.
What should the BA keep in mind during the process?
Explanation:
One thing that user stories help the business analyst do is encourage iterative development. Iterative development is an approach that breaks down a project into smaller cycles or iterations, each delivering a working piece of functionality or value to the user. User stories are well suited for iterative development because they are concise, focused, and prioritized based on user needs and value. User stories help to deliver features faster and more frequently, while allowing for feedback and changes along the way.
Reference: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories
Question 74

During a sprint grooming session for the Sales Cloud implementation at Cloud Kicks, the development team mentions the step 'Code Review by Technical Architect' listed within the acceptance criteria needs to be adjusted.
Which location should the business analyst move this item to?
Explanation:
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.
Reference: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/write-user-stories
Question 75

The business analyst (BA) at Universal Containers has been capturing the requirements for a major Sales Cloud release. An admin has been deploying the resulting system changes. The quality assurance (QA) team has run into challenges when testing the changes. The BA is unaware of deployment and testing challenges.
What should the BA do to resolve these challenges with the release team?
Explanation:
This answer states that associating each set of metadata changes to the corresponding user story is what the BA should do to resolve these challenges with the release team. Metadata changes are modifications to the configuration or customization of Salesforce, such as fields, objects, layouts, workflows, or apex code. Associating each set of metadata changes to the corresponding user story can help to track and manage the changes, and link them to the business requirements and acceptance criteria. This can also help to improve the communication and collaboration between the BA, the admin, and the QA team, and avoid any confusion or errors during deployment and testing.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models
Question 76

A group of business analysts (BA) at Universal Containers have been working with different teams of stakeholders on eliciting requirements for a new Salesforce app. The BAs have gathered and documented all of the information in a central location. Upon review of the requirements, the BAs discovered that changes made to the documentation were overwritten by each other, and they will lose time recapturing them.
What should the BAs do differently to prevent this error from happening?
Explanation:
The business analysts should use a shared system that has version control to prevent this error from happening. Version control is a feature that allows users to track and manage changes made to documents or files over time. Version control helps to avoid overwriting or losing previous versions of documents or files by creating backups or snapshots of each change. Version control also helps to compare different versions of documents or files and resolve any conflicts or discrepancies.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/collaboration-with-stakeholders
Question 77

The business analyst (BA) at Northern Trail Outfitters is writing user stories for a Service Cloud implementation.
In which order should the BA arrange the three components of a user story?
Explanation:
This is the correct order for arranging the three components of a user story. The first component is ''As a <xyz>'', which specifies the role or persona of the user who will benefit from the user story. The second component is ''I want <xyz>'', which describes the goal or feature that the user wants to achieve or use. The third component is ''so that <xyz>'', which explains the reason or value behind the goal or feature for the user.
Reference: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/write-user-stories
Question 78

Universal Containers is currently doing user acceptance testing for a global customer service project that leverages Service Cloud. A stakeholder is executing a test case for a specific user story. The stakeholder has provided this feedback:
* The functionality described in the test case is working as expected.
* The stakeholder wants to change the label of several fields described in the test case.
* The stakeholder wants to add two new fields that were excluded from the test case.
Which step should the business analyst take next?
Explanation:
This answer suggests acknowledging the feedback, creating a new user story that includes the field changes, and asking the stakeholder to update the existing test case to show it was successfully tested as the next step for the BA after receiving this feedback from a stakeholder during user acceptance testing for a global customer service project that leverages Service Cloud. Acknowledging the feedback shows respect and appreciation for the stakeholder's input and involvement. Creating a new user story that includes the field changes helps to capture and prioritize the new requirements, and avoid scope creep or impact on other user stories. Asking the stakeholder to update the existing test case to show it was successfully tested helps to validate and document that the functionality described in the test case is working as expected.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements
Question 79

A business analyst (BA) at Northern Trail Outfitters is preparing for a user acceptance testing (UAT) session for a global Sales Cloud project.
What should the BA do to engage the business most effectively during UAT'?
Question 80

The business analyst (BA) is preparing for user acceptance testing (UAT) for Northern Trail Outfitters' new Service Cloud implementation. The BA secured the sandbox for the testing environment, wrote test cases, and created a process to track and manage reported bugs.
Which additional step is required during the UAT planning process?
Explanation:
The first step that the business analyst should take before starting UAT is to identify power users. Power users are users who have extensive knowledge and experience with using Salesforce, and can provide valuable feedback and insights during UAT. Power users can help to write, review, and execute UAT scenarios, as well as train and support other users during UAT. Power users can also act as champions for change management, and help to promote adoption and satisfaction with the solution. The business analyst should identify power users from different roles, teams, or regions, depending on the scope and scale of the project. The business analyst should also communicate with power users about their expectations, responsibilities, and availability for UAT.
Question