Your question is API Versioning and Graceful Degradation. 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).
How do you handle API versioning, backward compatibility, and graceful degradation when network conditions are poor?
Explain how you would design the client and service contracts so older mobile app versions remain functional while APIs evolve. Cover request negotiation, schema compatibility, retries, caching, timeouts, offline behavior, fallback responses, observability, and safe rollout or rollback decisions.