Practice Free Certified Business Analyst Exam Online Questions
The business analyst (BA) at Northern Trail Outfitters is writing user stories about a Case creation feature within Service Cloud for an upcoming sprint. This feature overlaps with another feature that
is being developed in the current sprint. The BA is working with the technical team to identify metadata dependencies across features to prevent overwriting before the release.
What should the BA use?
- A . Setup Audit Trail
- B . Change Sets
- C . Version control
Cloud Kicks leadership wants to improve the new customer onboarding experience. There are a number of complex handoffs between teams. Service managers have been tasked with working with the operating team to improve the handoff between salesforce and internal systems. The business (BA) wants to break down the onboarding processing and sub-processes into simpler steps.
What should the BA create to engage stakeholders?
- A . Value Stream Map
- B . Universal Process Notation
- C . Capability Model
A
Explanation:
This answer states that creating a value stream map is what the BA should do to engage stakeholders for improving the new customer onboarding experience at Cloud Kicks which involves complex handoffs between teams. A value stream map is a type of process map that shows how value flows from a customer request to a product or service delivery across different teams or departments. Creating a value stream map means that the BA works with stakeholders from different teams or departments to identify and visualize their inputs, outputs, activities, roles, etc. related to customer onboarding. Creating a value stream map is what the BA should do to engage stakeholders for improving customer onboarding because it helps them to collaborate and communicate their perspectives and expectations, and to discover and eliminate waste or inefficiencies in customer onboarding.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-process-mapping-to-understand-your-business
Universal Containers is developing a new recurring app utilizing Lightning screen flows. The business analyst (BA) has started writing user stores in a repository. The project lead has edited user stories in the DevOps tool to make them more complete.
What should the BA do to understand which user stories were modified?
- A . Review the approval history.
- B . Review the change sets history
- C . Review the version control history.
C
Explanation:
The business analyst should review the version control history to understand which user stories were modified by the project lead. Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. Version control can help track who made what changes, when, and why. It can also help compare different versions, merge changes, resolve conflicts, and restore previous versions. The business analyst should use a version control system to store and manage their user stories in a repository and review the version control history to see the edits made by the project lead. Reviewing the approval history is not a good option because it would only show who approved or rejected the user stories, not who modified them or how. Reviewing the change sets history is not a good option because it would only show what metadata components were deployed or retrieved between orgs, not what user stories were modified or how.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/org-development-model/get-to-know-org-development
Up to how many Profiles can a User have?
- A . Up to 3
- B . The Administrator can have up to 3, normal users only 1.
- C . As many as required.
- D . Only 1
D
Explanation:
A User can have only 1 Profile in Salesforce. A Profile defines the permissions and access settings for a User. A User cannot have multiple Profiles or switch between them. A User can have multiple Permission Sets, which are additional sets of permissions that can be assigned to a User on top of their Profile.
Reference: https://help.salesforce.com/s/articleView?id=sf.users_profiles.htm&type=5
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.
C
Explanation:
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
Business analyst (BA) at Universal Containers looks at the user stories for a new implementation of the for salesforce Customer Data Platform (CDP) and notices they are too large. The BA recommends that the large Dries be broken down into smaller stories which will decrease the future level of effort for subsequent ac.
Which activity will be mast impacted by breaking down the user stories?
- A . Estimation
- B . Defining the persona
- C . Acceptance criteria
C
Explanation:
This answer states that estimation is the activity that will be most impacted by breaking down large user stories into smaller stories for implementing Experience Cloud at Cloud Kicks. Estimation is a process of predicting or calculating how much time, effort, or resources are needed to complete a user story or a task. Breaking down large user stories into smaller stories means that the BA divides a complex or vague user story into more manageable and specific user stories that can be delivered in a shorter time frame. Estimation is the activity that will be most impacted by breaking down large user stories into smaller stories because it helps the BA to reduce uncertainty and risk, increase accuracy and reliability, and facilitate planning and prioritization of user stories or tasks.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements
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.
B
Explanation:
The performance analyzer is a tool that helps business analysts and admins identify and troubleshoot performance issues on record pages. It shows the load time of each component on a record page and provides recommendations to improve performance. The first step to resolve the issue is to use the performance analyzer to view the assessment and identify the slowest components.
Reference:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/optimize-performance
https://help.salesforce.com/s/articleView?id=sf.performance_analyzer.htm&type=5
Universal Containers uses Kanban to complete its Salesforce development. In the middle of a sprint, the sales manager submits an important item to the team.
What should the business analyst do next?
- A . Ask the team to reprioritize the backlog and work on the item at the top.
- B . Ask the team to commit to the work for the next sprint.
- C . Ask the team to pivot and complete the work immediately.
A
Explanation:
The business analyst should ask the team to reprioritize the backlog and work on the item at the top. This is because Kanban is a development model that focuses on continuous delivery and flow of work, rather than fixed iterations or sprints. Kanban uses a visual board that shows the status of work items across different stages, such as backlog, in progress, done, etc. Work items are pulled from one stage to another when there is available capacity or demand, rather than according to a predefined schedule or plan. Reprioritizing the backlog can help the team accommodate the new item and ensure that the most important or urgent work is done first. Asking the team to commit to the work for the next sprint may not be a good option because Kanban does not use sprints or time-boxed iterations. Asking the team to pivot and complete the work immediately may not be a good option because it may disrupt the flow of work or create bottlenecks or waste in Kanban.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/user-acceptance https://trailhead.salesforce.com/en/content/learn/modules/agile-development-with-scrum
Over the past month, a business analyst (BA) has worked with various stakeholders at Cloud Kicks to document requirements for an upcoming Tableau implementation. A stakeholder suggested a revision to the requirements. The BA sent the updated requirements to the stakeholders and they signed off.
Where should the BA track this milestone?
- A . Statement of work
- B . Change log
- C . Sprint plan
A business analyst is gathering requirements for an automation that triggers tasks when an opportunity status changes. The requirement is that the system must alert the finance team when an opportunity is won.
What is an example of a well-written user story in this scenario?
- A . As a finance team member, I need to know when an opportunity is won that 1 can set up a billing
account and update the account number. - B . As an opportunity is won, task must be created for the finance team to set up a billing account and update the account the account number.
- C . As the system, it need to alert the finance team when an opportunity is won so they can set up a billing account and update the account number.
A
Explanation:
This user story follows best practices in user story writing by addressing the "Who, What, and Why": Clear Perspective: The story is written from the perspective of the finance team member, ensuring the user’s role and need are well-defined.
Action and Value: The "what" (setting up a billing account) and "why" (to support the opportunity won) are included, ensuring clarity and alignment with business goals.
Salesforce Guidance: Salesforce recommends framing user stories to reflect specific user needs, making the story actionable and valuable for the development team.