McAfee Secure

Exam Code: NetSec-Architect

Exam Name: Palo Alto Networks Network Security Architect

Certification Provider: Palo Alto Networks

Corresponding Certification: Palo Alto Networks Certified Network Security Architect

Palo Alto Networks NetSec-Architect Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

45 Questions & Answers with Testing Engine

"Palo Alto Networks Network Security Architect Exam", also known as NetSec-Architect exam, is a Palo Alto Networks certification exam.

Pass your tests with the always up-to-date NetSec-Architect Exam Engine. Your NetSec-Architect training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Palo Alto Networks NetSec-Architect Practice Test 26

Question 250

Original unofficial Palo Alto Networks NetSec-Architect scenario: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Which test result best demonstrates that the design meets its requirement?

  1. A test rule change follows its proper authority and produces a consistent auditable approval record.
  2. A packet capture shows protected log transport and the SIEM receives an attributed test event.
  3. A synthetic threat event correlates to its policy rule and source device in both systems.
  4. Local evidence remains intact and authorized high-severity test events appear in the cloud dashboard.

Explanation

Correct Answer

C:

Original fictional security architecture situation: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Governing principle: Log aggregation is only useful if records preserve source identity and chronology. The most defensible design response is: Define canonical timestamps, device IDs and schema mappings before connecting the managed logging export to the SIEM. Validation: A synthetic threat event correlates to its policy rule and source device in both systems. Sustained assurance: Regression-test parsing after connector or log schema updates

Incorrect Answers

A:

The suggested “A test rule change follows its proper authority and produces a consistent auditable approval record.” tests a different architectural concern: architect strata cloud manager, strata logging service and cloud identity engine. Here, a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.

B:

The proposed design “A packet capture shows protected log transport and the SIEM receives an attributed test event.” addresses this related architecture topic: recommend resilient strata logging service integrations and forwarding protocols. The actual security gap is that a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.

D:

This alternative is linked to the architecture category: recommend resilient strata logging service integrations and forwarding protocols. The actual problem is that a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent; the controlling distinction is: log aggregation is only useful if records preserve source identity and chronology.

Question 251

Original unofficial Palo Alto Networks NetSec-Architect scenario: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Which architectural principle best explains the risk or behavior?

  1. Unified organizational policy does not imply identical capabilities or object models across managers.
  2. Unencrypted transport can expose security telemetry and permit manipulation in transit.
  3. Operational analytics and legally required raw record custody may impose different storage controls.
  4. Log aggregation is only useful if records preserve source identity and chronology.

Explanation

Correct Answer

D:

Original fictional security architecture situation: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Governing principle: Log aggregation is only useful if records preserve source identity and chronology. The most defensible design response is: Define canonical timestamps, device IDs and schema mappings before connecting the managed logging export to the SIEM. Validation: A synthetic threat event correlates to its policy rule and source device in both systems. Sustained assurance: Regression-test parsing after connector or log schema updates

Incorrect Answers

A:

The proposed design “Unified organizational policy does not imply identical capabilities or object models across managers.” addresses this related architecture topic: architect strata cloud manager, strata logging service and cloud identity engine. The actual security gap is that a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.

B:

“Unencrypted transport can expose security telemetry and permit manipulation in transit.” concerns the separate design topic: recommend resilient strata logging service integrations and forwarding protocols. It would not fix the described weakness: a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.

C:

This alternative is linked to the architecture category: recommend resilient strata logging service integrations and forwarding protocols. The actual problem is that a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent; the controlling distinction is: log aggregation is only useful if records preserve source identity and chronology.

Question 252

Original unofficial Palo Alto Networks NetSec-Architect scenario: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Which continuing assurance practice best prevents recurrence?

  1. Revalidate service feature availability before consolidating management platforms.
  2. Regression-test parsing after connector or log schema updates.
  3. Monitor TLS certificate expiry and delivery errors on the log integration.
  4. Run periodic local/cloud event reconciliation and retention checks.

Explanation

Correct Answer

B:

Original fictional security architecture situation: A security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Governing principle: Log aggregation is only useful if records preserve source identity and chronology. The most defensible design response is: Define canonical timestamps, device IDs and schema mappings before connecting the managed logging export to the SIEM. Validation: A synthetic threat event correlates to its policy rule and source device in both systems. Sustained assurance: Regression-test parsing after connector or log schema updates

Incorrect Answers

A:

“Revalidate service feature availability before consolidating management platforms.” concerns the separate design topic: architect strata cloud manager, strata logging service and cloud identity engine. It would not fix the described weakness: a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.

C:

The suggested “Monitor TLS certificate expiry and delivery errors on the log integration.” tests a different architectural concern: recommend resilient strata logging service integrations and forwarding protocols. Here, a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.

D:

The proposed design “Run periodic local/cloud event reconciliation and retention checks.” addresses this related architecture topic: recommend resilient strata logging service integrations and forwarding protocols. The actual security gap is that a security architecture mixes Strata Logging Service logs with local SIEM alerts but timestamp normalization and device identifiers are inconsistent. Log aggregation is only useful if records preserve source identity and chronology.

Question 253

Original unofficial Palo Alto Networks NetSec-Architect scenario: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Which architectural decision best addresses the requirement?

  1. Define canonical timestamps, device IDs and schema mappings before connecting the managed logging export to the SIEM.
  2. Evaluate supported CIE/User-ID identity context for Prisma SD-WAN policy while retaining device fallback where appropriate.
  3. Design Cloud Identity Engine synchronization once while mapping each enforcement platform to the attributes it supports.
  4. Design separate authentication and directory/group synchronization paths as supported, with mapping freshness tests.

Explanation

Correct Answer

C:

Original fictional security architecture situation: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Governing principle: A shared directory is not proof that every product enforces the same identity predicates. The most defensible design response is: Design Cloud Identity Engine synchronization once while mapping each enforcement platform to the attributes it supports. Validation: The approved user-group mapping is consumed by each intended platform without inventing unsupported device signals. Sustained assurance: Maintain a platform-by-platform identity capability matrix

Incorrect Answers

A:

This alternative is linked to the architecture category: architect strata cloud manager, strata logging service and cloud identity engine. The actual problem is that a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer; the controlling distinction is: a shared directory is not proof that every product enforces the same identity predicates.

B:

The suggested “Evaluate supported CIE/User-ID identity context for Prisma SD-WAN policy while retaining device fallback where appropriate.” tests a different architectural concern: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. Here, a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

D:

“Design separate authentication and directory/group synchronization paths as supported, with mapping freshness tests.” concerns the separate design topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. It would not fix the described weakness: a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

Question 254

Original unofficial Palo Alto Networks NetSec-Architect scenario: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Which test result best demonstrates that the design meets its requirement?

  1. A synthetic threat event correlates to its policy rule and source device in both systems.
  2. A user moving between office workstations retains only the permissions assigned to that identity.
  3. The approved user-group mapping is consumed by each intended platform without inventing unsupported device signals.
  4. A newly approved user is authenticated and mapped into the intended authorization group after sync.

Explanation

Correct Answer

C:

Original fictional security architecture situation: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Governing principle: A shared directory is not proof that every product enforces the same identity predicates. The most defensible design response is: Design Cloud Identity Engine synchronization once while mapping each enforcement platform to the attributes it supports. Validation: The approved user-group mapping is consumed by each intended platform without inventing unsupported device signals. Sustained assurance: Maintain a platform-by-platform identity capability matrix

Incorrect Answers

A:

The suggested “A synthetic threat event correlates to its policy rule and source device in both systems.” tests a different architectural concern: architect strata cloud manager, strata logging service and cloud identity engine. Here, a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

B:

The proposed design “A user moving between office workstations retains only the permissions assigned to that identity.” addresses this related architecture topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual security gap is that a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

D:

This alternative is linked to the architecture category: recommend cloud identity engine on-prem agent and cloud-directory sync choices. The actual problem is that a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer; the controlling distinction is: a shared directory is not proof that every product enforces the same identity predicates.

Question 255

Original unofficial Palo Alto Networks NetSec-Architect scenario: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Which architectural principle best explains the risk or behavior?

  1. A shared directory is not proof that every product enforces the same identity predicates.
  2. Log aggregation is only useful if records preserve source identity and chronology.
  3. Dynamic address placement is a weak proxy for staff authorization in changing branches.
  4. An authentication assertion and a durable group-identity mapping serve distinct purposes.

Explanation

Correct Answer

A:

Original fictional security architecture situation: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Governing principle: A shared directory is not proof that every product enforces the same identity predicates. The most defensible design response is: Design Cloud Identity Engine synchronization once while mapping each enforcement platform to the attributes it supports. Validation: The approved user-group mapping is consumed by each intended platform without inventing unsupported device signals. Sustained assurance: Maintain a platform-by-platform identity capability matrix

Incorrect Answers

B:

“Log aggregation is only useful if records preserve source identity and chronology.” concerns the separate design topic: architect strata cloud manager, strata logging service and cloud identity engine. It would not fix the described weakness: a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

C:

This alternative is linked to the architecture category: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual problem is that a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer; the controlling distinction is: a shared directory is not proof that every product enforces the same identity predicates.

D:

The suggested “An authentication assertion and a durable group-identity mapping serve distinct purposes.” tests a different architectural concern: recommend cloud identity engine on-prem agent and cloud-directory sync choices. Here, a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

Question 256

Original unofficial Palo Alto Networks NetSec-Architect scenario: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Which continuing assurance practice best prevents recurrence?

  1. Maintain a platform-by-platform identity capability matrix.
  2. Regression-test parsing after connector or log schema updates.
  3. Audit identity mapping coverage and fallback behavior by branch.
  4. Alert on stalled synchronization rather than inferring health from successful sign-ins.

Explanation

Correct Answer

A:

Original fictional security architecture situation: A retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. Governing principle: A shared directory is not proof that every product enforces the same identity predicates. The most defensible design response is: Design Cloud Identity Engine synchronization once while mapping each enforcement platform to the attributes it supports. Validation: The approved user-group mapping is consumed by each intended platform without inventing unsupported device signals. Sustained assurance: Maintain a platform-by-platform identity capability matrix

Incorrect Answers

B:

This alternative is linked to the architecture category: architect strata cloud manager, strata logging service and cloud identity engine. The actual problem is that a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer; the controlling distinction is: a shared directory is not proof that every product enforces the same identity predicates.

C:

The suggested “Audit identity mapping coverage and fallback behavior by branch.” tests a different architectural concern: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. Here, a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

D:

The proposed design “Alert on stalled synchronization rather than inferring health from successful sign-ins.” addresses this related architecture topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. The actual security gap is that a retail chain wants one identity integration to serve NGFW, Prisma Access, and Prisma SD-WAN but does not inventory supported identity attributes for each consumer. A shared directory is not proof that every product enforces the same identity predicates.

Question 257

Original unofficial Palo Alto Networks NetSec-Architect scenario: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Which architectural decision best addresses the requirement?

  1. Design separate authentication and directory/group synchronization paths as supported, with mapping freshness tests.
  2. Create explicit identity classes and least-privilege group-policy distinctions for employees, contractors and service users across target platforms.
  3. Design identity synchronization resilience across credential lifecycle, directory dependencies and node health, not only host redundancy.
  4. Choose a supported on-premises Cloud Identity Engine directory synchronization agent model and limit outbound connectivity appropriately.

Explanation

Correct Answer

D:

Original fictional security architecture situation: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Governing principle: Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure. The most defensible design response is: Choose a supported on-premises Cloud Identity Engine directory synchronization agent model and limit outbound connectivity appropriately. Validation: Group membership updates from the isolated directory reach the cloud mapping through the approved agent path. Sustained assurance: Monitor agent freshness, certificates and least-privileged directory service permissions

Incorrect Answers

A:

This alternative is linked to the architecture category: recommend cloud identity engine on-prem agent and cloud-directory sync choices. The actual problem is that an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter; the controlling distinction is: private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

B:

The suggested “Create explicit identity classes and least-privilege group-policy distinctions for employees, contractors and service users across target platforms.” tests a different architectural concern: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. Here, an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

C:

The proposed design “Design identity synchronization resilience across credential lifecycle, directory dependencies and node health, not only host redundancy.” addresses this related architecture topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual security gap is that an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

Question 258

Original unofficial Palo Alto Networks NetSec-Architect scenario: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Which test result best demonstrates that the design meets its requirement?

  1. A newly approved user is authenticated and mapped into the intended authorization group after sync.
  2. Group membership updates from the isolated directory reach the cloud mapping through the approved agent path.
  3. A contractor test identity receives only the approved limited application set.
  4. A controlled node or credential-expiry simulation alerts operators and the supported backup path maintains mappings.

Explanation

Correct Answer

B:

Original fictional security architecture situation: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Governing principle: Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure. The most defensible design response is: Choose a supported on-premises Cloud Identity Engine directory synchronization agent model and limit outbound connectivity appropriately. Validation: Group membership updates from the isolated directory reach the cloud mapping through the approved agent path. Sustained assurance: Monitor agent freshness, certificates and least-privileged directory service permissions

Incorrect Answers

A:

The suggested “A newly approved user is authenticated and mapped into the intended authorization group after sync.” tests a different architectural concern: recommend cloud identity engine on-prem agent and cloud-directory sync choices. Here, an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

C:

“A contractor test identity receives only the approved limited application set.” concerns the separate design topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. It would not fix the described weakness: an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

D:

This alternative is linked to the architecture category: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual problem is that an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter; the controlling distinction is: private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

Question 259

Original unofficial Palo Alto Networks NetSec-Architect scenario: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Which architectural principle best explains the risk or behavior?

  1. An authentication assertion and a durable group-identity mapping serve distinct purposes.
  2. Directory presence indicates an authenticated principal, not a universal business entitlement.
  3. Redundant compute does not eliminate common-mode authentication failure.
  4. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

Explanation

Correct Answer

D:

Original fictional security architecture situation: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Governing principle: Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure. The most defensible design response is: Choose a supported on-premises Cloud Identity Engine directory synchronization agent model and limit outbound connectivity appropriately. Validation: Group membership updates from the isolated directory reach the cloud mapping through the approved agent path. Sustained assurance: Monitor agent freshness, certificates and least-privileged directory service permissions

Incorrect Answers

A:

The proposed design “An authentication assertion and a durable group-identity mapping serve distinct purposes.” addresses this related architecture topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. The actual security gap is that an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

B:

“Directory presence indicates an authenticated principal, not a universal business entitlement.” concerns the separate design topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. It would not fix the described weakness: an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

C:

This alternative is linked to the architecture category: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual problem is that an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter; the controlling distinction is: private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

Question 260

Original unofficial Palo Alto Networks NetSec-Architect scenario: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Which continuing assurance practice best prevents recurrence?

  1. Alert on stalled synchronization rather than inferring health from successful sign-ins.
  2. Monitor agent freshness, certificates and least-privileged directory service permissions.
  3. Recertify external identity group scope at contract expiration.
  4. Rotate service credentials and test failover before expiration windows.

Explanation

Correct Answer

B:

Original fictional security architecture situation: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Governing principle: Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure. The most defensible design response is: Choose a supported on-premises Cloud Identity Engine directory synchronization agent model and limit outbound connectivity appropriately. Validation: Group membership updates from the isolated directory reach the cloud mapping through the approved agent path. Sustained assurance: Monitor agent freshness, certificates and least-privileged directory service permissions

Incorrect Answers

A:

“Alert on stalled synchronization rather than inferring health from successful sign-ins.” concerns the separate design topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. It would not fix the described weakness: an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

C:

The suggested “Recertify external identity group scope at contract expiration.” tests a different architectural concern: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. Here, an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

D:

The proposed design “Rotate service credentials and test failover before expiration windows.” addresses this related architecture topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual security gap is that an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.

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