Free Practice Questions for Salesforce Certified-Business-Analyst Exam

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. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

The step of the application lifecycle management (ALM) cycle that requires the business analyst to study current business processes, gather requirements, and analyze them is plan. ALM is a process that helps manage changes to an application from planning to deployment and beyond. ALM has six steps: plan, develop, test, build release, test release, and release. The plan step is where the business analyst studies current business processes, gathers requirements, and analyzes them to understand what needs to be changed or improved in an application. The plan step also involves defining objectives, scope, budget, timeline, deliverables, roles and responsibilities for a project. The develop step is where developers create or modify code or declarative components based on the requirements gathered in the plan step. The test step is where testers verify that the code or declarative components work as expected and meet quality standards using various testing techniques and tools. The build release step is where developers package all code or declarative components into a release that can be deployed to other environments using various deployment techniques and tools. The test release step is where end users test the release in a sandbox or test environment to verify that it works as intended, and what was originally requested is actually being delivered. The release step is where the release is deployed to production and made available to end users. References: https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/understand-what-application-lifecycle-management-is

A functional requirements specification (FRS) is a document that defines what features and functions a system should provide to meet the business needs and objectives. It describes how users will interact with the system and what outcomes they expect from it. An FRS typically includes use cases, user stories, acceptance criteria, data models, business rules, workflows, diagrams, mockups, and other details that describe how the system should work. A BA should create an FRS to define the enhancement features for the current Salesforce CPQ implementation that must be configured in the next phase of the project. References: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-functional-requirements/understand-functional-requirements

This answer states that saving user stories outside of a shared repository is why UC’s development team reports they are unable to confirm which user stories are ready to be built after receiving verbal acceptance of all user stories by the product owner and setting their status to ‘Ready for Development’ on a spreadsheet by UC’s BA. A shared repository is a common or central location where documents or files can be stored, accessed, and updated by multiple users or teams. Saving user stories outside of a shared repository means that the BA stores user stories in a place where they are not visible or available to other users or teams, such as their personal computer, email, etc. Saving user stories outside of a shared repository is why UC’s development team reports they are unable to confirm which user stories are ready to be built because it prevents them from seeing or accessing the latest version or status of user stories, and it creates confusion or inconsistency among them. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

This answer states that scheduling a one-on-one meeting with the new employee to get an alternative perspective from a beginner’s mind is what the BA should do when responding to the new employee’s input. A beginner’s mind is a mindset that is open, curious, and eager to learn, without any preconceptions or biases. A beginner’s mind can help the BA to discover new insights, ideas, or opportunities that might otherwise be overlooked or dismissed by more experienced or knowledgeable stakeholders. Scheduling a one-on-one meeting with the new employee can help the BA to listen to their input, understand their perspective, and appreciate their contribution. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

This answer states that violating the definition of done is the principle of Agile methodology that this situation violates for completing UAT of a solution at Universal Containers. Agile methodology is an approach to software development that emphasizes delivering value to customers in short iterations or sprints, and responding to changing requirements with flexibility and collaboration. Definition of done is a criterion or a checklist that specifies when a user story or a task is considered complete and ready for deployment or delivery. Violating the definition of done means that the BA accepts a user story or a task as done without ensuring that it meets all the quality standards or acceptance criteria agreed upon by the project team. References: https://trailhead.salesforce.com/en/content/learn/modules/agile-basics/agile-basics-done

The best practice for handling an urgent, high-priority change request in Scrum is to add it to the prioritized backlog for the next sprint. This way, the change request can be reviewed by the product owner and estimated by the development team before being added to a sprint. Adding a change request to an ongoing sprint would disrupt the planned scope and schedule of work.

This answer states that partners and customers are external stakeholders that should assist with determining project priorities for developing a new inventory forecasting application available on its Experience Cloud site at UC. Partners are external entities or organizations that have a business relationship or an agreement with UC, such as suppliers, distributors, resellers, etc. Customers are external entities or organizations that purchase or use UC’s products or services. Partners and customers are external stakeholders that should assist with determining project priorities for developing a new inventory forecasting application because they have an interest or an influence on UC’s business performance and outcomes, and they can provide valuable feedback or insights on UC’s inventory forecasting needs and expectations. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

This answer suggests adjusting the goal of the user story to be independent as a way to improve this user story for updating its customer portal built on Experience Cloud. The goal of a user story is what the user or stakeholder wants to accomplish, why they want to accomplish it, and how they will measure success. The goal of a user story should be independent, meaning that it does not depend on or overlap with other user stories. This user story has a goal that is too broad and complex, as it includes multiple features or functionalities (chat with a support agent, view account, see orders, ask questions) in one user story. Adjusting the goal of the user story to be independent can help to break down this user story into smaller and simpler user stories that can be completed in one sprint. References: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements