Salesforce Updated Certified-Business-Analyst Exam Questions and Answers by bea

This answer selects sprint review as the type of meeting that should be held to review the current build with stakeholders and gather feedback. A sprint review is a meeting that takes place at the end of each sprint in the scrum methodology, where the development team demonstrates the working product increment to the stakeholders and collects their feedback. A sprint review helps to validate the requirements, evaluate the progress, and adjust the priorities for the next sprint. References: https://trailhead.salesforce.com/en/content/learn/modules/agile-development-with-scrum/perform-a-sprint-review

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

A functional requirements specification (FRS) is a document that defines what features and functions a system should provide to meet the business needs and objectives. It describes how users will interact with the system and what outcomes they expect from it. An FRS typically includes use cases, user stories, acceptance criteria, data models, business rules, workflows, diagrams, mockups, and other details that describe how the system should work. A BA should create an FRS to define the enhancement features for the current Salesforce CPQ implementation that must be configured in the next phase of the project. References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-functional-requirements/understand-functional-requirements

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. References: https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models