- Email support@dumps4free.com
A sales manager express frustration that the sales team is failing to enter calls in salesforce. The manager is hoping to resolve the issue quickly and has limited time and budget to complete revamp existing tools and process, the sales manager reaches out to the business analyst (BA) for recommendation. What should the BA do next?
A. Engage a developer to scope a custom solution
B. Research third-party apps on the AppExchange.
C. Export a weekly report of user activity.
Explanation:
This answer suggests researching third-party apps on the AppExchange as the next thing that the BA should do after a sales manager expresses frustration that the sales team is failing to enter calls in Salesforce, and hopes to resolve the issue quickly and has limited time and budget to complete revamp existing tools and process. The AppExchange is an online marketplace where customers can find, try, buy, and install apps that extend the functionality of Salesforce.
Researching third-party apps on the AppExchange can help the BA to find a possible solution that can address the issue of entering calls in Salesforce without requiring a lot of time, budget, or customization. Researching third-party apps on the AppExchange can also help the BA to compare different features, prices, ratings, and reviews of various apps that can meet the sales manager’s needs and expectations.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills
At the start of a new Agile development project, the Universal Containers' product owner asked the business analyst (BA) to clearly define the intended results of the work based on stakeholder needs. The development and implementation teams will use the intended results to plan product decisions. The definition should avoid assumptions and focus on stakeholder value. Which element should the BA choose to define the intended results?
A. Requirements
B. User stories
C. Epics
Explanation:
This answer chooses user stories as the element that the BA should use to define the intended results of the work based on stakeholder needs. User stories are short and simple descriptions of a feature or a functionality from the perspective of an end user or a stakeholder. User stories can help the BA define what stakeholders want to accomplish, why they want to accomplish it, and how they will measure success. User stories can also help the development and implementation teams to plan product decisions based on stakeholder value.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements
Cloud Kicks will launch a new customer experience portal. During discussions with the VP of customer service, a business analyst (BA) recorded the following:
• All logins must use multi-factor authentication (MFA).
• Portal pages should load within 2 seconds.
How should the BA document the items?
A. functional requirement
B. Non-functional requirement
C. User story
Explanation:
The items that the business analyst documented are non-functional requirements. Non-functional requirements are statements that describe how a system or solution should perform, behave, or appear, rather than what it should do or provide. Non-functional requirements can include aspects such as usability, reliability, security, availability, scalability, etc. Non-functional requirements help to ensure that the system or solution meets the quality standards and expectations of the stakeholders or users. The items that the business analyst documented are non-functional requirements because they specify how Sales Cloud should perform (portal pages should load within 2 seconds) and behave (all logins must use multi-factor authentication).
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/requirements-management
Universal Containers is developing a new recruitment app using Service Cloud. The project team has started writing user stories including:
"As a human resources (HR) manager, I need to document the progress of a candidate's submission so I can manage the candidate's application throughout the recruiting process."
What is one definition of done for this user story?
A. The Candidate Status field can be updated.
B. The acceptance criteria has been approved.
C. The Candidate object has Edit access.
Explanation:
A definition of done is a set of criteria that determines when a user story is completed and ready for deployment. It typically includes technical, functional, and quality aspects of the user story, such as code quality, unit testing, documentation, performance, security, and usability. One possible definition of done for this user story is “The Candidate Status field can be updated.” This criterion checks if the functionality of updating the candidate’s submission progress is working as expected and meets the user’s need.
References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/define-done
The business analyst at Cloud Kicks is using a checklist to assess the quality of user stones for an upcoming Experience Cloud implementation. Which characteristics make a user story successful?
A. Clean Direct, Concise, Cross Functional, Configurable
B. Actionable., Concise, Testable, Solution-oriented, Defined
C. Independent, Negotiable, Valuable, Estimable. Small, Testable
Explanation:
These are the characteristics that make a user story successful, according to the INVEST acronym. A user story should be independent of other user stories, negotiable in terms of scope and details, valuable to the user or customer, estimable in terms of effort and time, small enough to fit in a sprint or iteration, and testable with clear acceptance criteria.
References:
https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories
| Page 2 out of 62 Pages |
| Previous |