Practice Exams:

Palo Alto Networks NetSec-Architect Dumps

EXAM: Palo Alto Networks Network Security Architect
Verified By Experts
Premium Bundle
$49.99

NetSec-Architect Premium ETE File


  • Premium File 45 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Palo Alto Networks NetSec-Architect Practice Test 29

Question 280

An insurer consolidates cloud and data-center authorization rules around one identity governance source. Suppose the team implements this unsafe shortcut: Assume an identity group configured on one NGFW automatically creates matching Prisma Access access rules. Which concrete security or availability failure is most likely?

  1. Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load
  2. A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds
  3. A local exception can unintentionally alter security policy across unrelated subsidiaries
  4. Hybrid workers receive inconsistent least-privilege controls across office and remote connections

Answer & Explanations

Correct answer: D

A.

That outcome arises from a different failure: Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load. The related situation is: A bank needs redundant firewall logs across two data centers without loss during a collector maintenance. In the present case: An insurer consolidates cloud and data-center authorization rules around one identity governance source. The more pertinent consequence is: Hybrid workers receive inconsistent least-privilege controls across office and remote connections. Prevent it by: Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping.

B.

That outcome arises from a different failure: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. The related situation is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. In the present case: An insurer consolidates cloud and data-center authorization rules around one identity governance source. The more pertinent consequence is: Hybrid workers receive inconsistent least-privilege controls across office and remote connections. Prevent it by: Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping.

C.

That outcome arises from a different failure: A local exception can unintentionally alter security policy across unrelated subsidiaries. The related situation is: A holding company manages cloud NGFW policies for three subsidiaries sharing global protection templates. In the present case: An insurer consolidates cloud and data-center authorization rules around one identity governance source. The more pertinent consequence is: Hybrid workers receive inconsistent least-privilege controls across office and remote connections. Prevent it by: Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping.

D.

Hybrid workers receive inconsistent least-privilege controls across office and remote connections. This follows when the team chooses the shortcut: Assume an identity group configured on one NGFW automatically creates matching Prisma Access access rules. The situation is: An insurer consolidates cloud and data-center authorization rules around one identity governance source. The correction is: Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping. The observable test is: Use one authorized identity group in both enforcement environments and compare effective allow/deny outcomes.

Question 281

A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Which network security architecture decision best satisfies the business and technical requirements?

  1. Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed
  2. Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping
  3. Design a synchronized Panorama HA pair at separated failure domains with planned management failover validation
  4. Size Panorama log collectors and collector groups for ingestion, retention, redundancy and supported quorum behavior

Answer & Explanations

Correct answer: A

A.

The best-matched action is: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. The actual need is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Here Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access. Check the result by: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

B.

This action would be appropriate when: A national retailer wants office and mobile employees to follow role-aligned policies while connecting from different sites. It follows from: Shared directory records do not guarantee identical policies, so each enforcement plane must receive mapped groups with verified refresh and availability. The current case instead states: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The response it requires is: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

C.

The alternative action addresses a different condition: A national retailer centralizes policy for hundreds of NGFWs and cannot tolerate one management VM failure. Its reasoning is: Panorama HA protects central management availability, but forwarding firewalls still require their own independent HA and policy continuity design. Here the case is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The more direct response is: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

D.

That choice fits Design resilient distributed log collector groups, illustrated by: A bank needs redundant firewall logs across two data centers without loss during a collector maintenance. Here the material condition is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The controlling reason is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access. Apply: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

Question 282

A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. An architect proposes: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. Which technical explanation most directly supports that architecture?

  1. Log collector redundancy preserves duplicate evidence during node loss, while throughput and capacity change when duplicate logs consume additional storage
  2. Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access
  3. The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration
  4. Cloud-managed shared policy can be inherited while scoped overrides prevent one subsidiary from changing another business unit's rules

Answer & Explanations

Correct answer: B

A.

This offered mechanism is relevant to Design resilient distributed log collector groups: Log collector redundancy preserves duplicate evidence during node loss, while throughput and capacity change when duplicate logs consume additional storage. It explains the different task: Size Panorama log collectors and collector groups for ingestion, retention, redundancy and supported quorum behavior. The current condition is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. For that condition the operative principle is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

B.

Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access. This causal relationship matters in: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. It supports the action: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. Test the result by: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

C.

This offered mechanism is relevant to Plan firewall log forwarding preferences independent of management failover: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration. It explains the different task: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. The current condition is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. For that condition the operative principle is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

D.

This offered mechanism is relevant to Separate Strata Cloud Manager administration scopes for subsidiaries: Cloud-managed shared policy can be inherited while scoped overrides prevent one subsidiary from changing another business unit's rules. It explains the different task: Design SCM folders, snippets and variables with scoped inheritance and change approval across business units. The current condition is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. For that condition the operative principle is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

Question 283

A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Publish a harmless test configuration from a child folder and check inherited policy plus effective variable substitutions
  2. Generate a permitted test event and trace ingestion, role-limited search and approved downstream export
  3. Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point
  4. Modify a test user group in the local directory and verify permitted group changes reach relevant policy consumers

Answer & Explanations

Correct answer: C

A.

That test checks a different intervention: Design SCM folders, snippets and variables with scoped inheritance and change approval across business units. Its applicable setting is: A holding company manages cloud NGFW policies for three subsidiaries sharing global protection templates. It would not directly establish the result required by: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The specific acceptance check here is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

B.

That test checks a different intervention: Map Strata Logging Service ingestion, analytics consumers and authorized security operations exports independently from SCM policy authoring. Its applicable setting is: An investment firm wants standardized cloud policy administration but regulated logs must reach its SIEM. It would not directly establish the result required by: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The specific acceptance check here is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

C.

Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point. This evidence tests whether the response, Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed, addresses the specific condition: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The mechanism being tested is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

D.

That test checks a different intervention: Deploy an approved Cloud Identity Engine directory-sync agent with resilient connectivity to required local directory services. Its applicable setting is: A hospital maintains Active Directory in a private data center and needs group updates in cloud-managed NGFW policies. It would not directly establish the result required by: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The specific acceptance check here is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

Question 284

A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Which tempting shortcut would most directly undermine the required architecture control?

  1. Open unrestricted inbound directory service ports from the internet to eliminate the synchronization agent
  2. Map every federated user to one shared admin account because SAML authentication already worked
  3. Send sensitive event streams over unauthenticated plaintext links because the receiving SIEM is on a corporate subnet
  4. Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity

Answer & Explanations

Correct answer: D

A.

This shortcut would undermine Choose Cloud Identity Engine on-premises directory synchronization for: A hospital maintains Active Directory in a private data center and needs group updates in cloud-managed NGFW policies. The present situation is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Here the unsafe move is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. That could cause: Compromised or unapproved branch users can obtain access intended for privileged staff. Use: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

B.

This shortcut would undermine Federate identity with an approved cloud directory and SAML provider for: A SaaS-heavy enterprise uses Entra ID and wants role-based NGFW and Prisma Access policy. The present situation is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Here the unsafe move is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. That could cause: Compromised or unapproved branch users can obtain access intended for privileged staff. Use: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

C.

This shortcut would undermine Forward cloud security logs reliably using secured syslog for: A health provider exports Strata logs to a regulatory SIEM across a shared transit network. The present situation is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Here the unsafe move is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. That could cause: Compromised or unapproved branch users can obtain access intended for privileged staff. Use: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

D.

The unsafe shortcut is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. It conflicts with the necessary control for: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The plausible consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Instead: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. Confirm with: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

Question 285

A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. Suppose the team implements this unsafe shortcut: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. Which concrete security or availability failure is most likely?

  1. Compromised or unapproved branch users can obtain access intended for privileged staff
  2. Monitoring evidence may be disclosed, forged or lost across the forwarding boundary
  3. Critical alerts can be missed or private records disclosed to unapproved external channels
  4. A legitimate application user may inherit administration rights without any approved identity privilege

Answer & Explanations

Correct answer: A

A.

Compromised or unapproved branch users can obtain access intended for privileged staff. This follows when the team chooses the shortcut: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. The situation is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The correction is: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. The observable test is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

B.

That outcome arises from a different failure: Monitoring evidence may be disclosed, forged or lost across the forwarding boundary. The related situation is: A health provider exports Strata logs to a regulatory SIEM across a shared transit network. In the present case: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The more pertinent consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Prevent it by: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

C.

That outcome arises from a different failure: Critical alerts can be missed or private records disclosed to unapproved external channels. The related situation is: A payment company sends critical event summaries to incident response but full logs remain in its SIEM. In the present case: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The more pertinent consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Prevent it by: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

D.

That outcome arises from a different failure: A legitimate application user may inherit administration rights without any approved identity privilege. The related situation is: A bank needs cloud-console SSO for security engineers but workload policies use employee directory groups. In the present case: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. The more pertinent consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Prevent it by: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

Question 286

A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. Which network security architecture decision best satisfies the business and technical requirements?

  1. Map Strata Logging Service ingestion, analytics consumers and authorized security operations exports independently from SCM policy authoring
  2. Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed
  3. Deploy an approved Cloud Identity Engine directory-sync agent with resilient connectivity to required local directory services
  4. Configure Cloud Identity Engine integration with supported Entra ID or Okta identity sources and test SAML or cloud-directory group claims

Answer & Explanations

Correct answer: B

A.

The alternative action addresses a different condition: An investment firm wants standardized cloud policy administration but regulated logs must reach its SIEM. Its reasoning is: Central logging and cloud policy administration are related but distinct services with their own connectivity, retention, access and availability constraints. Here the case is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The more direct response is: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

B.

Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. The case describes: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The reason this response fits is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access. Confirm it with: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

C.

That choice fits Choose Cloud Identity Engine on-premises directory synchronization, illustrated by: A hospital maintains Active Directory in a private data center and needs group updates in cloud-managed NGFW policies. Here the material condition is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The controlling reason is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access. Apply: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

D.

This action would be appropriate when: A SaaS-heavy enterprise uses Entra ID and wants role-based NGFW and Prisma Access policy. It follows from: Federated identity exchanges authenticated assertions and group information without exposing a static corporate LDAP server to arbitrary internet clients. The current case instead states: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The response it requires is: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

Question 287

A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. An architect proposes: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. Which technical explanation most directly supports that architecture?

  1. Federated identity exchanges authenticated assertions and group information without exposing a static corporate LDAP server to arbitrary internet clients
  2. Encryption and delivery monitoring protect integrity and confidentiality of log transit; merely sending plaintext UDP leaves gaps and exposure risks
  3. Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access
  4. Event notification transports vary in payload, delivery guarantees and privacy, so each destination needs defined alert meaning and failure handling

Answer & Explanations

Correct answer: C

A.

This offered mechanism is relevant to Federate identity with an approved cloud directory and SAML provider: Federated identity exchanges authenticated assertions and group information without exposing a static corporate LDAP server to arbitrary internet clients. It explains the different task: Configure Cloud Identity Engine integration with supported Entra ID or Okta identity sources and test SAML or cloud-directory group claims. The current condition is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. For that condition the operative principle is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

B.

This offered mechanism is relevant to Forward cloud security logs reliably using secured syslog: Encryption and delivery monitoring protect integrity and confidentiality of log transit; merely sending plaintext UDP leaves gaps and exposure risks. It explains the different task: Select authenticated encrypted syslog over TLS or supported log export for a central SIEM with explicit retry and monitoring design. The current condition is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. For that condition the operative principle is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

C.

Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access. This causal relationship matters in: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. It supports the action: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. Test the result by: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

D.

This offered mechanism is relevant to Route security event notifications for distinct responders: Event notification transports vary in payload, delivery guarantees and privacy, so each destination needs defined alert meaning and failure handling. It explains the different task: Design controlled Strata Logging Service export and alert routing using supported HTTP, email or syslog integrations suited to severity. The current condition is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. For that condition the operative principle is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

Question 288

A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Inject synthetic high-severity events and confirm correct destination, access control and retry observation
  2. Revoke an operator's administrative role and confirm console denial without disrupting ordinary employee User-ID application policies
  3. Use one authorized identity group in both enforcement environments and compare effective allow/deny outcomes
  4. Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point

Answer & Explanations

Correct answer: D

A.

That test checks a different intervention: Design controlled Strata Logging Service export and alert routing using supported HTTP, email or syslog integrations suited to severity. Its applicable setting is: A payment company sends critical event summaries to incident response but full logs remain in its SIEM. It would not directly establish the result required by: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The specific acceptance check here is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

B.

That test checks a different intervention: Use User-ID for policy attribution and controlled SAML-based administrator authentication for human console access. Its applicable setting is: A bank needs cloud-console SSO for security engineers but workload policies use employee directory groups. It would not directly establish the result required by: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The specific acceptance check here is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

C.

That test checks a different intervention: Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping. Its applicable setting is: A national retailer wants office and mobile employees to follow role-aligned policies while connecting from different sites. It would not directly establish the result required by: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The specific acceptance check here is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

D.

Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point. This evidence tests whether the response, Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed, addresses the specific condition: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The mechanism being tested is: Central identity signals can help branch enforcement discriminate user context; routing path selection alone does not determine identity-based access.

Question 289

A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. Which tempting shortcut would most directly undermine the required architecture control?

  1. Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity
  2. Assume an identity group configured on one NGFW automatically creates matching Prisma Access access rules
  3. Use a single Panorama virtual appliance and declare that all data-plane firewalls are resilient because management is centralized
  4. Enable redundant logging on a single unpaired collector and claim all audit evidence survives its disk failure

Answer & Explanations

Correct answer: A

A.

The unsafe shortcut is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. It conflicts with the necessary control for: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The plausible consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Instead: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. Confirm with: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

B.

This shortcut would undermine Apply Cloud Identity Engine consistently to NGFW and Prisma Access for: A national retailer wants office and mobile employees to follow role-aligned policies while connecting from different sites. The present situation is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. Here the unsafe move is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. That could cause: Compromised or unapproved branch users can obtain access intended for privileged staff. Use: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

C.

This shortcut would undermine Architect Panorama management HA without confusing it with data-plane HA for: A national retailer centralizes policy for hundreds of NGFWs and cannot tolerate one management VM failure. The present situation is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. Here the unsafe move is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. That could cause: Compromised or unapproved branch users can obtain access intended for privileged staff. Use: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

D.

This shortcut would undermine Design resilient distributed log collector groups for: A bank needs redundant firewall logs across two data centers without loss during a collector maintenance. The present situation is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. Here the unsafe move is: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. That could cause: Compromised or unapproved branch users can obtain access intended for privileged staff. Use: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

Question 290

A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. Suppose the team implements this unsafe shortcut: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. Which concrete security or availability failure is most likely?

  1. Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load
  2. Compromised or unapproved branch users can obtain access intended for privileged staff
  3. A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds
  4. A local exception can unintentionally alter security policy across unrelated subsidiaries

Answer & Explanations

Correct answer: B

A.

That outcome arises from a different failure: Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load. The related situation is: A bank needs redundant firewall logs across two data centers without loss during a collector maintenance. In the present case: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The more pertinent consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Prevent it by: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

B.

Compromised or unapproved branch users can obtain access intended for privileged staff. This follows when the team chooses the shortcut: Treat any branch traffic originating from the same SD-WAN tunnel as one fully trusted identity. The situation is: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The correction is: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. The observable test is: Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point.

C.

That outcome arises from a different failure: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. The related situation is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. In the present case: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The more pertinent consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Prevent it by: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

D.

That outcome arises from a different failure: A local exception can unintentionally alter security policy across unrelated subsidiaries. The related situation is: A holding company manages cloud NGFW policies for three subsidiaries sharing global protection templates. In the present case: A shipping company requires authorized warehouse roles to be distinguished across its SD-WAN sites. The more pertinent consequence is: Compromised or unapproved branch users can obtain access intended for privileged staff. Prevent it by: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed.

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