Your question is De-risk a Critical Team Dependency. 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 are the engineering manager for a hardware-enabled product launch, and your team is on the critical path for a customer-facing release. A key dependency owned by another team is now slipping, and without it your team cannot complete integration, validation, or the launch readiness review on time. The dependency owner has their own roadmap commitments, your leadership team is asking for a firm date, and the launch delay would affect a committed customer rollout.
What would you do if a critical project was at risk because of a dependency on another team?