Salesforce Certified Business Analyst Practice Test - Questions Answers, Page 27

This answer states that number of passed test cases divided by total number of test cases is how the success rate is calculated after completing user acceptance testing (UAT) for a Commerce Cloud implementation at CK. Test cases are scenarios or steps that verify or validate if a feature or a functionality meets the acceptance criteria or requirements. Passed test cases are test cases that meet or pass the acceptance criteria or requirements. Total number of test cases are all test cases that are executed or performed for UAT. Number of passed test cases divided by total number of test cases is how the success rate is calculated because it measures how many test cases meet or pass the acceptance criteria or requirements out of all test cases executed or performed for UAT.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

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.

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

This answer states that identifying personas, documenting the current state, and proposing the future state are the key steps that the BA should take next after identifying the stakeholders, reviewing the project scope, and scheduling each workshop for preparing for the initial requirements gathering workshops with CK on a new Sales Cloud project. Personas are fictional characters that represent the typical users or customers of a product or a service. Current state is how a business process or a system works or operates at present. Future state is how a business process or a system should work or operate in the future. Identifying personas, documenting the current state, and proposing the future state are the key steps that the BA should take next after identifying the stakeholders, reviewing the project scope, and scheduling each workshop because they help the BA to understand and empathize with the users or customers of Sales Cloud, to analyze and document the existing problems or issues with Sales Cloud, and to suggest and validate possible solutions or improvements for Sales Cloud.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-process-mapping-to-understand-your-business

This answer states that enabling history in the shared spreadsheet is what the BA should recommend to ensure UAT results are documented securely after receiving verbal acceptance of all user stories by the product owner for developing a new Commerce Cloud implementation at CK. History is a feature that allows users to view, restore, or compare previous versions of a document or a file. Enabling history in the shared spreadsheet means that the BA turns on this feature in the spreadsheet where user stories are stored, such as Google Sheets, Microsoft Excel, etc. Enabling history in the shared spreadsheet is what the BA should recommend to ensure UAT results are documented securely because it helps the BA to track and record who made what changes to user stories and when, and to prevent or recover any accidental or unauthorized changes to user stories.

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

This answer states that eliciting requirements, documenting requirements, analyzing information, and facilitating solutions are the key activities that the BA must complete prior to beginning development for a Service Cloud implementation at UC. Eliciting requirements means that the BA gathers and clarifies the needs, expectations, and objectives of the stakeholders for the Service Cloud implementation. Documenting requirements means that the BA records and organizes the information obtained from eliciting requirements in a clear and concise way. Analyzing information means that the BA reviews and evaluates the information obtained from documenting requirements to identify gaps, issues, or opportunities for improvement. Facilitating solutions means that the BA proposes and validates possible solutions or alternatives for addressing the gaps, issues, or opportunities for improvement identified from analyzing information. Eliciting requirements, documenting requirements, analyzing information, and facilitating solutions are the key activities that the BA must complete prior to beginning development for a Service Cloud implementation because they help the BA to define and communicate the scope and specifications of the Service Cloud implementation, and to ensure that they meet the stakeholder's needs, expectations, and objectives.

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

This answer states that intent of both parties is what is important for the BA to consider when responding to feedback from UC's marketing team who feels that their current solution for managing leads in Sales Cloud is incomplete. Intent of both parties means that what both UC's marketing team and UC's Salesforce team want to achieve or accomplish by implementing a solution for managing leads in Sales Cloud, such as increasing lead conversion rate, improving lead quality, enhancing lead tracking, etc. Intent of both parties is what is important for the BA to consider when responding to feedback from UC's marketing team because it helps the BA to align and communicate their goals and expectations, and to identify and resolve any gaps or issues between them.

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

This answer states that asking for specific examples to review is how the BA should respond to feedback from UC's project manager who tells the BA that the developers on the team are having trouble understanding what to build because the acceptance criteria for the Sales Cloud user stories are confusing. Asking for specific examples to review means that the BA requests the project manager or the developers to provide concrete instances or scenarios of where and how the acceptance criteria for the Sales Cloud user stories are confusing, such as ambiguous, inconsistent, or incomplete acceptance criteria. Asking for specific examples to review is how the BA should respond to feedback from UC's project manager because it helps the BA to clarify and verify the feedback, and to revise and update the acceptance criteria accordingly.

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

This answer states that conducting multiple dry runs is the additional activity that is most likely to result in a successful sprint demo for demonstrating some new Sales Cloud functionality for a project's stakeholders at Cloud Kicks. A dry run is a practice or a rehearsal of a presentation or a demonstration before the actual event. Conducting multiple dry runs means that the BA performs and repeats the presentation or the demonstration of the new Sales Cloud functionality several times before showing it to the project's stakeholders. Conducting multiple dry runs is the additional activity that is most likely to result in a successful sprint demo because it helps the BA to prepare and polish their presentation or demonstration skills, to identify and fix any errors or issues in the new Sales Cloud functionality, and to anticipate and address any questions or feedback from the project's stakeholders.

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

This answer states that saving user stories outside of a shared repository is why UC's development team reports they are unable to confirm which user stories are ready to be built after receiving verbal acceptance of all user stories by the product owner and setting their status to 'Ready for Development' on a spreadsheet by UC's BA. A shared repository is a common or central location where documents or files can be stored, accessed, and updated by multiple users or teams. Saving user stories outside of a shared repository means that the BA stores user stories in a place where they are not visible or available to other users or teams, such as their personal computer, email, etc. Saving user stories outside of a shared repository is why UC's development team reports they are unable to confirm which user stories are ready to be built because it prevents them from seeing or accessing the latest version or status of user stories, and it creates confusion or inconsistency among them.

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