Palo Alto Networks NetSec-Architect Practice Test 34 - Prepaway
Practice Exams:

Pass Palo Alto Networks NetSec-Architect Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

NetSec-Architect Premium ETE File


  • Premium File 45 Questions & Answers. Last Update: Nov 10, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Palo Alto Networks NetSec-Architect Practice Test 34

Question 330

For the architecture board of fictional Seabright Global Systems, a proposed change to modernizing branches design, continuity, policy and architecture governance follows this problem: A branch relies on interface uptime alerts to manage SaaS experience but cannot distinguish ISP loss from a remote app slowdown. Discriminating observation: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Which network security architecture principle best explains why the existing design is insufficient?

  1. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, SASE branch resilience depends on redundant transport plus consistent cloud security inspection.
  2. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, Branch architecture needs user-experience evidence, not just interface availability signals.
  3. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.
  4. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, Branch security classification should preserve device and user meaning beyond the temporary IP address.

Explanation

Correct Answer

B:

Branch architecture needs user-experience evidence, not just interface availability signals. In the reported case, health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The remedy follows that mechanism: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics.

Incorrect Answers

A:

The cited mechanism, SASE branch resilience depends on redundant transport plus consistent cloud security inspection, does not account for the recorded clue. Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Branch architecture needs user-experience evidence, not just interface availability signals.

C:

An alternative principle holds that interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends, but this is not the mechanism shown here. This case reports that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Its governing principle is that branch architecture needs user-experience evidence, not just interface availability signals.

D:

The cited mechanism, branch security classification should preserve device and user meaning beyond the temporary IP address, does not account for the recorded clue. Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Branch architecture needs user-experience evidence, not just interface availability signals.

Question 331

At fictional Seabright Global Systems, the design team must preserve least privilege, auditable change and measurable business availability. Architecture risk: A branch relies on interface uptime alerts to manage SaaS experience but cannot distinguish ISP loss from a remote app slowdown. Evidence: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Which narrowly scoped design action AND separately measurable postchange confirmation together form the most defensible response?

  1. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, Design action: Design dual underlay and resilient remote-network on-ramp with monitored health and fail-closed enforcement policy. Independent proof: Disconnecting one branch circuit preserves authorized inspected application access through the alternate approved path.
  2. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, Design action: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Independent proof: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.
  3. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, Design action: Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security. Independent proof: A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel.
  4. For Seabright Global Systems and the branch adem lacks application-path visibility assessment, Design action: Design PAN-OS SD-WAN connectivity together with forwarding, zone-based policy, application inspection and managed failover. Independent proof: Lab path-failure tests preserve permitted business apps and block an unauthorized app in both active routes.

Explanation

Correct Answer

B:

Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The paired correction is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Validate its effect with: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert. Branch architecture needs user-experience evidence, not just interface availability signals.

Incorrect Answers

A:

The offered action and verification—design dual underlay and resilient remote-network on-ramp with monitored health and fail-closed enforcement policy. Independent proof: Disconnecting one branch circuit preserves authorized inspected application access through the alternate approved path—do not establish closure of the stated failure. The case evidence is that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The relevant response is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Check its effect against: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

C:

This pair does not resolve the recorded clue: health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The scoped correction is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Confirm success using: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

D:

The offered action and verification—design PAN-OS SD-WAN connectivity together with forwarding, zone-based policy, application inspection and managed failover. Independent proof: Lab path-failure tests preserve permitted business apps and block an unauthorized app in both active routes—do not establish closure of the stated failure. The case evidence is that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The relevant response is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Check its effect against: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

Question 332

At fictional Mariner Cloud Infrastructure, the architecture team is responsible for cross-region modernizing branches design validation during staged modernization and must verify failure behavior and compliance without expanding unnecessary application exposure. Risk case: A branch relies on interface uptime alerts to manage SaaS experience but cannot distinguish ISP loss from a remote app slowdown. Verified finding: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Which scoped architecture decision most directly addresses the documented control gap without unnecessarily changing other services?

  1. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Design PAN-OS SD-WAN connectivity together with forwarding, zone-based policy, application inspection and managed failover.
  2. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics.
  3. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Architect consistent DNS and URL/threat inspection for approved branch and roaming paths with controlled resolver policy.
  4. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Design dual underlay and resilient remote-network on-ramp with monitored health and fail-closed enforcement policy.

Explanation

Correct Answer

B:

The evidence is that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The appropriate change is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics, because branch architecture needs user-experience evidence, not just interface availability signals. After the change, simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

Incorrect Answers

A:

One alternative is to design PAN-OS SD-WAN connectivity together with forwarding, zone-based policy, application inspection and managed failover, but this does not address the decisive finding: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Instead, the correction is: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Check the result using: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

C:

The proposed change—architect consistent DNS and URL/threat inspection for approved branch and roaming paths with controlled resolver policy—does not repair the condition documented in the case. The decisive evidence is that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The necessary change is: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics.

D:

One alternative is to design dual underlay and resilient remote-network on-ramp with monitored health and fail-closed enforcement policy, but this does not address the decisive finding: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Instead, the correction is: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Check the result using: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

Question 333

For fictional Mariner Cloud Infrastructure, architects investigating cross-region modernizing branches design validation during staged modernization observe this risk: A branch relies on interface uptime alerts to manage SaaS experience but cannot distinguish ISP loss from a remote app slowdown. Before making broad configuration or topology changes, which finding most directly isolates the failure mechanism?

  1. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet.
  2. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Topology shows one remote-network connectivity attachment with no validated secondary path or policy-equivalent reroute.
  3. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Network insights show diverse Device-ID classifications and User-ID mappings sharing a single IP-range permit rule.
  4. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake.

Explanation

Correct Answer

D:

The record shows that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Branch architecture needs user-experience evidence, not just interface availability signals. The corresponding correction is: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics.

Incorrect Answers

A:

An alternative finding indicates that topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet; this is not the controlling evidence in the report. Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The appropriate correction is: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics.

B:

A different observation—topology shows one remote-network connectivity attachment with no validated secondary path or policy-equivalent reroute—does not establish the specific fault described here. The record instead shows this: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Branch architecture needs user-experience evidence, not just interface availability signals.

C:

A competing observation indicates that network insights show diverse Device-ID classifications and User-ID mappings sharing a single IP-range permit rule, which points away from this case. The distinguishing evidence is: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. That is consistent with the mechanism: branch architecture needs user-experience evidence, not just interface availability signals.

Question 334

At fictional Mariner Cloud Infrastructure, the security design for cross-region modernizing branches design validation during staged modernization faces: A branch relies on interface uptime alerts to manage SaaS experience but cannot distinguish ISP loss from a remote app slowdown. Diagnostic evidence: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Proposed design change: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Which independent observation would demonstrate that the change met its intended outcome?

  1. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel.
  2. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.
  3. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Injected jitter on the primary causes voice traffic to move to the cleaner approved path without bypassing security.
  4. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Disconnecting one branch circuit preserves authorized inspected application access through the alternate approved path.

Explanation

Correct Answer

B:

Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert. This post-change check addresses the recorded finding: health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Branch architecture needs user-experience evidence, not just interface availability signals.

Incorrect Answers

A:

A different check—A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert. This tests the condition shown by health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake.

C:

An alternative check—injected jitter on the primary causes voice traffic to move to the cleaner approved path without bypassing security—is not sufficient closure evidence for this fault. The relevant acceptance test is: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert. Branch architecture needs user-experience evidence, not just interface availability signals.

D:

A different check—disconnecting one branch circuit preserves authorized inspected application access through the alternate approved path—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert. This tests the condition shown by health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake.

Question 335

For the architecture board of fictional Mariner Cloud Infrastructure, a proposed change to cross-region modernizing branches design validation during staged modernization follows this problem: A branch relies on interface uptime alerts to manage SaaS experience but cannot distinguish ISP loss from a remote app slowdown. Discriminating observation: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Which network security architecture principle best explains why the existing design is insufficient?

  1. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Branch security classification should preserve device and user meaning beyond the temporary IP address.
  2. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Branch architecture needs user-experience evidence, not just interface availability signals.
  3. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, SASE branch resilience depends on redundant transport plus consistent cloud security inspection.
  4. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, DNS security is effective only if all relevant name-resolution paths cross a policy enforcement point.

Explanation

Correct Answer

B:

The governing principle is: Branch architecture needs user-experience evidence, not just interface availability signals. The case specifically shows health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The corresponding change is: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics.

Incorrect Answers

A:

An alternative principle holds that branch security classification should preserve device and user meaning beyond the temporary IP address, but this is not the mechanism shown here. This case reports that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Its governing principle is that branch architecture needs user-experience evidence, not just interface availability signals.

C:

That alternative rule—SASE branch resilience depends on redundant transport plus consistent cloud security inspection—does not explain the deciding observation: health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Branch architecture needs user-experience evidence, not just interface availability signals. That is the mechanism the corrective action must address.

D:

An alternative principle holds that DNS security is effective only if all relevant name-resolution paths cross a policy enforcement point, but this is not the mechanism shown here. This case reports that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Its governing principle is that branch architecture needs user-experience evidence, not just interface availability signals.

Question 336

At fictional Mariner Cloud Infrastructure, the design team must verify failure behavior and compliance without expanding unnecessary application exposure. Architecture risk: A branch relies on interface uptime alerts to manage SaaS experience but cannot distinguish ISP loss from a remote app slowdown. Evidence: Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. Which narrowly scoped design action AND separately measurable postchange confirmation together form the most defensible response?

  1. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Design action: Design dual underlay and resilient remote-network on-ramp with monitored health and fail-closed enforcement policy. Independent proof: Disconnecting one branch circuit preserves authorized inspected application access through the alternate approved path.
  2. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Design action: Design PAN-OS SD-WAN connectivity together with forwarding, zone-based policy, application inspection and managed failover. Independent proof: Lab path-failure tests preserve permitted business apps and block an unauthorized app in both active routes.
  3. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Design action: Design identity- and application-aware Prisma SD-WAN enforcement using available App-ID, User-ID and Device-ID signals. Independent proof: Controlled managed app traffic passes; a classified unauthorized IoT device is restricted and attributed.
  4. For Mariner Cloud Infrastructure and the branch adem lacks application-path visibility assessment, Design action: Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Independent proof: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

Explanation

Correct Answer

D:

The proposed action is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Independent verification is: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert. That pair addresses the actual recorded clue: health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake.

Incorrect Answers

A:

At Mariner Cloud Infrastructure, this pair does not address the recorded clue: health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The scoped correction is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Confirm success using: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

B:

At Mariner Cloud Infrastructure, the offered action and verification—design PAN-OS SD-WAN connectivity together with forwarding, zone-based policy, application inspection and managed failover. Independent proof: Lab path-failure tests preserve permitted business apps and block an unauthorized app in both active routes—do not establish closure of the stated failure. The case evidence is that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The relevant response is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Check its effect against: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

C:

That alternative would test a different outcome: design identity- and application-aware Prisma SD-WAN enforcement using available App-ID, User-ID and Device-ID signals. Independent proof: Controlled managed app traffic passes; a classified unauthorized IoT device is restricted and attributed. Here, health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake. The paired response is to design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics. Its acceptance check is: Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.

Question 337

At fictional Harborview Financial Services, the architecture team is responsible for modernizing branches design, continuity, policy and architecture governance and must preserve least privilege, auditable change and measurable business availability. Risk case: An enterprise connects a legacy third-party SD-WAN edge to Prisma Access without mapping tunnel ownership or route failover behavior. Verified finding: Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Which scoped architecture decision most directly addresses the documented control gap without unnecessarily changing other services?

  1. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Design dual underlay and resilient remote-network on-ramp with monitored health and fail-closed enforcement policy.
  2. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security.
  3. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Design identity- and application-aware Prisma SD-WAN enforcement using available App-ID, User-ID and Device-ID signals.
  4. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics.

Explanation

Correct Answer

B:

Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends. The direct correction is to define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security. Verify the outcome with: A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel.

Incorrect Answers

A:

The proposed change—design dual underlay and resilient remote-network on-ramp with monitored health and fail-closed enforcement policy—does not repair the condition documented in the case. The decisive evidence is that topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. The necessary change is: Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security.

C:

An alternative operation—design identity- and application-aware Prisma SD-WAN enforcement using available App-ID, User-ID and Device-ID signals—does not directly resolve the recorded failure. Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. The appropriate intervention is: Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security.

D:

The proposed change—design ADEM site and app transaction probes with correlated ISP, routing, identity and service metrics—does not repair the condition documented in the case. The decisive evidence is that topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. The necessary change is: Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security.

Question 338

For fictional Harborview Financial Services, architects investigating modernizing branches design, continuity, policy and architecture governance observe this risk: An enterprise connects a legacy third-party SD-WAN edge to Prisma Access without mapping tunnel ownership or route failover behavior. Before making broad configuration or topology changes, which finding most directly isolates the failure mechanism?

  1. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Network insights show diverse Device-ID classifications and User-ID mappings sharing a single IP-range permit rule.
  2. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake.
  3. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Prisma SD-WAN app telemetry shows high jitter for the selected lower-cost circuit and lower jitter on an alternate circuit.
  4. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet.

Explanation

Correct Answer

D:

The evidence shows that topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends. The direct correction is: Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security.

Incorrect Answers

A:

A competing observation indicates that network insights show diverse Device-ID classifications and User-ID mappings sharing a single IP-range permit rule, which points away from this case. The distinguishing evidence is: Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. That is consistent with the mechanism: interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

B:

An alternative finding indicates that health logs show both circuits up while branch-user synthetic web probes consistently fail at the external app handshake; this is not the controlling evidence in the report. Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. The appropriate correction is: Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security.

C:

A different observation—prisma SD-WAN app telemetry shows high jitter for the selected lower-cost circuit and lower jitter on an alternate circuit—does not establish the specific fault described here. The record instead shows this: Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

Question 339

At fictional Harborview Financial Services, the security design for modernizing branches design, continuity, policy and architecture governance faces: An enterprise connects a legacy third-party SD-WAN edge to Prisma Access without mapping tunnel ownership or route failover behavior. Diagnostic evidence: Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Proposed design change: Define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security. Which independent observation would demonstrate that the change met its intended outcome?

  1. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert.
  2. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Controlled managed app traffic passes; a classified unauthorized IoT device is restricted and attributed.
  3. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel.
  4. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Disconnecting one branch circuit preserves authorized inspected application access through the alternate approved path.

Explanation

Correct Answer

C:

Verify the result with: A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel. This tests the correction against the actual evidence: Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

Incorrect Answers

A:

An alternative check—simulated app failure produces an attributed application-stage incident while an ISP drop produces a distinct path alert—is not sufficient closure evidence for this fault. The relevant acceptance test is: A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

B:

A different check—controlled managed app traffic passes; a classified unauthorized IoT device is restricted and attributed—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel. This tests the condition shown by topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet.

D:

An alternative check—disconnecting one branch circuit preserves authorized inspected application access through the alternate approved path—is not sufficient closure evidence for this fault. The relevant acceptance test is: A tested guest segment remains policy restricted while allowed corporate apps survive loss of a primary tunnel. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

Question 340

For the architecture board of fictional Harborview Financial Services, a proposed change to modernizing branches design, continuity, policy and architecture governance follows this problem: An enterprise connects a legacy third-party SD-WAN edge to Prisma Access without mapping tunnel ownership or route failover behavior. Discriminating observation: Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Which network security architecture principle best explains why the existing design is insufficient?

  1. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, SD-WAN transport and NGFW threat policy must be architected as one forwarding/control system.
  2. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, SASE branch resilience depends on redundant transport plus consistent cloud security inspection.
  3. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, DNS security is effective only if all relevant name-resolution paths cross a policy enforcement point.
  4. For Harborview Financial Services and the third-party sd-wan edge security gap assessment, Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

Explanation

Correct Answer

D:

Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends. That distinction fits the observed clue: topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. The practical fix is to define supported third-party branch attachment, route scope, traffic steering and control-plane observability across SASE security.

Incorrect Answers

A:

That alternative rule—SD-WAN transport and NGFW threat policy must be architected as one forwarding/control system—does not explain the deciding observation: topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends. That is the mechanism the corrective action must address.

B:

An alternative principle holds that SASE branch resilience depends on redundant transport plus consistent cloud security inspection, but this is not the mechanism shown here. This case reports that topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Its governing principle is that interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

C:

The cited mechanism, DNS security is effective only if all relevant name-resolution paths cross a policy enforcement point, does not account for the recorded clue. Topology proof shows the legacy edge is capable of two tunnels but sends guest traffic directly to uninspected internet. Interoperable SASE branch solutions require explicit traffic classification and path ownership at both ends.

Palo Alto Networks Network Security Architect (NetSec-Architect) Practice Tests