Free CERTIFIED-BUSINESS-ANALYST Exam Dumps Preview

A challenge is an element of the storytelling process for UX that describes a hurdle that makes it difficult for your heroes to succeed on their journeys. A monster is an element of the storytelling process for UX that describes a person or thing that causes problems for your heroes. A victory is an element of the storytelling process for UX that describes a successful outcome for your heroes. A helper is an element of the storytelling process for UX that describes a person or thing that assists your heroes along their journeys.
References:
https://trailhead.salesforce.com/content/learn/modules/ux-design-fundamentals/
understand-the-storytelling-process

When faced with budgetary constraints, re-prioritizing requirements ensures alignment with available resources: Budget Optimization: Re-prioritizing allows the team to focus on delivering high-value features while deferring less critical requirements. Role Collaboration: Salesforce recommends close collaboration
between the BA and project manager to adjust project scope and maintain alignment with business goals.
Stakeholder Alignment: This approach ensures transparency with stakeholders about changes in project focus due to budgetary constraints.

The business analyst should seek sign-offs from the business for the functional requirements, individual test case functionality, and final go live date. The functional requirements are the statements that describe what the solution must do or provide to meet user needs or business objectives. The individual test case functionality is the verification that each test case meets the acceptance criteria for the corresponding user story or requirement. The final go live date is the date when the solution will be released to production and available for users or customers. These sign-offs help to ensure that the solution is complete, satisfactory, and ready for launch.

The business analyst should set up a casual meeting to create a personal connection with the stakeholder to build trust with them as the project continues. A casual meeting is an informal conversation that allows the business analyst and the stakeholder to get to know each other better, share their backgrounds and interests, and establish rapport and empathy. A casual meeting can help to ease any tension or frustration that may have arisen during the discovery session, as well as show respect and appreciation for the stakeholder's input and feedback.
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/
stakeholder-management

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.
References:
https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/
understand-the-application-lifecycle

The primary value of the business analyst (BA) speaking with customer service reps during the discovery for a new Service Cloud implementation is validating current processes. Customer service reps are the end users of Service Cloud and they can provide valuable insights into how they perform their tasks, what challenges they face, and what expectations they have from the new system. The BA can use this information to validate or update the current process maps and identify areas for improvement. Estimating the project cost is not a value of speaking with customer service reps, as this is usually done by project managers or sponsors based on resource allocation and budget constraints. Building solution design consensus is not a value of speaking with customer service reps, as this is usually done by solution architects or developers based on technical feasibility and best practices.
References:
https://trailhead.salesforce.com/content/learn/modules/business-analysis-for-salesforce-projects/
understand-the-salesforce-implementation-lifecycle (https://trailhead.salesforce.com/content/learn/modules/business-analysis-for-salesforce-projects/analyze-business-processes-and-requirements)

This answer states that using standard naming conventions is the best practice that the BA should train the employee on for sending a document named UserStories_v37_final_final_final.docx. A standard naming convention is a set of rules or guidelines that define how to name or label a document or a file in a consistent and meaningful way. A standard naming convention typically includes elements such as project name, document type, version number, date, author, etc. Using standard naming conventions is the best practice that the BA should train the employee on for sending a document because it helps the BA to organize and manage documents or files more efficiently and effectively, and to avoid confusion or
duplication among them.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

The type of research that the business analyst should use to elicit user stories from UC's customers is interviewing. Interviewing is a technique that involves asking open-ended questions to stakeholders or users to gather information and feedback about their needs, expectations, preferences, pain points, goals, etc. Interviewing helps to elicit user stories from UC's customers by allowing them to express their opinions and experiences in their own words, as well as clarifying any doubts or ambiguities. Interviewing also helps to build rapport and trust with the customers and show them respect and appreciation for their input.
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/
customer-discovery

A capability model is a high-level representation of what a business does or needs to do in order to achieve its goals and objectives. A capability model can help a business analyst review the key process areas that were used for NA team with APAC team so they can scope their priorities for overall business improvement. A capability model can also help identify gaps or overlaps between different regions or teams.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/
create-a-capability-model (https://www.bain.com/insights/management-tools-capability-sourcing/)

Identity Only is the Salesforce standard license that can be given to someone who need access only identity services, such as single sign-on (SSO). Lightning Platform, SSO License, and Salesforce License are not valid standard licenses in Salesforce.
References:
https://help.salesforce.com/s/articleView?id=sf.users_license_types_available.htm&type=5

Proactively engaging the sales team is crucial for gathering a comprehensive set of requirements: Ensuring Inclusivity: All functional teams must provide input for a successful CRM merger. Salesforce encourages proactive engagement with less responsive stakeholders to ensure all perspectives are considered. Addressing Resistance: Direct follow-ups allow the BA to uncover reasons for disengagement and address them effectively.
Balanced Requirements Gathering: This approach prevents an imbalance in requirements that may lead to solutions favoring one team over another.

The goal of user acceptance testing (UAT) is to ensure what was originally requested is being delivered by the development team. UAT is the final phase of testing before a solution is released to production. UAT involves users or stakeholders who validate that the solution meets their needs and expectations, based on the user stories and acceptance criteria. UAT helps to verify that the solution is fit for purpose and ready for launch.
References:
https://trailhead.salesforce.com/content/learn/modules/user-story-creation/user-acceptance-testing

For a project like developing a new inventory forecasting application on an Experience Cloud site, identifying key external stakeholders is critical for ensuring that the solution meets the end-users' needs.
Buyers and customers are the primary users of such a platform and are directly impacted by its functionality and performance. Involving them in determining project priorities helps to align the development efforts with the actual market demand and user expectations, leading to a more successful and user-centric solution.

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.

The user story that most accurately represents the goal is B. As a site administrator of the CK website, I want to make sure that the web server can process requests at 150% of the average traffic rate during the latest promotion. This user story clearly defines who (site administrator), what (make sure that the web server can process requests), why (during the latest promotion), and how (at 150% of the average traffic rate). This user story also aligns with the goal of performing stress testing for an upcoming promotion, which is a type of testing that evaluates how a system performs under extreme load or demand. The other options are either inaccurate or incomplete.
Option A is inaccurate because it does not represent the goal of stress testing, but rather the goal of usability testing, which is a type of testing that evaluates how easy and intuitive a system is to use.
Option C is incomplete because it does not specify how (at what rate or level) to make sure that shoppers can complete their purchases without disruption.
References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write-user-stories

The elicitation technique that the business analyst should use to gather information about the steps a user takes to accomplish a goal, challenges a user faces, people the user interacts with, applications they use to complete the steps, and their level of morale as they move through the process is journey mapping.
Journey mapping is a technique that creates a visual representation of a user's experience with a product or service over time. It can help the business analyst understand how a user interacts with a product or service across different touchpoints or stages, what pain points or obstacles they encounter, what emotions or feelings they have, etc. Survey/Questionnaire is an elicitation technique that collects quantitative or qualitative data from a large number of stakeholders using predefined questions or scales. It can help the business analyst measure stakeholder satisfaction, preferences, or feedback, but not capture the details or nuances of their experience.

The type of session that the business analyst should perform to elicit user stories from UC's customers is journey mapping. Journey mapping is a technique that involves creating a visual representation of the steps or stages that a customer goes through when interacting with an organization, product, or service.
Journey mapping helps to capture the customer's experience, needs, goals, pain points, emotions, and touchpoints across their entire lifecycle. Journey mapping also helps to identify any gaps or opportunities for improvement or innovation in the customer journey. Journey mapping can help elicit user stories from UC's customers by allowing them to share their perspectives and feedback in their own words, as well as showing how the solution can add value and benefits to their journey.
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/
customer-discovery

When addressing issues reported by users following a Salesforce implementation, the business analyst's primary responsibility is to understand and analyze the problem comprehensively before taking any corrective action. Gathering Requirements: This step involves communicating directly with the end users to identify their issues and expectations. This ensures that the analyst has a clear understanding of the problem's root cause.
References:
Salesforce Business Analysis documentation emphasizes requirements
elicitation and validation as critical first steps in identifying misalignments or implementation gaps. Avoiding Premature Actions: Jumping to training or creating a high-priority bug may address symptoms rather than the actual problem. Salesforce implementation guides and best practices stress the importance of first understanding the user experience and system functionality through direct feedback. Stakeholder Engagement: Engaging stakeholders and users is a critical phase outlined in Salesforce's business analysis processes.
It ensures that the problem definition aligns with the users' needs and organizational objectives. Follow-Up
Steps: Once requirements are gathered, the next steps involve validating and analyzing the data, and based on findings, proposing appropriate solutions such as additional training, system adjustments, or bug fixes. Salesforce Business Analyst responsibilities include continuous alignment of implemented solutions with business needs.
This approach aligns with Salesforce's process-driven methodology for ensuring successful system adoption and user satisfaction.

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.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

When a business analyst discovers that different teams have different needs or preferences for using Salesforce fields, they should refine the requirements to accommodate both teams. This is because deleting fields that are actively used by another team could cause data loss, errors, or inefficiencies in their processes. The business analyst should work with both teams to understand their use cases, data models, workflows, reports, dashboards, integrations, security settings, etc., and find ways to customize Salesforce fields that meet both teams' needs without compromising data quality or performance.
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/
requirements

The Manage Sandbox permission is required to create, delete, refresh or activate a Sandbox. Sandbox Editor, Environment Manager, and System Administrator are not valid permissions in Salesforce.
References:
https://help.salesforce.com/s/articleView?id=sf.data_sandbox_manage.htm&type=5

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

This answer states that circulating the requirements to stakeholders, incorporating feedback, and obtaining sign-off is what the BA should do to ensure alignment on goals and strategies across NTO's organization for creating an engaging site for its customers using Experience Cloud. Circulating the requirements to stakeholders means that the BA shares the written statements that describe what the solution must do or have to meet the goals and strategies of NTO's organization with the people who have a significant interest or influence in the project outcome. Incorporating feedback means that the BA revises and updates the requirements based on the comments or suggestions from the stakeholders. Obtaining sign-off means that the BA gets a formal approval or confirmation from the stakeholders that they agree with and accept the requirements.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

The business analyst should write test scripts that reflect real life and cover the requirements to help prevent gaps from being discovered after go live. Test scripts are step-by-step instructions on how to execute a test scenario on a specific user or level of access using expected inputs and outputs. Test scripts should reflect real life situations that users may encounter when using the solution in production, such as creating cases, updating records, generating reports, etc. Test scripts should also cover all the requirements that were defined for the project or enhancement, as well as any exceptions or variations that may occur. Writing test scripts that reflect real life and cover the requirements can help ensure that the solution works as intended and meets stakeholder needs.
References:
https://trailhead.salesforce.com/content/learn/modules/user-acceptance-testing-video/create-test-scripts

Facilitating workshops is the best way to guide conversations and identify meaningful process improvements: Stakeholder Engagement: Workshops bring together diverse perspectives, enabling stakeholders to share insights and prioritize issues based on their impact and feasibility. Interactive Problem-Solving: Salesforce's business analysis methodology recommends workshops as an effective way to identify root causes and collaboratively develop solutions. Prioritization: The collaborative format helps stakeholders focus on key pain points and align on process improvements that deliver the most significant value.

This answer states that asking for specific examples to review is how the BA should respond to feedback from UC's project manager who tells the BA that the developers on the team are having trouble understanding what to build because the acceptance criteria for the Sales Cloud user stories are confusing. Asking for specific examples to review means that the BA requests the project manager or the developers to provide concrete instances or scenarios of where and how the acceptance criteria for the Sales Cloud user stories are confusing, such as ambiguous, inconsistent, or incomplete acceptance criteria. Asking for specific examples to review is how the BA should respond to feedback from UC's project manager because it helps the BA to clarify and verify the feedback, and to revise and update the
acceptance criteria accordingly.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills

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.
References:
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

The approach that the business analyst should take to begin this process is to schedule a meeting with stakeholders and create a journey map. A journey map is a tool that creates a visual representation of the steps or stages that a user goes through when interacting with a system or solution. A journey map helps to understand and document the user's experience, needs, goals, pain points, emotions, and touchpoints across their entire lifecycle. A journey map also helps to identify any gaps or opportunities for improvement or innovation in the user journey. The business analyst should schedule a meeting with stakeholders and create a journey map by asking questions, collecting feedback, drawing diagrams, and validating information. Scheduling a meeting with stakeholders and creating a journey map helps to begin this process by engaging and involving them in defining and designing the new client onboarding process.
References:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/
customer-discovery

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.
References:
1 (https://trailhead.salesforce.com/en/content/learn/modules/user-acceptance-testing-video/)
learn-about-user-acceptance-testing

A full copy sandbox is a copy of a production environment that includes all data and metadata. It is suitable for user testing because it provides a realistic and isolated environment where users can test changes without affecting live data or users. Power users are users who have extensive knowledge and experience with the business domain and processes. They can provide valuable feedback and insights on whether the solution meets their expectations and requirements. A scratch org is a temporary and lightweight environment that is suitable for development and testing of code-based changes, but not for user testing of declarative changes. A partial sandbox is a copy of a production environment that includes some data and all metadata. It is suitable for quality assurance testing, but not for user testing because it may not have enough data to cover all scenarios.
References:
1 (https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/understand-what-application-lifecycle-management-is)

The missing component necessary to finish this user story is why because it describes the benefit or value that sales reps will get from having visibility into their pipeline revenue (such as forecasting sales performance or identifying opportunities). The who part of this user story is "sales reps" because it describes the user role or persona who will benefit from this feature or functionality. The what part of this user story is "visibility into sales rep' pipeline" because it describes the feature or functionality that sales reps want or need.

The information that the business analyst should gather during the initial discovery meeting is the limitations of the current support process. The initial discovery meeting is a meeting where the business analyst meets with the key stakeholders and sponsors of a project to understand their needs, expectations, goals, challenges, and pain points. The business analyst should gather information about the limitations of the current support process to identify the gaps, issues, or opportunities for improvement that the project aims to address. The business analyst should also gather information about the scope, budget, timeline, deliverables, roles and responsibilities, and success criteria for the project. The employee review cycle for the support team is not information that the business analyst should gather during the initial discovery meeting. The employee review cycle is a process that evaluates the performance and development of employees on a regular basis. It is not relevant to the project scope or objectives and does not help identify the limitations of the current support process. The contact information for key stakeholders is not information that the business analyst should gather during the initial discovery meeting. The contact information for key stakeholders is a detail that can be obtained before or after the meeting, but it does not help understand the needs or expectations of the stakeholders or the limitations of the current support process.
References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analyst_skills-strategies/explore-techniquesnformation-discovery

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

The business analyst should gather testing requirements from the stakeholder to address the need for user acceptance testing (UAT) for a particular story involving an update to an important trigger. UAT is end-user testing performed in a sandbox or test environment to verify that a project or enhancement works as intended and what was originally requested is actually being delivered. The business analyst should gather testing requirements from the stakeholder to understand what scenarios or cases need to be tested, what data or inputs need to be used, what outputs or results need to be expected, and what criteria or metrics need to be measured. The business analyst should also document and communicate these testing requirements to the testers and developers involved in UAT. Running all Apex tests using change set validation is not an action that the business analyst should take to address the need for UAT for a particular story involving an update to an important trigger. Running all Apex tests using change set validation is a process that checks whether deploying a change set would succeed or fail in another org without actually deploying it. Running all Apex tests using change set validation helps ensure code quality and coverage but does not verify whether a project or enhancement meets user needs or expectations.
Performing testing on all objects in the trigger is not an action that the business analyst should take to address the need for UAT for a particular story involving an update to an important trigger. Performing testing on all objects in the trigger is a process that checks whether the trigger works correctly and consistently for all objects that it affects. Performing testing on all objects in the trigger helps ensure functionality and performance but does not verify whether a project or enhancement meets user needs or expectations.
References:
https://trailhead.salesforce.com/en/content/learn/modules/user-acceptance-testing-video/learn-about-user-acceptance-testing

The best tool for identifying the key recruitment steps and stakeholders in a visual format is to map the business process. Business process mapping is a technique that helps to create a visual representation of a business process. It shows the steps, inputs, outputs, roles, and decisions involved in the process.
Business process mapping helps to understand the current state of the process, identify areas for improvement, and design the future state of the process. A BA should use business process mapping to identify the key recruitment steps and stakeholders for the Salesforce application.
References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process-mapping/understand-process-mapping

The next thing that the business analyst should do after reviewing the details of the failed test case is to attempt to reproduce the issue. Reproducing an issue means following the same steps or actions that caused the issue to occur in order to verify its existence and severity. Reproducing an issue helps to confirm whether it is a real bug or a human error, as well as gather more information about its root cause, impact, frequency, etc. Reproducing an issue also helps to document it clearly and accurately for reporting and resolution purposes.
References:
https://trailhead.salesforce.com/content/learn/modules/user-acceptance-testing-video/report-and-resolve-issues

The best practice for identifying which stage in the sales process the industry standard due-diligence should be embedded is to develop a process map as a base, work with stakeholders to understand the trigger point, and locate the stage.
This practice helps
to:
Develop a process map as a base: This provides a visual representation of the sales process, showing the steps, inputs, outputs, roles, and decisions involved in each stage. Work with stakeholders to understand the trigger point: This helps to elicit feedback and insights from the stakeholders who are familiar with or affected by the sales process, and identify when or why the industry standard due-diligence is needed or required.
Locate the stage: This helps to determine where in the sales process the industry standard due-diligence should be embedded, based on the trigger point and the business logic.
References:
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process-mapping/create-a-process-map

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.
References:
1 (https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/)
business-process-mapping

This answer suggests acknowledging the feedback, creating a new user story that includes the field changes, and asking the stakeholder to update the existing test case to show it was successfully tested as the next step for the BA after receiving this feedback from a stakeholder during user acceptance testing for a global customer service project that leverages Service Cloud. Acknowledging the feedback shows respect and appreciation for the stakeholder's input and involvement. Creating a new user story that includes the field changes helps to capture and prioritize the new requirements, and avoid scope creep or impact on other user stories. Asking the stakeholder to update the existing test case to show it was successfully tested helps to validate and document that the functionality described in the test case is working as expected.
References:
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements