Universal Containers is merging with another company that uses a different CRM. During
requirements workshops, the incoming support team has been proactively sharing ideas,
but the incoming sales team has been less engaged.
What should the BA do to ensure they are able to gather the necessary requirements?
A. Put extra effort into following up with the sales team … requirements. B. Shift focus to the support team since they are proactively providing requirements. C. Continue the requirements workshops and hope the salesforce become more responsive.
Answer: A
Explanation:
Proactively engaging the sales team is crucial for gathering a comprehensive set of
requirements:
Ensuring Inclusivity: All functional teams must provide input for a successful CRM
merger. Salesforce encourages proactive engagement with less responsive
stakeholders to ensure all perspectives are considered.
Addressing Resistance: Direct follow-ups allow the BA to uncover reasons for
disengagement and address them effectively.
Balanced Requirements Gathering: This approach prevents an imbalance in
requirements that may lead to solutions favoring one team over another.
Question # 22
Sales managers at Northern Trail Outfitters (NTO) have received feedback from sales reps
that record pages are slow and often take longer to load when using the app on the phone.
The business analyst (BA) has been asked to evaluate NTO’s org to find out which pages
are the slowest to load when using the app on the phone.
What is the first step the BA should take to help resolve the issue?
A. Create a new page layout for the phone. B. Use performance analyzer to view the assessment. C. Confirm steps to reproduce the issue.
A few users have reported an issue with the recent Cloud Kicks?
Salesforce implementation.
What should the business analyst do first?
A. Gather requirements from end users. B. Provide additional end user training. C. Create a high priority bug for a quick fix.
Answer: A
Explanation:
When addressing issues reported by users following a Salesforce implementation, the
business analyst's primary responsibility is to understand and analyze the problem
comprehensively before taking any corrective action.Gathering Requirements: This step involves communicating directly with the end
users to identify their issues and expectations. This ensures that the analyst has a
clear understanding of the problem's root cause. Reference: Salesforce Business
Analysis documentation emphasizes requirements elicitation and validation as
critical first steps in identifying misalignments or implementation gaps.
Avoiding Premature Actions: Jumping to training or creating a high-priority bug
may address symptoms rather than the actual problem. Salesforce implementation
guides and best practices stress the importance of first understanding the user
experience and system functionality through direct feedback.
Stakeholder Engagement: Engaging stakeholders and users is a critical phase
outlined in Salesforce's business analysis processes. It ensures that the problem
definition aligns with the users' needs and organizational objectives.
Follow-Up Steps: Once requirements are gathered, the next steps involve
validating and analyzing the data, and based on findings, proposing appropriate
solutions such as additional training, system adjustments, or bug fixes. Salesforce
Business Analyst responsibilities include continuous alignment of implemented
solutions with business needs.
This approach aligns with Salesforce's process-driven methodology for ensuring successful
system adoption and user satisfaction.
Question # 24
A new employee at Universal Containers just sent the business analyst (BA) a Slack
message with an named User3tories_v37_final_final_final.docx.
Which best practice should the 6A train the employee on first?
A. Use standard naming conventions. B. Use acceptance criteria to define success. C. Use a version control repository.
Answer: C
Explanation: This answer states that using standard naming conventions is the best
practice that the BA should train the employee on for sending a document named
UserStories_v37_final_final_final.docx. A standard naming convention is a set of rules or
guidelines that define how to name or label a document or a file in a consistent and
meaningful way. A standard naming convention typically includes elements such as project
name, document type, version number, date, author, etc. Using standard naming
conventions is the best practice that the BA should train the employee on for sending a
document because it helps the BA to organize and manage documents or files more
efficiently and effectively, and to avoid confusion or duplication among them. References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analystquick-
look/use-stakeholder-engagement-skills
Question # 25
Universal Containers is nearing the launch date for its new Salesforce Loyalty Management program. The business analyst (BA) has ensured the user acceptance testing (UAT) plan has the proper test scripts. What is another important item the BA should look for in the UAT plan?
A. Estimated cost B. Timelines C. Process maps
Answer: B Explanation:Another important item that the BA should look for in the UAT plan is timelines. Timelinesare schedules that specify when each testing activity or task should start and end, and whois responsible for completing them. Timelines help to ensure that testing is conducted in anefficient and timely manner, avoid delays or conflicts in testing resources or availability, andmeet the project deadlines and expectations. The other options are either irrelevant orincomplete. Option A does not relate to the UAT plan, but rather to the project budget orscope. Option C does not specify what process maps are needed or how they are used intesting. References: https://trailhead.salesforce.com/en/content/learn/modules/businessanalysis-testing/plan-user-acceptance-testing
Question # 26
Cloud Kicks (CK) wants to Improve the current business process for moving orders from the warehouse to the customer as part of a Commerce Cloud Implementation. The business analyst would like to gather more Information to create the future state process. Who is the most appropriate subject matter expert (SME) to confirm the current business process and elicit deeper understanding of CK's goals, opportunities, and pain points?
A. Sales manager B. Chief financial officer C. Supply chain manager
Answer: C Explanation:The most appropriate subject matter expert (SME) to confirm the current business processand elicit deeper understanding of CK’s goals, opportunities, and pain points is the supplychain manager. The supply chain manager is responsible for overseeing the flow of goodsfrom the warehouse to the customer, and has the most knowledge and insight into thecurrent business process. The supply chain manager can also provide valuable feedbackand suggestions for improving the business process and achieving the desired outcomes.The sales manager and the chief financial officer are not directly involved in the businessprocess of moving orders from the warehouse to the customer, and may not have the samelevel of expertise or interest as the supply chain manager. References: CustomerDiscovery, Get Started with Salesforce Business Analyst Certification Prep, Cert Prep:Salesforce Business Analyst
Question # 27
A business analyst (BA) is preparing to demonstrate the functionality built by the development team over the last sprint to the client. Which technique should the BA use to create a compelling demo?
A. Functional - requirements, code/configuration, run as user B. Storytelling - hero, challenge, helper, victory C. STAR method - situation, task, action, result
Answer: B Explanation:In creating a compelling demo, the storytelling technique is highly effective. This approachinvolves framing the demo narrative around a hero (typically the end-user), presenting achallenge they face, introducing the solution (the Salesforce functionality) as the helper,and showcasing the victory, which is the successful resolution of the challenge through theimplemented functionality. This technique engages the audience by making thedemonstration relatable and showing the practical value of the solution in a real-worldcontext. It emphasizes the impact of the features on the users' daily tasks and how itaddresses their specific needs.
Question # 28
Cloud Kicks (CK) is expanding and has many different departments in manufacturing and delivery. CK needs to prepare for a new Sales Cloud implementation for it, 6,000 users. To increase adoption, the business analyst (BA) wants to break down existing sides between the manufacturing and delivery departments. Which planning approach should the ISA take to get buy-in from users?
A. Recombined clear owners up for the platform and identity executive sponsors. B. Assign a team to start building a prototype of product functionality. C. Document user requirement from each department during discovery sessions.
Answer: A Explanation: This answer states that documenting user requirements from eachdepartment during discovery sessions is what the BA should do to get buy-in from users forpreparing for a new Sales Cloud implementation for 6,000 users at CK. User requirementsare the needs, expectations, and objectives of the users for the Sales Cloudimplementation. Discovery sessions are meetings or workshops where the BA gathers andclarifies user requirements from different stakeholders. Documenting user requirementsfrom each department during discovery sessions means that the BA records and organizesthe information obtained from different stakeholders from different departments, such asmanufacturing and delivery, in a clear and concise way. Documenting user requirementsfrom each department during discovery sessions is what the BA should do to get buy-infrom users for preparing for a new Sales Cloud implementation because it helps the BA tounderstand and validate the user requirements, and to communicate and align them withthe project scope and goals. References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analystquick-look/use-stakeholder-engagement-skills
Question # 29
Cloud Kicks is preparing for User Acceptance testing (UAT) related to an upcoming major release. To which environment should a business analyst recommend that users log in to complete their assigned testing?
A. Full Sandbox B. Production C. Developer
Answer: A Explanation: This answer states that a full sandbox is what users should log in tocomplete their assigned testing for preparing for UAT related to an upcoming major releaseat Cloud Kicks. A full sandbox is a type of sandbox that copies all data and metadata froman organization’s production environment into an isolated environment for development,testing, or training purposes. A full sandbox is what users should log in to complete theirassigned testing because it provides a realistic and accurate representation of how the newfunctionality would work in production, and it allows users to test without affecting live dataor operations. References:https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-anddevelopment-models/application-lifecycle-and-development-models-sandboxes
Question # 30
The product owner at Cloud Kicks wants to know which user stories fail user acceptance testing (UAT) and the potential impact on other successful use stories. Currently, user stories are stored in a shared spreadsheet. What should a business analyst recommend to ensure UAT result are document security.
A. Give all stakeholder the ability to edit the shared spreadsheet. B. Ask each tester to admit share spreadsheet. C. Enable history y in the shared spreadsheet.
Answer: C Explanation:This answer states that enabling history in the shared spreadsheet is what the BA shouldrecommend to ensure UAT results are documented securely after receiving verbalacceptance of all user stories by the product owner for developing a new Commerce Cloudimplementation at CK. History is a feature that allows users to view, restore, or compareprevious versions of a document or a file. Enabling history in the shared spreadsheetmeans 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 iswhat the BA should recommend to ensure UAT results are documented securely becauseit helps the BA to track and record who made what changes to user stories and when, andto prevent or recover any accidental or unauthorized changes to user stories. References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst- quick-look/use-stakeholder-engagement-skills