A city runs Kubernetes clusters and servers in another public cloud and wants a consistent Azure management theme across that multi-cloud estate. Which service aligns?
Select an answer to reveal the explanation.
Short Explanation
Other-cloud clusters still in the mix? Arc is the consistency glue for Azure-style management across that sprawl. DNS failover and CDNs move traffic — they do not become your multi-cloud control plane.
Full Explanation
Azure Arc supports hybrid and multi-cloud management consistency under Azure control themes. When Kubernetes clusters and servers run in another public cloud but the city still wants a coherent Azure-oriented management story, Arc is the service theme that addresses projecting and governing that sprawl rather than leaving each cloud as an isolated console island.
Azure Traffic Manager alone provides DNS-based traffic distribution and failover; failover routing does not enroll foreign clusters into Azure Policy or become a multi-cloud control plane. A content delivery network caches and serves content at the edge; edge caches do not replace cluster governance. Virtual Network peering inside one region addresses private network connectivity within Azure networking designs—it is not the hybrid/multi-cloud management projection story Arc provides.
Exam caveat: multi-cloud management consistency is not the same as identical feature parity everywhere—Arc aligns management themes within supported resource types and scenarios. Operational check: inventory non-Azure clusters/servers in scope, map which Arc offerings apply, onboard a non-production cluster or server, and confirm it appears under Azure management views used for the city’s governance baseline.