A customer is implementing Prisma Access (Managed by Strata Cloud Manager) to connect mobile users,...

B2B partner connections in this scenario present two compounding requirements: partners need reachability specifically to internally hosted proprietary applications on non-standard ports, and — critically — multiple B2B partners are advertising overlapping IP prefixes, which means Prisma Access cannot rely on raw source addressing alone to distinguish one partner ' s traffic from another ' s without introducing address translation. Onboarding these B2B connections as Remote Networks and applying dedicated NAT pools per connection resolves the overlapping-prefix problem directly at the point of ingress, translating each partner ' s overlapping internal addressing into a unique, non-conflicting address space as it enters the Prisma Access backbone — this is essential specifically because of the overlap condition stated in the scenario, making option B correct. Once translated to unique addressing, those NAT ' d prefixes still need to be made reachable to the specific internal application resources; advertising the corresponding (translated) network prefixes via eBGP or static routes ensures the data center and Prisma Access properly exchange reachability information for that now-unique addressing, making option A the necessary complementary action. Service connections (option C) are the mechanism used for the organization ' s own data center connectivity to Prisma Access broadly, not the specific mechanism for resolving the B2B overlapping-prefix and access-scoping requirement described here, so while service connections exist elsewhere in this deployment, they are not the answer to this specific sub-question. NAT ' ing traffic at the customer premises equipment (option D) pushes the translation responsibility onto each individual B2B partner ' s own infrastructure, which the customer does not control and cannot guarantee is correctly implemented, making it an unreliable and non-scalable solution compared to handling NAT natively within the Remote Networks onboarding.