Secure Inbound Access has been configured to allow access to an RDP application at a...

Secure Inbound Access reverses the normal traffic direction Prisma Access is built around: an internet-originated user is reaching into a Remote Network location to access an internally hosted application such as RDP, and when source NAT is applied to that inbound flow, the return traffic from the RDP application must be routed back not to the original internet user ' s real address, but to the translated source address, which corresponds to the Service Endpoint Address of the Inbound Access Remote Network Node. If the branch CPE ' s routing table does not have a route pointing that translated address back toward Prisma Access — because the required static or dynamic route to the Service Endpoint Address was never added during onboarding or was misconfigured — the RDP server ' s response traffic has no path back into the tunnel and is dropped or black-holed at the branch, producing exactly the " return traffic not reaching the internet user " symptom described, which makes option B the correct root cause. A Remote Network Security policy source zone of " Untrust " (option A) would affect whether inbound traffic is permitted by policy at all, but the scenario states the commit was successful and implies policy is allowing the flow; the failure described is specifically a return-path routing issue, not a policy match issue. The " Allow inbound flows to other Remote Networks " checkbox (option C) governs a different capability — inter-remote-network inbound reachability — and is unrelated to the return-path routing failure for this internet-to-branch RDP flow. Option D references the eBGP Router ID, which is a BGP peering identifier, not the actual translated source NAT address the CPE needs a route back to; the correct routing target is the Service Endpoint Address, not the eBGP Router ID.