Once an administrator has moved away from Prisma Access ' s default, automatic bandwidth-sharing behavior and explicitly customized bandwidth allocation per site on a shared IPSec termination node, the platform respects that deliberate, manual configuration rather than silently recalculating or redistributing percentages whenever a new site is added to the same node. Onboarding a fifth branch office onto a termination node where the existing four sites already have customized, fixed bandwidth values does not trigger an automatic rebalancing to a new even split; instead, the new site simply has no bandwidth allocation defined for it and will remain unallocated, effectively receiving no guaranteed or prioritized QoS treatment, until the engineer explicitly assigns it a bandwidth value as part of onboarding. This makes option B the accurate description of default platform behavior. Options A and C both describe an automatic, evenly-redistributed percentage outcome (25% and 20% respectively, which would correspond to five equal shares or four equal shares) that does not reflect how customized QoS interacts with new site onboarding — automatic even redistribution is the behavior only when no manual customization has been introduced in the first place, and once customization exists, the platform does not silently override or reflow it. Option D is incorrect because new branch offices absolutely can be added to an IPSec termination node with existing customized QoS; the addition itself is fully supported, it simply requires the administrator to manually define that site ' s bandwidth.

Palo Alto Networks documentation directly addresses this exact scenario: when the majority of traffic flows logged by a service connection are asymmetric — meaning the forward and return legs of a session traverse different paths through the Prisma Access backbone — disabling traffic logging specifically on that service connection is documented as the action that may be required to reduce the resulting consumption of Strata Logging Service storage, since asymmetric flows can generate excessive or fragmented log volume relative to the operational value the logs actually provide. This makes option B the directly documented and correct answer for this specific storage-consumption scenario. Configuring a log forwarding profile filter to selectively exclude asymmetric traffic (option A) is a more surgical-sounding idea, but it is not the documented mechanism Palo Alto Networks provides for this problem; log forwarding profiles control which log types are sent to which external destinations broadly, not a fine-grained filter isolating only asymmetric-flow traffic specifically for exclusion. Disabling the log forwarding profile for the service connection entirely (option C) is a broader and less precise action than the dedicated " disable traffic logging " setting, and is not the specific, named configuration Palo Alto Networks documents for this use case. Reducing the log retention period (option D) addresses how long already-generated logs are kept in storage, not the underlying rate at which new log volume is being generated by asymmetric flows, so it treats the symptom of storage growth rather than its actual cause.

Embargo rules are a purpose-built, pre-defined Security policy rule construct in Prisma Access that lets an organization block inbound connection attempts — most commonly authentication attempts against the GlobalProtect portal, Explicit Proxy, or Remote Networks entry points — that originate from specific countries or regions, using Palo Alto Networks ' geolocation-based source address matching. Their defining behavior is unconditional blocking (a Drop action) of the specified source countries, which makes option C the accurate general description of their purpose; they exist to reduce attack surface against brute-force and credential-stuffing attempts by preventing connection attempts before normal identity-based Security policy would even be evaluated, since embargo rules are enforced as top-of-stack pre-rules using the reserved tag PA_predefined_embargo_rule. Option A is incorrect because embargo rules are a binary block mechanism, not a rate-limiting or throttling control — there is no partial-restriction behavior involved. Option B inverts the logic entirely; embargo rules are not an allow-list mechanism restricting traffic to only a permitted set of countries, they are a deny-list mechanism for specific countries while leaving all other geographies unaffected. Option D is too narrow and factually incorrect as a generalization: embargo rules are configurable for any country or region the organization chooses to specify, and are frequently used for the broader set of countries subject to export or sanctions restrictions, not a fixed three-country list.