A control says a dataset must stay in a named authorized cloud offering. A private interconnect into a cheaper commercial region is up. The commercial region is not that offering. Which path meets the control?
Select an answer to reveal the explanation.
Short Explanation
Private is only half of the rule, and you aimed it at the wrong offering. You use a private path into the named authorized offering. A cheaper commercial region stays out of bounds even when the cable never touches the internet.
Full Explanation
The control names the offering, not merely a private cable. A private interconnect into a commercial region that is not that offering fails the boundary even though it stays off the public internet. The path that fits is private connectivity into the named offering. An internet VPN into the right offering fails the private-path side of a control that also keeps the dataset off the public internet. The two private paths are not interchangeable, because the control does name an offering. Exam caveat: this is a design fit for the stated control, not a legal opinion. Buying the right region's interconnect does not by itself authorize the workload. Operational check: routes for the dataset should point at the interconnect for the named offering, and the commercial region should not carry them.