Quiz SSE-Engineer: Palo Alto Networks Security Service Edge Engineer

To meet the customer’s requirements, two separate Prisma Access instances should be deployed:
Instance 1 should include mobile users, remote networks, and private access for internal
connectivity. This ensures that mobile users can access the internet, data centers, and remote branch
locations while enforcing security policies.
Instance 2 should be configured with remote networks and private application access for B2B
connections. This instance will restrict access to only the required internally developed applications
using non-standard ports, ensuring that partners cannot access other corporate resources.
By using specific configuration scopes for different connection types, the security team can manage
access to mobile users and branch locations, while the network team can manage B2B partner
connections. This ensures proper segmentation of management responsibilities while maintaining
security and compliance.

To meet the customer’s requirements, GlobalProtect and Remote Networks should be used as
follows:
GlobalProtect: This enables secure access for mobile users, ensuring internet filtering, data center
connectivity, and access to branch locations.
Remote Networks: This is used to provide security and connectivity for branch locations, ensuring
internet filtering and data center access.
Service Connections: These allow both mobile users and branch locations to securely connect to the
data center for internal resources.
This configuration ensures that mobile users and branch locations can securely access the internet
while maintaining a segregated and secure connection to internal resources. It also aligns with
Prisma Access's best practices for security enforcement, traffic filtering, and centralized
management.

Enabling eBGP for dynamic routing and configuring Remote Networks ensures seamless connectivity
between branch locations, mobile users, and the data center. eBGP allows Prisma Access to
dynamically exchange routes with the Customer Premises Equipment (CPE), optimizing path
selection without requiring manual updates. Configuring Remote Networks and defining branch IP
subnets using static routes ensures controlled and segmented routing, aligning with security policies.
This setup provides proper internet filtering, data center connectivity, and restricted access for B2B
partners while keeping management responsibilities aligned.

Service connections enable secure connectivity between Prisma Access and on-premises data
centers, allowing mobile users and branch locations to access internal applications. They facilitate
seamless integration of internal networks with Prisma Access while maintaining security policies.
Colo-Connect provides a dedicated and optimized pathway for traffic between Prisma Access and
data centers, ensuring stable performance and reduced latency over the internet. Both components
together support secure and efficient data center connectivity while aligning with the customer's
access control and filtering requirements.

Configuring a webhook allows the company to receive real-time notifications when Prisma Access
changes its egress IP addresses, ensuring that policy rules are updated automatically. Downloading a
client certificate is necessary for authentication to the Egress IP API, allowing secure API access for
retrieving updated IP addresses. These actions ensure that security policies remain effective without
manual intervention.

Palo Alto Networks documentation explicitly states that the "Preview Changes" functionality within
the Strata Cloud Manager (SCM) push dialogue allows engineers to review a detailed summary of all
modifications that will be applied to the Prisma Access configuration before committing the changes.
This is the primary and most reliable method to ensure only the intended changes are deployed.
Let's analyze why the other options are incorrect based on official documentation:
A . Review the SCM portal for blue circular indicators next to each configuration menu item and
ensure only the intended areas of configuration have this indicator. While blue circular indicators
might signify unsaved changes within a specific configuration section, they do not provide a
comprehensive, consolidated view of all pending changes across different policy areas. This method
is insufficient for verifying the entirety of the intended modifications.
B . Compare the candidate configuration and the most recent version under "Config Version
Snapshots". While comparing configuration snapshots is a valuable method for understanding
historical changes and potentially identifying unintended deviations after a push, it does not provide
a real-time preview of the pending changes before they are applied during the current modification
session
C . Select the most recent job under Operations > Push Status to view the pending changes that
would apply to Prisma Access. The "Push Status" section primarily displays the status and details of
completed or in-progress push operations. It does not offer a preview of the changes before a push is
initiated.
Therefore, the "Preview Changes" feature within the push dialogue is the documented and
recommended method for an engineer to verify that only the intended changes will be applied when
modifying Prisma Access policy configuration in Strata Cloud Manager (SCM).

Palo Alto Networks documentation clearly states that when configuring the traffic replication feature
in Prisma Access, you must specify an internal security appliance as the destination for the mirrored
traffic. This appliance, typically a Palo Alto Networks next-generation firewall or a third-party security
tool, is responsible for receiving and analyzing the replicated traffic for various purposes like threat
analysis, troubleshooting, or compliance monitoring.
Let's analyze why the other options are incorrect based on official documentation:
B . Dedicated cloud storage location: While Prisma Access logs and other data might be stored in the
cloud, the mirrored traffic for real-time analysis is directly streamed to a designated security
appliance, not a passive storage location.
C . Panorama: Panorama is the centralized management system for Palo Alto Networks firewalls.
While Panorama can receive logs and manage the configuration of Prisma Access, it is not the direct
destination for real-time mirrored traffic intended for immediate analysis.
D . Strata Cloud Manager (SCM): Strata Cloud Manager is the platform used to configure and manage
Prisma Access. It facilitates the setup of traffic replication, including specifying the destination
appliance, but it does not directly receive or analyze the mirrored traffic itself.
Therefore, the mirrored traffic from the traffic replication feature in Prisma Access is directed to a
specified internal security appliance for analysis.

When network routers appear multiple times with different IP addresses in IoT Security, it is likely
because they have multiple interfaces with separate IPs. Merging these entries into a single device
with multiple interfaces ensures that the system correctly identifies each router as a unique entity
while maintaining visibility across all its interfaces. This approach prevents unnecessary duplicates,
improves asset management, and enhances security monitoring.

Selecting the “Disable Server Response Inspection” checkbox means that traffic flowing from the
server to the client will not be inspected for threats, even if a threat protection profile is applied to
the Security policy rule. This setting can reduce processing overhead but may expose the network to
threats embedded in server responses, such as malware or exploits.

In Prisma Access's default routing mode, the service connections establish BGP sessions with the
customer premises equipment (CPE) in the data centers. To ensure traffic destined for mobile users
in a specific region (e.g., North America) traverses the service connection in that same region, you
need to control the route advertisements.
Filtering out the mobile user pool prefixes from the other region on each service connection achieves
this by:
Preventing the data center in one region from learning the specific mobile user prefixes of the other
region. For example, the North American service connection would filter out the mobile user pool
prefixes allocated to European users.
Ensuring that when a data center needs to send traffic to a mobile user, it will only see and use the
route advertised by the service connection in the appropriate geographical region. This forces the
traffic to enter the Prisma Access infrastructure through the intended regional service connection.
Let's analyze why the other options are incorrect based on official documentation regarding default
routing mode:
A . Configure BGP on the customer premises equipment (CPE) to prefer the assigned community
string attribute on the mobile user prefixes in its respective Prisma Access region. While BGP
communities can be used for influencing routing decisions, in the context of default routing mode
and ensuring regional traffic flow, relying solely on the CPE to prefer community strings might not be
the most robust or direct method to guarantee traffic traverses the correct regional service
connection. The service connection itself needs to control the advertisement of prefixes.
C . Configure BGP on the customer premises equipment (CPE) to prefer the MED attribute on the
mobile user prefixes in its respective Prisma Access region. The BGP MED (Multi-Exit Discriminator)
attribute is primarily used to influence the path selection between autonomous systems (AS) or
within the same AS at different entry points. In this scenario, where service connections are
advertising prefixes, filtering at the source (service connection) is a more direct and reliable way to
ensure regional traffic flow than relying on the MED attribute on the CPE.
D . Configure each service connection to prepend the BGP ASN five times for mobile user pool
prefixes originating from the other region. BGP AS path prepending is a mechanism to make a path
less desirable. While this could influence routing, it doesn't guarantee that traffic will always take the
intended regional path. Filtering provides a more definitive control over which routes are advertised
and learned.
Therefore, configuring each service connection to filter out the mobile user pool prefixes from the
other region in the advertisements to the data center is the verified method to ensure traffic
destined for mobile users traverses the service connection in the appropriate region when using
Prisma Access in default routing mode.