Home › Business Analyst › Collaboration with Stakeholders

Business Analyst practice questions: Collaboration with Stakeholders

Collaboration with Stakeholders is 24% of the Salesforce Certified Business Analyst exam. It covers stakeholder maps, RACI, communication and escalation. Try these 9 free questions, then open each answer to see why every option is right or wrong.

Ahead of a Service Cloud rollout at an outdoor gear company, the business analyst must find out why support agents average 14 minutes per case resolution, almost twice the industry benchmark. Which elicitation technique should the BA apply FIRST to uncover the root cause?

Survey every customer service agent and ask them to rank their biggest pain points.
Run a JAD workshop with the customer service manager and the IT team to design the desired future state.
Shadow individual agents while they resolve live cases to see how they actually work.
Read the current case management documentation and standard operating procedures.

Show answer

Answer: C

A. Survey every customer service agent and ask them to rank their biggest pain points.Incorrect. Surveys reach many people but lack the depth to reveal the step-by-step causes of a particular inefficiency.

B. Run a JAD workshop with the customer service manager and the IT team to design the desired future state.Incorrect. JAD focuses on designing the future state; jumping there before understanding current activity will miss the existing root cause.

C. Shadow individual agents while they resolve live cases to see how they actually work. ✓Correct. Shadowing exposes undocumented workarounds, tool switching, and bottlenecks that agents might not mention in interviews or surveys.

D. Read the current case management documentation and standard operating procedures.Incorrect. Documents usually describe the intended process, not the real one, so they would not reveal the informal workarounds driving the 14-minute average.

Why: When the goal is to diagnose a specific operational inefficiency, observation (shadowing) comes first because it shows what people really do rather than what they report. Surveys suit broad opinion gathering and JAD workshops suit future-state design.

The business analyst is running a 12-person Sales Cloud requirements workshop with frontline reps, two regional managers, and the VP of Sales. The VP dominates every topic and the reps have gone quiet. Which facilitation technique should the BA use so that everyone is heard?

Ask the VP to present the full set of requirements for the whole team to speed things up.
Use small breakout groups or round-robin input, where each participant offers ideas before open discussion, so dominant voices cannot drown out quieter ones.
Have the VP removed from the session for being disruptive.
Treat the VP's requirements as representative of the group and record them as final.

Show answer

Answer: B

A. Ask the VP to present the full set of requirements for the whole team to speed things up.Incorrect. Letting the VP speak for everyone shuts out the reps whose daily experience matters most; executive-only input often misses operational reality.

B. Use small breakout groups or round-robin input, where each participant offers ideas before open discussion, so dominant voices cannot drown out quieter ones. ✓Correct. Breakouts without the VP and round-robin contributions are designed to draw out quieter participants, and individual ideation before discussion avoids anchoring on the most senior voice.

C. Have the VP removed from the session for being disruptive.Incorrect. Ejecting a VP is politically damaging and removes a stakeholder whose input is needed; the BA should manage the dynamic through facilitation.

D. Treat the VP's requirements as representative of the group and record them as final.Incorrect. A single executive's top-down view can miss frontline realities, so treating it as the voice of 12 people is a requirements quality failure.

Why: Structured participation techniques counter dominant voices: breakouts that separate executives from frontline staff, round-robin turns before open discussion, or silent written idea generation before sharing. They even out participation and bring out the operational insight that executives can unintentionally suppress.

The business analyst will run a joint application design (JAD) session for a Service Cloud implementation with the operations director, three service managers, two Salesforce administrators, and the solution architect. Which preparation step matters MOST for a productive JAD session?

Create a fully designed future-state process map to present as the starting point for the group to validate.
Build a structured agenda with pre-assigned discussion topics, defined decision points, and a clear session objective, and send it to participants beforehand.
Have the solution architect design the Salesforce configuration before the JAD so technical decisions are settled when business stakeholders arrive.
Book the JAD session for at least 8 hours so every topic can be covered without rushing.

Show answer

Answer: B

A. Create a fully designed future-state process map to present as the starting point for the group to validate.Incorrect. JAD gets its value from designing together; presenting a finished design limits contributions and anchors the group on the BA's assumptions.

B. Build a structured agenda with pre-assigned discussion topics, defined decision points, and a clear session objective, and send it to participants beforehand. ✓Correct. A clear objective, a timed topic agenda, and assigned responsibilities, distributed early, let participants prepare and make decisions efficiently.

C. Have the solution architect design the Salesforce configuration before the JAD so technical decisions are settled when business stakeholders arrive.Incorrect. Settling technical decisions before business input defeats JAD's purpose of co-creating solutions across business and technical teams.

D. Book the JAD session for at least 8 hours so every topic can be covered without rushing.Incorrect. Length alone does not create productivity; without structure, a longer session just means more unfocused discussion.

Why: A productive JAD session depends on structured preparation: a clear objective, a topic agenda with defined decision points, and pre-assigned discussion items, all shared in advance so participants come ready and the discussion stays focused. Unstructured sessions tend to end with unresolved debates and vague outputs.

In a discovery workshop with sales operations and IT, the sales ops team talks in business terms while IT concentrates on technical constraints. Halfway through, the groups start talking past each other and progress stops. What is the MOST effective step for the business analyst?

Send the IT team out of the session and meet with them separately for a technical design discussion.
Translate technical constraints into business outcomes and sketch a process diagram on a shared whiteboard to give both groups a common visual language.
Bring a senior executive into the session to make a final call on the contested points.
Send both groups a post-session survey to rate priorities independently, then combine the results offline.

Show answer

Answer: B

A. Send the IT team out of the session and meet with them separately for a technical design discussion.Incorrect. Separating the groups avoids the problem instead of bridging the communication gap, which is the BA's job.

B. Translate technical constraints into business outcomes and sketch a process diagram on a shared whiteboard to give both groups a common visual language. ✓Correct. A shared visual and business-impact language gives both groups something concrete to work on together, so the session can progress.

C. Bring a senior executive into the session to make a final call on the contested points.Incorrect. Escalating to an executive in a working session is premature; facilitation techniques should be tried first.

D. Send both groups a post-session survey to rate priorities independently, then combine the results offline.Incorrect. Moving to an asynchronous survey loses the workshop's collaborative momentum; the breakdown should be resolved in the room.

Why: The BA bridges business and technical stakeholders. When vocabulary differences stall a session, visual facilitation (process maps, diagrams) plus translating constraints into business impact creates a shared reference point and gets the group moving again.

Fifteen minutes into a Service Cloud requirements workshop, a stakeholder starts presenting a detailed solution design, complete with field names, record types, and automation logic. The rest of the group begins debating that solution instead of exploring business needs. What should the business analyst do?

Let the discussion continue, since solutions proposed by stakeholders can be useful requirements input.
Record the proposed solution in the parking lot, acknowledge the stakeholder's expertise, and steer the group back to the underlying business problem the solution is meant to address.
Immediately document every proposed field name and automation rule as a requirement and close the workshop early.
Ask the IT architect to assess the proposed solution's feasibility before the workshop continues.

Show answer

Answer: B

A. Let the discussion continue, since solutions proposed by stakeholders can be useful requirements input.Incorrect. Turning the session into solution design too early yields solution-biased requirements and hides the underlying need, which another approach might serve better.

B. Record the proposed solution in the parking lot, acknowledge the stakeholder's expertise, and steer the group back to the underlying business problem the solution is meant to address. ✓Correct. Parking the idea respects the input without dismissing it, while redirecting to the business problem keeps requirements problem-focused and open to the best solution.

C. Immediately document every proposed field name and automation rule as a requirement and close the workshop early.Incorrect. Recording implementation details as requirements confuses one possible solution with the problem itself.

D. Ask the IT architect to assess the proposed solution's feasibility before the workshop continues.Incorrect. A mid-workshop feasibility review is premature because the business problem has not been confirmed yet.

Why: When stakeholders jump to design before needs are explored, the BA parks the proposed solution, recognizes the stakeholder's expertise, and returns the group to the business problem. The guiding principle is 'problem before solution': understand the need fully before judging how to meet it.

An athletic footwear company is extending its Salesforce implementation from North America to Europe. The business analyst finds that some North American requirements, such as particular data visibility rules and record sharing configurations, may conflict with GDPR in Europe. How should the BA respond?

Reuse the North American configuration for Europe and let IT make any GDPR adjustments after implementation.
Record the GDPR data privacy needs as regulatory/compliance requirements for the European rollout and involve the legal or compliance team to confirm the planned configuration satisfies GDPR obligations.
Leave the European team out of the Salesforce rollout until a separate GDPR-compliant platform is identified.
Ask the project sponsor to accept the GDPR compliance risk as part of the European rollout to keep the schedule.

Show answer

Answer: B

A. Reuse the North American configuration for Europe and let IT make any GDPR adjustments after implementation.Incorrect. Postponing GDPR work until after implementation risks serious violations; these requirements belong in the requirements phase.

B. Record the GDPR data privacy needs as regulatory/compliance requirements for the European rollout and involve the legal or compliance team to confirm the planned configuration satisfies GDPR obligations. ✓Correct. Compliance requirements are a non-functional category the BA must capture, and having legal or compliance validate the design before build guards against significant GDPR fines.

C. Leave the European team out of the Salesforce rollout until a separate GDPR-compliant platform is identified.Incorrect. Salesforce offers GDPR-compliant configuration options, so excluding Europe is an extreme reaction to a solvable requirements issue.

D. Ask the project sponsor to accept the GDPR compliance risk as part of the European rollout to keep the schedule.Incorrect. GDPR compliance is a legal obligation that a sponsor cannot waive for the sake of the schedule.

Why: When discovery uncovers regulatory requirements (GDPR, HIPAA, SOX), the BA documents them as regulatory/compliance requirements and brings in legal or compliance experts to validate the planned solution. Such requirements are non-negotiable constraints that outrank convenience and schedule, and surfacing them early avoids expensive fixes after go-live.

A company rolling out Salesforce for the first time wants its BA to draft a stakeholder engagement plan, and the sponsor asks specifically how stakeholders who push back should be handled. Which approach reflects the BEST professional practice for managing that resistance?

Pinpoint the resistant stakeholders and meet with them individually first to learn why they are resisting, before the wider engagement plan is built.
Mark resistant stakeholders as 'blockers' in the RACI matrix and send every communication through the project sponsor so their objections are sidestepped.
Expect the resistance to fade on its own after training and leave resistant stakeholders out of all engagement before go-live.
Record every resistant stakeholder and their concerns, then hand the list to the CEO so leadership can step in.

Show answer

Answer: A

A. Pinpoint the resistant stakeholders and meet with them individually first to learn why they are resisting, before the wider engagement plan is built. ✓Correct. Meeting resistant stakeholders before the broad plan is final shows whether their concerns are legitimate (process gaps, data quality, role changes) or based on misinformation, and that insight shapes a more effective engagement strategy.

B. Mark resistant stakeholders as 'blockers' in the RACI matrix and send every communication through the project sponsor so their objections are sidestepped.Incorrect. Branding people as 'blockers' and routing around them is adversarial; excluded stakeholders tend to resist harder. The BA should engage them, not bypass them.

C. Expect the resistance to fade on its own after training and leave resistant stakeholders out of all engagement before go-live.Incorrect. Resistance seldom disappears without engagement. Shutting people out before go-live usually amplifies resistance when an unfamiliar system is imposed on them.

D. Record every resistant stakeholder and their concerns, then hand the list to the CEO so leadership can step in.Incorrect. Going straight to the CEO is an outsized first step. The BA should understand and address the resistance directly, escalating only if those efforts fail.

Why: Handling resistance starts with finding its cause. Early one-on-one conversations reveal whether pushback comes from valid concerns (gaps in requirements), misinformation (unfounded fears), or personal stakes (impact on someone's role). Knowing the cause lets the BA respond with targeted engagement instead of generic inclusion activities that miss the real driver.

In a Service Cloud requirements workshop at a sneaker company, the customer service director demands real-time desktop notifications for every new case, while the IT security manager says real-time push notifications would breach the data security policy. Neither will budge. How should the business analyst keep the project moving?

Back the IT security manager, because security requirements always override business preferences.
Escalate to the project sponsor and halt all project work until a decision is reached.
Run a focused session with both stakeholders to uncover their underlying concerns and explore compliant notification options that satisfy both.
Log both requirements as 'Must-have' in the backlog and let the development team sort it out during build.

Show answer

Answer: C

A. Back the IT security manager, because security requirements always override business preferences.Incorrect. The BA facilitates consensus rather than ruling in favor of one stakeholder category. Both security and business needs must be addressed collaboratively.

B. Escalate to the project sponsor and halt all project work until a decision is reached.Incorrect. Stopping all work over one disagreement is disproportionate and delays the project. Facilitation comes first; escalation only if it fails.

C. Run a focused session with both stakeholders to uncover their underlying concerns and explore compliant notification options that satisfy both. ✓Correct. By clarifying what each side really needs (timely awareness versus data security), the BA can explore options such as in-app notifications, permission-based alerts, or secured notification channels that work for both.

D. Log both requirements as 'Must-have' in the backlog and let the development team sort it out during build.Incorrect. Developers need clear, agreed requirements. The conflict must be resolved during requirements work, not deferred to build.

Why: The BA's job with competing priorities is facilitation: bring the parties together, surface the real concerns, and find a mutually acceptable solution. Picking a side, stopping work, or handing the conflict to developers all fall short of the goal of reaching stakeholder consensus.

At an athletic footwear brand, the BA is running a requirements workshop for a new Experience Cloud self-service portal. Customer success wants every interaction to require an account login so data is captured; marketing wants fully anonymous access to encourage discovery. What is the BEST way for the BA to handle this conflict?

Go with marketing's preference, since acquiring users usually outranks capturing data.
Record both requirements as conflicting and leave the decision to the development team during build.
Lead a structured discussion that brings out the business goal behind each requirement, then offer options (e.g., anonymous browsing with progressive profiling, gated content for high-value resources) that serve both goals.
Escalate right away to the project sponsor for a final ruling on portal access.

Show answer

Answer: C

A. Go with marketing's preference, since acquiring users usually outranks capturing data.Incorrect. Ranking one team's priority without organizational context, and without a consensus process, is not the BA's call.

B. Record both requirements as conflicting and leave the decision to the development team during build.Incorrect. Conflicts must be settled during requirements; developers should get clear, agreed requirements rather than open business decisions.

C. Lead a structured discussion that brings out the business goal behind each requirement, then offer options (e.g., anonymous browsing with progressive profiling, gated content for high-value resources) that serve both goals. ✓Correct. Understanding the 'why' behind each request lets the BA propose creative options, such as letting visitors browse anonymously while collecting data gradually, that satisfy both teams. Facilitating that discussion is core BA collaboration work.

D. Escalate right away to the project sponsor for a final ruling on portal access.Incorrect. Escalation fits when facilitation fails; the BA should try to build consensus first.

Why: With conflicting requirements, the BA uncovers why each group wants what it wants and then proposes solutions that meet several goals at once. Here, an approach like anonymous browsing combined with progressive profiling can support marketing's discovery goal and customer success's data capture goal, reaching consensus through broader solution thinking instead of an either/or choice.

Find out if you're ready to pass

Take the free Business Analyst diagnostic: 20 questions, no account needed. Then unlock all 180 questions, full practice exams and the study guide.

Start the free diagnostic See plans

Business Analyst practice questions: Collaboration with Stakeholders

Ahead of a Service Cloud rollout at an outdoor gear company, the business analyst must find out why support agents average 14 minutes per case resolution, almost twice the industry benchmark. Which elicitation technique should the BA apply FIRST to uncover the root cause?

The business analyst is running a 12-person Sales Cloud requirements workshop with frontline reps, two regional managers, and the VP of Sales. The VP dominates every topic and the reps have gone quiet. Which facilitation technique should the BA use so that everyone is heard?

The business analyst will run a joint application design (JAD) session for a Service Cloud implementation with the operations director, three service managers, two Salesforce administrators, and the solution architect. Which preparation step matters MOST for a productive JAD session?

In a discovery workshop with sales operations and IT, the sales ops team talks in business terms while IT concentrates on technical constraints. Halfway through, the groups start talking past each other and progress stops. What is the MOST effective step for the business analyst?

A company rolling out Salesforce for the first time wants its BA to draft a stakeholder engagement plan, and the sponsor asks specifically how stakeholders who push back should be handled. Which approach reflects the BEST professional practice for managing that resistance?

Find out if you're ready to pass

Other sections of this exam