CV0-003 · Question #843
An organization's two-node, hybrid container cluster is experiencing failures during horizontal scaling to the cloud cluster instance. The on-premises IP range is 192.168.0.0/16, and the cloud…
The correct answer is E. Incorrect IP route. A hybrid cluster spanning two non-overlapping subnets requires explicit IP routes between locations. Without a correct route, on-premises nodes cannot reach cloud instances even when those instances are healthy.
Question
An organization's two-node, hybrid container cluster is experiencing failures during horizontal scaling to the cloud cluster instance. The on-premises IP range is 192.168.0.0/16, and the cloud environment is 10.168.0.0/16. Overlapping or stretched VLANs are not permitted, and a node is deployed in each location. The cloud monitoring agent reports a healthy status for the second instance, but when pining the clusters from on premises, the following output is received:
Which of the following is the most likely reason for the scaling failure?
Options
- AIncorrect DNS entry
- BOffline cluster node
- CIncorrect proxy entry
- DIncorrect cluster IP
- EIncorrect IP route
How the community answered
(27 responses)- A22% (6)
- B4% (1)
- C7% (2)
- D7% (2)
- E59% (16)
Why each option
A hybrid cluster spanning two non-overlapping subnets requires explicit IP routes between locations. Without a correct route, on-premises nodes cannot reach cloud instances even when those instances are healthy.
A DNS misconfiguration would cause name resolution failures, but if the ping output shows a target IP directly, DNS is not in the path and would not explain the failure.
The cloud monitoring agent explicitly reports the second instance as healthy, which rules out the node being offline.
Proxy entries operate at the application layer for HTTP/HTTPS traffic and do not affect ICMP ping or low-level IP routing between subnets.
The cluster IPs are on distinct, non-overlapping subnets as described, and the cloud node reports healthy, so the cluster IP assignment itself is not the source of the failure.
The on-premises network (192.168.0.0/16) and cloud network (10.168.0.0/16) are separate, non-overlapping subnets with no stretched VLANs permitted, so traffic between them depends entirely on explicit IP routing. A missing or misconfigured route on the on-premises side would drop packets destined for the cloud subnet, causing ping failures and scaling failures even though the cloud node itself is healthy. This matches the symptom: cloud monitoring reports healthy, but on-premises connectivity fails.
Concept tested: IP routing in hybrid multi-subnet environments
Source: https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/hybrid-networking/vpn
Topics
Community Discussion
No community discussion yet for this question.