Home › MCA Cloud Computing › cloudcomputing › cloudobservability › A common trade-off when adopting a strict multi-…
A common trade-off when adopting a strict multi-cloud architecture is:
AInability to use any internet protocol at all
BLoss of provider-specific managed-service depth in exchange for portability — you tend to use the lowest-common-denominator services
CPermanent zero-cost compute hosting
DAutomatic infinite scaling regardless of workload
Answer & Solution
Correct answer: B. Loss of provider-specific managed-service depth in exchange for portability — you tend to use the lowest-common-denominator services
Multi-cloud portability often pushes teams toward lowest-common-denominator services (VMs, K8s, object storage) and away from deeply differentiated managed services (BigQuery, Cosmos DB, etc.). The other options are fiction.
Related questions
A canary deployment differs from a blue/green deployment because:What does an SRE typically aim for when setting the WHITE-BOX vs BLACK-BOX monitoring balaWhich managed-observability service maps to its cloud correctly?A hybrid cloud architecture connects on-premises systems to one or more public clouds. WhiA multi-cloud strategy primarily aims to:Which observability practice helps a SRE diagnose a specific slow user request in a microsAn error budget is computed from an SLO. If an SLO is 99.9% success over 30 days, the erroService-level objectives (SLOs) are best described as: