Salesforce Certified Business Analyst Practice Test - Questions Answers, Page 18

This answer states that using Salesforce terminology and language is what the BA should recommend to the project team to increase understanding when documenting requirements, process and potential solutions for reviewing the existing Salesforce manufacturing solution that has low adoption and a variety of customization including custom objects, custom fields, renamed standard fields. Salesforce terminology and language are the words and phrases that are commonly used in the Salesforce ecosystem, such as objects, fields, records, apps, tabs, profiles, roles, etc. Using Salesforce terminology and language can help the BA to communicate and document the requirements, process and potential solutions in a consistent and accurate way, and avoid confusion or misunderstanding among the project team members who are familiar with Salesforce.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

Universal Process Notation (UPN) is a method to show current state business flows in Salesforce. UPN is a process modeling technique that shows the flow of activities and decisions using simple symbols and plain language. It can help document existing processes in a clear and concise way that can be easily understood by anyone involved in the project. Entity Relationship Diagramming (ERD) is not a method to show current state business flows in Salesforce. ERD is a data modeling technique that shows the relationships among entities using symbols and attributes. It can help design database schemas or data structures for an application. Storyboarding is not a method to show current state business flows in Salesforce. Storyboarding is a technique to help stakeholders visualize how a solution will work by creating sketches or mockups of the user interface and interactions.It can help elicit feedback and validate requirements for a proposed solution.

Reference:1https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/business-process-mapping

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.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

The business analyst should focus on scheduling an all-day collaboration workshop with both teams to resolve their differences around contact management for a new Salesforce implementation. A collaboration workshop is a technique to bring together different stakeholders to share information, discuss issues, generate ideas, make decisions, or reach consensus on a topic or problem. Scheduling an all-day collaboration workshop with both teams can help identify their needs, expectations, pain points, goals, and priorities around contact management and find common ground or alignment among them.Mapping historical lead data from each team and building charts to highlight similarities is not a good option because it would not address the disconnect between the sales and marketing teams' definition of a qualified lead, which is related to contact management, not lead management. Evaluating team' skill and experience to determine how they can better align is not a good option because it would not address the disconnect between the sales and marketing teams' definition of a qualified lead, which is related to contact management, not skill or experience.

Reference:1https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/collaborate-with-stakeholders

The business analyst should log a defect for the page layout change and discuss it with the DevOps team to address the issue of one of the minor changes to the Account page layout for the project being missing. A defect is an error or flaw in an application that causes it to deviate from its expected behavior or result. Logging a defect for the page layout change can help document the issue, its impact, and its priority, and assign it to someone responsible for fixing it. Discussing it with the DevOps team can help understand why the change was missing, how it can be resolved, and when it can be deployed. Making the page layout change directly in UAT so the client can begin testing is not a good option because it would bypass the development process, create inconsistency among environments, and introduce potential risks or errors. Asking the project manager to reschedule UAT until after the defect is resolved is not a good option because it would delay the testing schedule, impact the project timeline, and reduce customer satisfaction.

Reference:1https://trailhead.salesforce.com/en/content/learn/modules/user-acceptance-testing-video/learn-about-user-acceptance-testing

Kanban is an agile methodology that focuses on visualizing work, limiting work in progress, managing flow, making policies explicit, implementing feedback loops, improving collaboratively, evolving experimentally (Kaizen). Kanban is suitable for scenarios where work is generally project-based and can be broken into smaller pieces that can be completed quickly and independently by different team members without dependencies or bottlenecks. Kanban uses boards with columns representing different stages of work (such as backlog, doing, done) and cards representing individual work items (such as tasks, features, bugs). Kanban helps teams monitor their progress, identify issues, prioritize work, optimize resources, improve quality, reduce waste, increase efficiency, deliver value faster, adapt to changing needs, etc.

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

The mistake that the business analyst made when writing this user story was that the story included feature-specific language rather than focusing on what needs to be achieved by implementing this feature or functionality. For example, specifying that ''a customer service representative wants to use Salesforce Macros'' implies a particular design choice rather than describing what outcome should be achieved by reducing the time spent on each case (such as automating repetitive tasks or streamlining workflows). User stories should be aligned with the user's goal rather than prescribing how to achieve it so that they do not limit creativity or innovation in finding solutions. User stories should also be small and testable so that they can be easily verified by using techniques such as scenarios or test cases. The incorrect persona was not used in the story because customer service representative is a valid user role or persona who will benefit from this feature or functionality. The story explained the value to the user rather than focusing on what needs to be achieved by implementing this feature or functionality because reducing the time spent on each case is a benefit or value that the customer service representative will get from this feature or functionality.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/user-stories

The business analyst should use the metadata coverage report to determine which changes must be made manually in each environment. The metadata coverage report is a tool that shows which metadata types and components are supported in different development models and tools, such as change sets, Metadata API, Salesforce CLI, etc. The business analyst should use the metadata coverage report to identify which changes can be deployed automatically using declarative change sets and which changes must be made manually using other tools or methods. The object schema builder is not a resource to determine which changes must be made manually in each environment. The object schema builder is a tool that lets you create and modify custom objects and fields using a graphical interface. It does not show which metadata types and components are supported in different development models and tools. The setup audit trail is not a resource to determine which changes must be made manually in each environment. The setup audit trail is a tool that tracks the recent setup changes that you and other admins have made to your org. It does not show which metadata types and components are supported in different development models and tools.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/understand-what-application-lifecycle-management-is