Your question is Architecting Hardware Deployment Tracking. 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).
Walk me through how you would architect a tracking system for hardware deployment across distributed sites. Explain the entities, state transitions, APIs, synchronization model, and behavior during offline operation, retries, duplicate messages, and partial failures. The interviewer is checking whether you can turn deployment progress into a consistent, auditable system while separating desired state from observed state. Scope your answer to the backend, site connectivity, persistence, and operational failure handling, not UI design.