Salesforce CERTIFIED-BUSINESS-ANALYST Online Practice Questions and Exam Preparation

Salesforce CERTIFIED-BUSINESS-ANALYST Online Questions & Answers

• Question 301:

  A business analyst (BA) at Universal Containers (UC) has been asked to evaluate a business process at a high level and in detail, while also keeping regulatory considerations in mind. Management wants to use the output from the BA's evaluation to inform decisions about UC's future implementations of Sales Cloud and Service Cloud.

  What should the BA use for their evaluation?

  A. Cross-functional flowchart
  B. Entity Relationship Diagram (ERD)
  C. Universal Process Notation (UPN)
  C. Universal Process Notation (UPN)

  ---

  Explanation

  This answer selects Universal Process Notation (UPN) as the tool that the BA should use for their evaluation of a business process at UC. UPN is a simple and standardized way of creating process maps, using only four symbols: activity,

  decision, start/end, and annotation. UPN can help the BA evaluate a business process at a high level and in detail, while also keeping regulatory considerations in mind, by showing the steps, actions, decisions, roles, and dependencies of the

  process, and adding notes or comments to explain or clarify certain aspects.

  References:

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

• Question 302:

  A business analyst (BA) is facilitating a workshop to refine user stories for a new feature. Which of the following should the BA focus on during the workshop?

  A. Ensuring user stories are small, testable, and valuable
  B. Creating a detailed technical design
  C. Determining deployment schedules
  D. Writing acceptance tests
  A. Ensuring user stories are small, testable, and valuable

  ---

  Explanation

• Question 303:

  The business analyst (BA) at Universal Containers is meeting with business leaders to elicit and document functional requirements specifications related to its new Salesforce implementation. The BA will also document the functionality this system should provide so it can be developed into a work item.

  What is the name of this documentation type?

  A. Business analysis plan
  B. Use case
  C. User story
  A. Business analysis plan

  ---

  Explanation

  A user story is a type of documentation that describes what functionality a system should provide from a user's perspective. It is written in simple language that anyone can understand and follows a standard format of "As a [user role], I want [functionality], so that [benefit]". A user story helps to capture the user's needs and expectations from the system and provides a basis for developing test cases and acceptance criteria. A BA should use user stories to document the functionality that a system should provide so it can be developed into a work item.

  References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write-user-stories

• Question 304:

  During a sprint grooming session for the Sales Cloud implementation at Cloud Kicks, the development team mentions the step "Code Review by Technical Architect" listed within the acceptance criteria needs to be adjusted.

  Which location should the business analyst move this item to?

  A. Project plan
  B. Definition of done
  C. Pull request template
  B. Definition of done

  ---

  Explanation

  The business analyst should move this item to the definition of done. The definition of done is a set of criteria that must be met before a user story or sprint can be considered complete or ready for release. The definition of done helps to ensure quality, consistency, and transparency across the project team. The step "Code Review by Technical Architect" is not part of the acceptance criteria for a specific user story, but rather a general requirement that applies to all user stories or sprints.

  References: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/write-user-stories

• Question 305:

  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. Review the version control history.

  ---

  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.

  References: https://trailhead.salesforce.com/en/content/learn/modules/org-development-model/get-to-know-org-development

• Question 306:

  Universal Containers (UC) is wording with an implementation partner to help it optimize Salesforce. A new business analyst (BA) from the partner was introduced to UC stakeholders a few weeks into the project The BA is getting to know each of the stakeholders by their roles and contributions. However, the BA had one misstep and is slightly embarrassed.

  What should the BA do to build trust with the stakeholders?

  A. Be vulnerable and own their mistake.
  B. Promise to work harder to avoid other mistakes.
  C. Ask their supervisor for help immediately.
  A. Be vulnerable and own their mistake.

  ---

  Explanation

  The best way for a business analyst to build trust with stakeholders after making a mistake is to be vulnerable and own their mistake. This will show honesty, humility, accountability, and willingness to learn from errors. Promising to work harder to avoid other mistakes may sound defensive or unrealistic without acknowledging what went wrong or how to fix it. Asking their supervisor for help immediately may seem desperate or unprofessional without trying to resolve it first with stakeholders.

  References: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/collaboration-with-stakeholders

• Question 307:

  The business analyst (BA) at Northern Trail Outfitters is helping to improve the process for handling customer returns using Salesforce. The BA has completed a current state process map to identify areas for improvement. The BA plans to present ideas for a future state return handling process to the larger project team.

  What should the BA present to the team in a way that is relatable and invites discussion, feedback, and ideas?

  A. A prototype for a specific business outcome
  B. Detailed technical documentation with annotations
  C. A story using personas to illustrate potential solutions
  C. A story using personas to illustrate potential solutions

  ---

  Explanation

• Question 308:

  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
  C. Version control

  ---

  Explanation

• Question 309:

  The business analyst (BA) at Universal Containers is preparing for user acceptance testing (UAT) for an Experience Cloud implementation.

  Which people should participate in UAT?

  A. Business users, project manager, key stakeholders
  B. BA, project manager, key stakeholders
  C. BA, business users, key stakeholders
  A. Business users, project manager, key stakeholders

  ---

  Explanation

  This answer states that business users, project manager, and key stakeholders are the people who should participate in UAT for an Experience Cloud implementation. UAT is a phase of testing where the BA verifies that the solution meets the requirements and expectations of the end users or customers. Business users are the people who will use or benefit from the solution on a regular basis, and who can provide feedback on its functionality, usability, and value. Project manager is the person who oversees and coordinates the project activities, resources, and deliverables, and who can ensure that UAT is conducted according to the project plan and scope. Key stakeholders are the people who have a significant interest or influence in the project outcome, and who can approve or reject the solution based on UAT results

• Question 310:

  Cloud Kicks has assembled a new product team to launch a brand ambassador partner portal in Experience Cloud. The team is debating various ways to document the requirements. The business analyst recommends writing user stories within the Agile methodology.

  What is the benefit of creating user stories when documenting project requirements?

  A. User stories provide specific details about a product early in the development lifecycle.
  B. User stones decrease the need for collaboration within a product team throughout the project.
  C. User stones translate requirements in a way that shows a product's value to the end user.
  C. User stones translate requirements in a way that shows a product's value to the end user.

  ---

  Explanation

  User stories are short descriptions of a feature or functionality from the perspective of an end user. They follow the format "As a , I want , so that ". The who is the user role or persona who will benefit from the feature or functionality. The what is the feature or functionality that the user wants or needs. The why is the benefit or value that the user will get from the feature or functionality. User stories help translate requirements in a way that shows a product's value to the end user and helps prioritize and validate them. User stories do not provide specific details about a product early in the development lifecycle because they are usually high-level and flexible. User stories do not decrease the need for collaboration within a product team throughout the project because they require constant communication and feedback among stakeholders, developers, and testers.

  References: 1 https://parquet.dev/a-guide-to-salesforce-useracceptance-testing/