The business analyst (BA) At universal Containers is writing user stories for its Salesforce
Field Service implementation.
What should the BA evaluate to understand the understand the risk level of the user
stories?
A. Scope, resource, and documentation impact B. Team, budget, and timeline impact C. Technical, operational, and regulatory impact
Answer: A
Question # 52
The lead business analyst (BA) at Cloud Kicks is putting together user Stories for the new
sales process that will
be implemented in Sales Cloud. The lead BA is advising junior BAS on how to construct a
user story.
What should the lead BA tell the junior BAs to include in a user story?
A. Include the V2MOM structure B. Include who, What, and why C. Include technical details
Answer: B Explanation:
The lead BA should tell the junior BAs to include who, what, and why in a user story. Who,
what, and why are the essential elements of a user story that define who is requesting a
feature or functionality (the user or persona), what they want to achieve or accomplish (the
goal or value), and why they want it (the reason or benefit). A user story should include
who, what, and why because it helps to:
Clarify the scope, functionality, and quality of the user story Provide a basis for testing and validating the work done
Ensure that it meets the user’s needs and expectations The other options are
either incorrect or irrelevant. Option A is incorrect because V2MOM is a structure
that defines an organization’s vision, values, methods, obstacles, and measures,
not a user story. Option C is incorrect because technical details are not part of
auser story, but rather part of acceptance criteria or design specifications.
References: https://trailhead.salesforce.com/en/content/learn/modules/businessanalysis-user-stories/write-user-...
Question # 53
During a discovery session with several stakeholders from universal Container (UC)
services team, the business analyst (BA) learned that UC recently implemented as Experience Site that allows customers to view Knowledge article and submit cases. The
stakeholders have asked for suggestions to determine if the current solution is adding
value to the business.
What should the BA recommend?
A. Review the services team’s goal’ initiatives, strategies, and obstacles. B. Review the Einstein Article Recommendations feature in the services team’s org. C. Review user stories on the services team’s development backlog.
Answer: A Explanation: This answer states that reviewing the services team’s goals, initiatives,
strategies, and obstacles is what the BA should do to determine if the current solution of
implementing an Experience Site that allows customers to view Knowledge articles and
submit cases is adding value to UC’s business. Goals are what the services team wants to
achieve or accomplish in terms of business outcomes or benefits. Initiatives are what the
services team plans to do or implement to achieve their goals. Strategies are how the
services team executes or delivers their initiatives. Obstacles are what prevents or hinders
the services team from achieving their goals, implementing their initiatives, or executing
their strategies. Reviewing the services team’s goals, initiatives, strategies, and obstacles
means that the BA analyzes and documents these elements related to implementing an
Experience Site that allows customers to view Knowledge articles and submit cases.
Reviewing the services team’s goals, initiatives, strategies, and obstacles is what the BA
should do to determine if the current solution is adding value to UC’s business because it
helps the BA to measure and evaluate the performance and impact of the current solution
against these elements.
References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-businessanalyst-quick-look/use...
Question # 54
Northern Tail Outfitters has fixed a business analyst (BA to help revamp the order
management process. During the backlog regiment session, the BA discovers the few user
satires are no longer needed.
What should the BA do next?
A. Cancel these user stones and remove them from the backlog. B. Move these user stones to the button of the backlog. C. Review these user stones in the backlog at the next sprint retrospective.
Answer: C Explanation:
This answer states that reviewing these user stories in the backlog at the next sprint
retrospective is what the BA should do next after discovering that a few user stories are no
longer needed for revamping the order management process at NTO. User stories are
short descriptions of a feature or a functionality from a user’s perspective. Backlog is a list
of user stories that need tobe prioritized and completed for a project or a product. Sprint
retrospective is a meeting or a workshop where the project team reviews and reflects on
their performance and progress in the previous sprint. Reviewing these user stories in the
backlog at the next sprint retrospective means that the BA discusses and evaluates these
user stories with the project team to determine if they are still relevant, valuable, or feasible
for revamping the order management process. Reviewing these user stories in the backlog
at the next sprint retrospective is what the BA should do next after discovering that a few
user stories are no longer needed because it helps the BA to update and maintain the
backlog, and to ensure that the user stories align with the project scope and goals.
References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-businessanalyst-quick-look/use...
Question # 55
Northern Trail Outfitters follows an Agile methodology for its Marketing Cloud projects. The
project team creates several types of documents.
Which document should a business analyst use to. capture the software and behavioral
requirements of the application?
A. Scope statement specification B. Functional requirements specification C. System requirements specification
Answer: B Explanation: A functional requirements specification is a document that describes the software and behavioral requirements of an application, such as what features it should have and how it should behave under different scenarios. It can help communicate the expectations and needs of the stakeholders to the development team. A scope statement
specification is a document that defines the project scope, objectives, deliverables,
assumptions, constraints, and exclusions. It does not describe the software and behavioral
requirements of an application. A system requirements specification is a document that
describes the technical requirements of an application, such as hardware, software,
security, performance, and reliability. It does not describe the software and behavioral
requirements of an application. References: 1
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analystcertification-...
Question # 56
A business analyst (BA) at Cloud Kicks has been tasked with preparing for requirements
gathering workshops .. an upcoming Sales Cloud implementation.
Which documentation is mast beneficial for the BA to define the scope of the project?
A. Detailed Process Map B. Value Stream Map C. Suppliers. Inputs, Process, Outputs, Customers (SIPOC) Map
Answer: C Explanation: The documentation that is most beneficial for the business analyst to define
the scope of the project is a SIPOC (Suppliers, Inputs, Process, Outputs, Customers) Map.
A SIPOC Map is a high-level process map that shows the key elements of a process, such
as the suppliers, inputs, outputs, and customers. A SIPOC Map can help define the scope
and boundaries of a project by identifying what triggers the process, what are the inputs
and outputs of the process, who are involved in or affected by the process, and what are
the expectations or requirements of the process. A SIPOC Map can also help communicate
and validate the scope with stakeholders and sponsors. A detailed process map is not
documentation that is most beneficial for the business analyst to define the scope of the
project. A detailed process map is a diagram that shows the steps, activities, and decisions
involved in a process. A detailed process map can help document existing processes in a
clear and concise way that can be easily understood by anyone involved in the project, but
it does not help define the scope or boundaries of the project. A value stream map is not
documentation that is most beneficial for the business analyst to define the scope of the
project. A value stream map is a diagram that shows the flow of materials and information,
the value-added and non-value-added activities, and the cycle times and wait times
involved in a process. A value stream map can help identify waste, inefficiencies, and
opportunities for improvement within a process, but it does not help define the scope or
boundaries of the project.
References:https://trailhead.salesforce.com/en/content/learn/modules/businessanalyst_skills-strategies/explore...
Question # 57
The business analyst (BA) is preparing for the initial requirements gathering workshops
with Cloud Kicks on a new Sales Cloud project. The BA has identified the stakeholders,
reviewed the project scope, and scheduled each workshop.
Which key steps should the BA take next?
A. Identify persona, document the current state, and purpose the future state. B. Document the current state, offer a survey to stakeholder, and propose the future state. C. Document the current state, email it to attendees with an agenda, and propose the future state.
Answer: A
Explanation:
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.
References:https://trailhead.salesforce.com/en/content/learn/modules/salesforce-businessanalyst-quick-look/use...
Question # 58
The business analyst (BA) at Universal Containers is also its primary system admin. The
BA knows that version is mandatory when it comes to releasing.
What is the most efficient process for the BA to track the changes they are committing?
A. Agile planning B. DevOps C. Metadata backups
Answer: B
Question # 59
The business analyst at Northern Trail Outfitters receives a requirement from the CRM
manager to have visibility into their team's queues to monitor open cases.
Which user story meets this requirement?
A. As a CRM manager, I need a record-triggered flow to view my team's work queues so 1
can monitor their open tickets. B. As a CRM manager, I need to see my team’s work queues so I can monitor their open tickets. C. As a user, I need to see case queue to monitor my team's work.
Answer: B
Question # 60
The business analysis (BA) at Northern Trail Outfitters is assigned to a project to help
revamp its Experience Cloud implementation.
When assessing the existing process, which type of diagram should the BA use to identify
waste within and between processes?
A. Suppliers, Inputs, Process, Outputs, Customers (SIPOC) Map B. Detailed Process Map C. Value Stream Map