Welcome to your interview.
The question is on your right: Write Unambiguous Project Documentation. Take a moment with it first.
Talk your thinking through with me if you like - when you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes). Discussion and graded submissions share your five interviewer interactions, so spend them well.
You are documenting a business process and system change before delivery starts. The goal is to make sure engineering, QA, operations, and business stakeholders all interpret the requirements the same way and do not make different assumptions later.
How do you write clear, concise documentation that leaves no room for ambiguity?