Technical challenges of a multi-cloud strategy
realism about multi-cloud complexity.
data consistency and egress costs across providers, cross-cloud networking and latency, and federating disparate IAM systems, plus operational and tooling overhead.
WHAT THIS TESTS This probes whether you understand that multi-cloud trades lock-in for substantial operational and technical complexity, especially around data, networking, and identity.
A GOOD ANSWER COVERS Data consistency is the hardest problem: an application split across providers needs its data somewhere, and synchronizing or replicating state across clouds introduces latency, conflict resolution, and large egress fees, since moving data out of a provider is expensive. You often end up pinning data to one cloud or accepting eventual consistency. Networking requires connecting otherwise isolated provider networks through VPNs or dedicated interconnects, dealing with cross-cloud latency, overlapping IP ranges, and differing network primitives like security groups versus NSGs. Identity is genuinely difficult because each provider has its own IAM model and policy language; you need a central identity provider and federation so a single identity and consistent least-privilege policy span clouds. On top of all this sits duplicated tooling, monitoring, and the breadth of expertise required.
COMMON WRONG ANSWERS Believing multi-cloud delivers seamless portability for free. Ignoring egress costs. Underestimating inter-cloud latency for chatty or stateful workloads. Assuming one IAM system covers all providers. Pretending a single abstraction layer removes all differences without its own cost.
LIKELY FOLLOW-UPS How do you handle a shared database across clouds? Federate identity how? Is the lock-in avoidance worth it? When is multi-cloud actually justified?
ONE CONCRETE EXAMPLE A firm runs compute on both AWS and GCP. They keep the primary database in one cloud to avoid cross-cloud write latency and egress, connect the two with a dedicated interconnect, and federate access through a central identity provider with SAML or OIDC so engineers use one identity, while accepting that they now maintain monitoring and IaC for both platforms.
Interview question
Why does keeping data consistent across two cloud providers often become the hardest part of a multi-cloud application?
- a.Data consistency is automatically handled by any load balancer
- b.Cloud providers prohibit replicating data between them
- c.All providers share a single global database service
- d.Cross-cloud replication adds latency, conflict resolution, and expensive egress chargesCorrect
Why? this is the answer
Synchronizing state across providers means high-latency replication, conflict handling, and costly data egress, which is why teams often pin data to one cloud. Providers do not prohibit replication, load balancers do not solve consistency, and there is no shared global database.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
- #multi-cloud
- #vendor-lock-in
- #data-consistency
- #iam
- #networking
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles