Your question is Uncover Client Needs in Discovery. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You're working with a client on a new product request, and the stated ask sounds clear on the surface. But you suspect the request may be a proxy for a deeper business problem, workflow issue, or user pain point. You need to figure out what they actually need before recommending a solution.
How do you uncover what a client actually needs, not just what they ask for?