Question 650
Before approving a proposed shortcut for the following case—An architect wants a global colocation interconnect but assumes a private on-ramp and off-ramp are interchangeable—which risk should be considered first?
Explanation
Correct Answer
The issue is not a general product inconvenience: A direct colocation cable alone does not establish the correct security service traffic direction. That matters for an architect wants a global colocation interconnect but assumes a private on-ramp and off-ramp are interchangeable. The design should document the corresponding investigation and practical acceptance evidence.
Incorrect Answers
This can be appropriate when a team deploys four ZTNA Connectors across one group and assumes adding a fifth will automatically increase per-group capacity, but it does not isolate the distinguishing requirement here: An architect wants a global colocation interconnect but assumes a private on-ramp and off-ramp are interchangeable. The correct risk decision is a direct colocation cable alone does not establish the correct security service traffic direction.
That alternative belongs to the case: A private app uses unsupported NAT-sensitive IP semantics and a planned ZTNA Connector SNATs traffic. It is not sufficient evidence or remediation for an architect wants a global colocation interconnect but assumes a private on-ramp and off-ramp are interchangeable. The case-specific choice is a direct colocation cable alone does not establish the correct security service traffic direction.
This choice targets the separate scenario “two subsidiaries use overlapping 10.20.0.0/16 addresses for different private HR apps after a merger”. The expected safe result is that users reach the correct named app in each subsidiary without cross-site route ambiguity. The more relevant answer here is “A direct colocation cable alone does not establish the correct security service traffic direction”.