Stakeholder & client-work interview questionsAnalyst interview questions
← Interview & exam prep
Analyst interview questions

Stakeholder & client-work interview questions

24 questions from beginner to advanced, each with the correct answer and a one-line explanation of why. Study them here, or take them as a timed test.

24 questionsBeginner 12 · Intermediate 12Answers + explanations
Take it as a timed test
Free PDF
All 389 questions & answers, in one file

DAX, Excel, Power BI, Fabric, certification practice and analyst interviews — every answer with the reason behind it. Print it, study it offline.

Instant download, plus the free Tuesday briefing. Unsubscribe in one click.

Beginner 12 questions

1A stakeholder asks for 'a dashboard with everything'. Your best first step is to…

  1. Add every available column
  2. Politely refuse the request
  3. Pick charts you personally like
  4. Clarify the key decisions and questions it must support
  5. Build every visual you can fit
Show answerHide answer

D · Clarify the key decisions and questions it must support Start from the decisions the report must drive; scope follows from the questions, not from 'everything'.

2The most useful requirements question is usually…

  1. Which chart type do you prefer?
  2. What decision will you make with this?
  3. Which tool should I use?
  4. How many pages should it have?
  5. Which colour do you want?
Show answerHide answer

B · What decision will you make with this? Anchoring on the decision reveals the real metrics, grain and audience.

3You don't understand a business term the client uses. You should…

  1. Avoid using the term
  2. Ask them to define it and confirm your understanding
  3. Guess from context and move on
  4. Assume it means what you think
  5. Look it up later without confirming
Show answerHide answer

B · Ask them to define it and confirm your understanding Confirming shared definitions prevents building the wrong thing.

4The best way to confirm you captured requirements correctly is to…

  1. Email a long document nobody reads
  2. Start building immediately
  3. Rely on memory
  4. Wait for the client to complain
  5. Summarize them back (spec or mockup) and get sign-off
Show answerHide answer

E · Summarize them back (spec or mockup) and get sign-off A short written summary or mockup with sign-off aligns expectations early.

5The client disputes an unexpected number in the report. First you…

  1. Blame the data source
  2. Hide the visual
  3. Change it to match their expectation
  4. Insist your number is right
  5. Trace it to the source and validate the calculation together
Show answerHide answer

E · Trace it to the source and validate the calculation together Investigate transparently; the number may be right, or you may find a real issue — either way, trust grows.

6Presenting insights to executives, you should lead with…

  1. Every metric you built
  2. The methodology in detail
  3. Raw data tables
  4. The data model diagram
  5. The key takeaway and recommendation, then support
Show answerHide answer

E · The key takeaway and recommendation, then support Executives want the 'so what' first; detail is available on request.

7A requested deadline is unrealistic. The professional response is to…

  1. Communicate early and offer trade-offs (scope vs time)
  2. Refuse the project outright
  3. Silently miss it
  4. Agree now and miss it later
  5. Work nights secretly and hope
Show answerHide answer

A · Communicate early and offer trade-offs (scope vs time) Early, honest options let the client choose scope, time or resources.

8Scope creep is best managed by…

  1. Logging new requests and re-prioritizing via change control
  2. Ignoring extra requests
  3. Saying yes to every new request
  4. Escalating angrily
  5. Doing everything for free
Show answerHide answer

A · Logging new requests and re-prioritizing via change control Capture and prioritize changes visibly so trade-offs are explicit.

9When source data quality is poor, you should…

  1. Refuse to deliver anything
  2. Quietly fix and hide it
  3. Flag it, quantify the impact and agree remediation with the owner
  4. Ship it without comment
  5. Delete the bad rows silently
Show answerHide answer

C · Flag it, quantify the impact and agree remediation with the owner Surface data issues with impact and an owner; don't mask them.

10Useful hand-over documentation for a delivered report includes…

  1. Just a screenshot
  2. Data sources, refresh, measure definitions and known caveats
  3. Nothing — it's self-explanatory
  4. The DAX with no context
  5. Only your name
Show answerHide answer

B · Data sources, refresh, measure definitions and known caveats Definitions, lineage, refresh and caveats let others trust and maintain it.

11To drive adoption of a new report, the most effective step is to…

  1. Restrict who can open it
  2. Email it once and hope
  3. Train users and tie it to their real workflow and decisions
  4. Make it look fancier
  5. Add more visuals
Show answerHide answer

C · Train users and tie it to their real workflow and decisions Adoption follows relevance and enablement, not decoration.

12Two stakeholders give conflicting requirements. You should…

  1. Surface the conflict and facilitate a prioritization decision
  2. Do neither
  3. Build both and double the work
  4. Pick one secretly
  5. Let them fight it out
Show answerHide answer

A · Surface the conflict and facilitate a prioritization decision Make the conflict visible and get an explicit priority call from the business.

Intermediate 12 questions

13A client insists on a metric definition you believe is misleading. Best approach…

  1. Refuse and walk away
  2. Comply silently
  3. Implement both with no note
  4. Escalate to their boss immediately
  5. Show the impact with examples, recommend the sound definition, and document their decision if they persist
Show answerHide answer

E · Show the impact with examples, recommend the sound definition, and document their decision if they persist Advise clearly with evidence, but respect their decision on record — that's professional, not passive.

14An error is found in a report already used for decisions. You should…

  1. Wait to see if anyone notices
  2. Fix it quietly and say nothing
  3. Downplay it
  4. Blame the source system
  5. Notify stakeholders promptly, quantify the impact and correct transparently
Show answerHide answer

E · Notify stakeholders promptly, quantify the impact and correct transparently Prompt, transparent correction protects trust and lets decisions be revisited.

15A stakeholder wants direct production-database access to 'self-serve'. A balanced response is to…

  1. Grant raw prod access
  2. Give them the admin password
  3. Refuse any access
  4. Offer a governed semantic model/dataset with the agreed metrics
  5. Export everything to Excel weekly
Show answerHide answer

D · Offer a governed semantic model/dataset with the agreed metrics Provide governed self-service (a shared model with RLS), not raw production access.

16Estimating a new report, best practice is to…

  1. Give one exact date to please them
  2. Guess to sound fast
  3. Break it into tasks and give a range with stated assumptions and scope
  4. Refuse to estimate
  5. Pad the estimate massively
Show answerHide answer

C · Break it into tasks and give a range with stated assumptions and scope A ranged, assumption-based estimate tied to scope is honest and defensible.

17During a live demo, a visual breaks. The professional move is to…

  1. Acknowledge it calmly, note it, continue, and follow up with a fix
  2. Pretend it's intended
  3. End the meeting
  4. Hide that screen forever
  5. Blame the software loudly
Show answerHide answer

A · Acknowledge it calmly, note it, continue, and follow up with a fix Composure plus a clear follow-up commitment keeps credibility.

18Adoption is low two months after launch. Your first diagnostic step is to…

  1. Send another announcement email
  2. Add more features
  3. Talk to users about barriers and observe their actual workflow
  4. Blame the users
  5. Rebuild the whole UI
Show answerHide answer

C · Talk to users about barriers and observe their actual workflow Understand the real barrier before changing anything — usually it's fit, not features.

19A request would expose sensitive personal data to a broad audience. You should…

  1. Raise the privacy/governance concern and apply access controls or RLS
  2. Fulfil it as asked
  3. Anonymize nothing but ship it
  4. Ignore the concern
  5. Ask the intern to decide
Show answerHide answer

A · Raise the privacy/governance concern and apply access controls or RLS Flag data-protection risk and enforce least-privilege access; governance is part of delivery.

20The client asks for a prediction the data cannot support. Best response…

  1. Explain the data's limits and offer what can be shown reliably
  2. Blame the data team
  3. Refuse to talk further
  4. Invent a number
  5. Guess and caveat quietly
Show answerHide answer

A · Explain the data's limits and offer what can be shown reliably Set honest expectations and redirect to defensible, useful analysis.

21Mid-project the client changes the primary KPI. You should…

  1. Refuse the change
  2. Silently swap it and absorb the delay
  3. Start over from scratch immediately
  4. Ignore it to protect the timeline
  5. Assess the impact via change control and re-baseline scope/timeline
Show answerHide answer

E · Assess the impact via change control and re-baseline scope/timeline Treat it as a change: assess impact, agree the new baseline, communicate.

22An executive wants a single traffic-light indicator for a nuanced metric. Best…

  1. Add ten more KPIs instead
  2. Provide the indicator with clear thresholds and a drill-through to context
  3. Pick a colour at random
  4. Refuse; it's too simplistic
  5. Show only the raw data
Show answerHide answer

B · Provide the indicator with clear thresholds and a drill-through to context Give the simple signal they need, but make the definition and context transparent.

23Prioritizing a backlog with limited time, the best criterion is…

  1. Whoever shouts loudest
  2. Easiest tasks only
  3. Newest request first
  4. Your personal interest
  5. Business value/impact versus effort, agreed with stakeholders
Show answerHide answer

E · Business value/impact versus effort, agreed with stakeholders Value-vs-effort, agreed openly, keeps prioritization objective and defensible.

24A client keeps adding 'small' changes after sign-off. The healthiest response is to…

  1. Absorb them all for free
  2. Redo the contract angrily
  3. Silently deprioritize their project
  4. Refuse to speak to them
  5. Acknowledge each, note it against scope, and agree how to handle them
Show answerHide answer

E · Acknowledge each, note it against scope, and agree how to handle them Track changes against the agreed scope and decide together — protects both quality and the relationship.

More analyst interview questions