Question 660
The team must redesign controls for this problem: A datacenter integration requires the customer network to control egress routing decisions instead of Prisma Access. Which recommendation targets the documented root cause?
Explanation
Correct Answer
The appropriate architecture decision is to use the supported hot-potato route preference where customer network controls downstream paths. The stated requirement is: A datacenter integration requires the customer network to control egress routing decisions instead of Prisma Access. It follows from the evidence gathered by review BGP advertisements and differences between default and hot-potato service connection routing modes, and should be signed off only after trace tests show traffic handed to the customer network at the intended location.
Incorrect Answers
The distinct use case for this response is “an architect wants a global colocation interconnect but assumes a private on-ramp and off-ramp are interchangeable”. The prior inspection is identify whether traffic is entering Prisma Access or returning to private application networks. The present case instead calls for “Use the supported hot-potato route preference where customer network controls downstream paths”.
That option is relevant to “an application backend needs to initiate a connection to a managed endpoint, but the team proposes a connector design without validating directionality”. Under change control, verify that authorized management connections work in the required direction without opening general inbound access rather than relying on a diagram alone. It is not sufficient to establish the selected outcome, “Use the supported hot-potato route preference where customer network controls downstream paths”, in this question.
This can be appropriate when a Prisma Access tenant needs to establish ZTNA Connector IP pools but the proposed ranges overlap with existing mobile user addresses, but it does not isolate the distinguishing requirement here: A datacenter integration requires the customer network to control egress routing decisions instead of Prisma Access. The correct action decision is use the supported hot-potato route preference where customer network controls downstream paths.