Salesforce Certified Business Analyst (BA-201) Exam Practice Test

Answer : C

The level influence that business analyst should place HR Director stakeholder wheel project stakeholder wheel tool identifies understands needs expectations interests influence power stakeholders involved project stakeholder wheel has four levels influence sponsor project enterprise environment sponsor highest level influence project second highest level influence enterprise third highest level influence environment lowest level influence HR Director should placed project level influence stakeholder wheel HR Director makes decisions determines priorities requirements project HR Director also directly affected outcome project.

The sponsor is not level influence that business analyst should place HR Director stakeholder wheel sponsor highest level influence stakeholder wheel sponsor provides funding resources support project sponsor also defines vision objectives success criteria project HR Director not sponsor project unless also provides funding resources support project.

The enterprise is not level influence that business analyst should place HR Director stakeholder wheel enterprise third highest level influence stakeholder wheel enterprise includes internal individuals teams groups affected outcome project but not actively contribute project enterprise also includes policies procedures standards guidelines govern project HR Director not enterprise unless also affected outcome project but not actively contribute project.

Answer : B

The best practice for managing requested changes to the original requirements is to use a change request log and user stories. A change request log is a document that tracks and records any changes that are requested by stakeholders or identified by the project team during the project lifecycle. A user story is a concise statement that describes what a user wants to do and why they want to do it in Salesforce. The BA should update the change request log with the details of the requested change, such as the description, source, priority, impact, status, and approval. The BA should also draft a new user story that captures the requested change in terms of who, what, and why, and add it to the backlog for prioritization and development. Reference: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-change-management/manage-change-requests https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write-user-stories

Answer : A

This answer states that documenting user requirements from each department during discovery sessions is what the BA should do to get buy-in from users for preparing for a new Sales Cloud implementation for 6,000 users at CK. User requirements are the needs, expectations, and objectives of the users for the Sales Cloud implementation. Discovery sessions are meetings or workshops where the BA gathers and clarifies user requirements from different stakeholders. Documenting user requirements from each department during discovery sessions means that the BA records and organizes the information obtained from different stakeholders from different departments, such as manufacturing and delivery, in a clear and concise way. Documenting user requirements from each department during discovery sessions is what the BA should do to get buy-in from users for preparing for a new Sales Cloud implementation because it helps the BA to understand and validate the user requirements, and to communicate and align them with the project scope and goals. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

Answer : C

This answer states that using a DevOps tool can help to track changes in real time and provide a single source of truth as the benefits of using a DevOps tool in this situation where the requirements tracking spreadsheet is often incomplete or out-of-sync for the Slack transition project. A DevOps tool is a software application that supports the collaboration and automation of development and operations teams, such as Git, Jira, or Azure DevOps. A DevOps tool can help to track changes in real time by synchronizing the code changes, user stories, tasks, and bugs across different environments and branches. A DevOps tool can also help to provide a single source of truth by storing and managing all the project artifacts, such as requirements, code, tests, and documentation, in one centralized location that is accessible and visible to all project team members. Reference: https://trailhead.salesforce.com/en/content/learn/modules/git-and-git-hub-basics/work-with-teams

Answer : C

The type of analysis that the BA should recommend to ensure the implementation team avoids this challenge on the current project is stakeholder analysis. Stakeholder analysis is a technique that helps to identify and understand the people who are affected by or involved in a project, and their needs, expectations, interests, influence, and attitudes towards the project. Stakeholder analysis helps to avoid missing or overlooking important stakeholders, and to plan appropriate communication and engagement strategies for each stakeholder group. The other options are either irrelevant or insufficient. Option A does not address the challenge of identifying and understanding stakeholders, but rather their behaviors and preferences. Option B does not address the challenge of identifying and understanding stakeholders, but rather their organizational context and environment. Reference: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-stakeholder-management/identify-stakeholders

Answer : C

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. Reference: https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories

Answer : A

One of the benefits of ALM that the BA should share with the stakeholder is that ALM provides processes and policies which help build apps more efficiently. ALM is a framework that defines and manages the stages and activities involved in developing, testing, deploying, and maintaining software applications. ALM helps to:

Build apps more efficiently: ALM helps to streamline and standardize the development process, reduce errors and rework, improve collaboration and communication among team members and stakeholders, and ensure quality and consistency of the applications.

Align with business goals and needs: ALM helps to ensure that the applications meet the requirements and expectations of the users and stakeholders, deliver value and benefits to the business, and support the business strategy and objectives.

Adapt to changes and challenges: ALM helps to enable continuous feedback and improvement, incorporate new features and functionalities, address issues and risks, and leverage new technologies and innovations. The other options are either incorrect or irrelevant. Option B is incorrect because ALM does not offer preview access to the three Salesforce releases per year, but rather requires maintenance exams or modules to keep up with the releases. Option C is incorrect because ALM does not allow features to remain static and reduce incremental changes, but rather encourages iterative and agile development that embraces changes and enhancements. Reference: https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/understand-the-application-lifecycle