100% Latest & Updated Palo Alto Networks NetSec-Architect Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 200
Select THREE linked elements for National health network: a supported architecture, the direct test, and the required outcome. After National health network completed a limited security transformation pilot, reviewers observed a control gap: A cloud-managed branch fleet has inconsistent log retention and central investigations miss devices. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For National health network: Infer that enabling cloud management also guarantees infinite centralized log retention.
- For National health network: Investigators can retrieve expected events centrally under the approved retention design.
- For National health network: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
- For National health network: Align supported SAML authentication with Cloud Identity Engine/User-ID mapping and identity propagation to enforcement points.
- For National health network: Cloud policy receives on-premises directory identities through a supported protected integration.
- For National health network: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
Explanation
Correct Answer
B:The required end state is Investigators can retrieve expected events centrally under the approved retention design. The architect must deploy Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources. and validate using Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C050; angle 4; post-pilot control gap; option considered: Investigators can retrieve expected events centrally under the approved retention design.
C:This checks the relevant strata logging service logging enforcement path rather than a distant symptom. Generate labeled events from two firewall regions and validate central ingestion and retention behavior. The expected evidence is Investigators can retrieve expected events centrally under the approved retention design. Case R152-C050; angle 4; post-pilot control gap; option considered: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
F:This directly addresses the recorded gap: A cloud-managed branch fleet has inconsistent log retention and central investigations miss devices. The architectural control is Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources. The decisive test is Generate labeled events from two firewall regions and validate central ingestion and retention behavior. The objective is Investigators can retrieve expected events centrally under the approved retention design. Case R152-C050; angle 4; post-pilot control gap; option considered: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
Incorrect Answers
A:This is an unsafe or insufficient shortcut for strata logging service logging: Infer that enabling cloud management also guarantees infinite centralized log retention. The scoped requirement instead calls for Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources. Case R152-C050; angle 4; post-pilot control gap; option considered: Infer that enabling cloud management also guarantees infinite centralized log retention.
D:This option addresses a different design objective: SAML identity to user mapping, not the primary control for strata logging service logging. It would be relevant where A user authenticates successfully to cloud identity but firewall policies still see an unknown user. Here the necessary evidence is Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C050; angle 4; post-pilot control gap; option considered: Align supported SAML authentication with Cloud Identity Engine/User-ID mapping and identity propagation to enforcement points.
E:On-premises identity directory bridge addresses a different architectural concern, such as when an enterprise's authoritative directory remains on premises and direct inbound exposure of domain controllers is forbidden. It does not establish strata logging service logging here. The decisive test is to generate labeled events from two firewall regions and validate central ingestion and retention behavior.
Question 201
For Technology research institute, which is the most directly supported architectural control for cloud identity engine directory synchronization? The security architecture board of Technology research institute is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Technology research institute: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
- For Technology research institute: Adopt a documented supported noninteractive Okta integration method and rotate app credentials under owner control.
- For Technology research institute: Align supported SAML authentication with Cloud Identity Engine/User-ID mapping and identity propagation to enforcement points.
- For Technology research institute: Architect a shared Cloud Identity Engine identity source and clearly mapped policies for each supported enforcement platform.
Explanation
Correct Answer
A:This directly addresses the recorded gap: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. The architectural control is Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. The decisive test is Change a test user's group assignment and verify sync state and resulting access decision. The objective is Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C051; angle 1; architecture design; option considered: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
Incorrect Answers
B:This option addresses a different design objective: Okta directory service credentials, not the primary control for cloud identity engine directory synchronization. It would be relevant where An Okta directory sync deployment needs stable unattended operation, but its interactive authorization expires repeatedly. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C051; angle 1; architecture design; option considered: Adopt a documented supported noninteractive Okta integration method and rotate app credentials under owner control.
C:SAML identity to user mapping addresses a different architectural concern, such as when a user authenticates successfully to cloud identity but firewall policies still see an unknown user. It does not establish cloud identity engine directory synchronization here. The decisive test is to change a test user's group assignment and verify sync state and resulting access decision.
D:This option addresses a different design objective: Cross-platform identity policy consistency, not the primary control for cloud identity engine directory synchronization. It would be relevant where NGFW and Prisma Access independently evaluate groups, producing different privileges for the same person. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C051; angle 1; architecture design; option considered: Architect a shared Cloud Identity Engine identity source and clearly mapped policies for each supported enforcement platform.
Question 202
Which validation most directly demonstrates cloud identity engine directory synchronization is correctly designed for Technology research institute? The security architecture board of Technology research institute is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Technology research institute: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
- For Technology research institute: Disable and restore the test sync agent and check freshness and mapping diagnostics.
- For Technology research institute: Generate a labeled log event and verify that the SIEM records it once or recognizes the duplicate copies.
- For Technology research institute: Change a test user's group assignment and verify sync state and resulting access decision.
Explanation
Correct Answer
D:This checks the relevant cloud identity engine directory synchronization enforcement path rather than a distant symptom. Change a test user's group assignment and verify sync state and resulting access decision. The expected evidence is Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C051; angle 2; architecture design; option considered: Change a test user's group assignment and verify sync state and resulting access decision.
Incorrect Answers
A:Strata Logging Service logging addresses a different architectural concern, such as when a cloud-managed branch fleet has inconsistent log retention and central investigations miss devices. It does not establish cloud identity engine directory synchronization here. The decisive test is to change a test user's group assignment and verify sync state and resulting access decision.
B:This option addresses a different design objective: On-premises identity directory bridge, not the primary control for cloud identity engine directory synchronization. It would be relevant where An enterprise's authoritative directory remains on premises and direct inbound exposure of domain controllers is forbidden. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C051; angle 2; architecture design; option considered: Disable and restore the test sync agent and check freshness and mapping diagnostics.
C:Log duplication in redundant collectors addresses a different architectural concern, such as when a security analytics pipeline double counts events when both redundant collector copies are forwarded. It does not establish cloud identity engine directory synchronization here. The decisive test is to change a test user's group assignment and verify sync state and resulting access decision.
Question 203
Which design assumption should the architect REJECT when evaluating cloud identity engine directory synchronization for Technology research institute? The security architecture board of Technology research institute is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Technology research institute: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
- For Technology research institute: Change a test user's group assignment and verify sync state and resulting access decision.
- For Technology research institute: Manually hardcode group membership in firewall address objects as a permanent solution.
- For Technology research institute: Identity-backed policy reflects approved directory group changes after the documented sync interval.
Explanation
Correct Answer
C:Reject this assumption: Manually hardcode group membership in firewall address objects as a permanent solution. It does not establish cloud identity engine directory synchronization; the supported architecture is Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. Verify it by: Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C051; angle 3; architecture design; option considered: Manually hardcode group membership in firewall address objects as a permanent solution.
Incorrect Answers
A:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. It is consistent with the required outcome: Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C051; angle 3; architecture design; option considered: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
B:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Change a test user's group assignment and verify sync state and resulting access decision. It is consistent with the required outcome: Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C051; angle 3; architecture design; option considered: Change a test user's group assignment and verify sync state and resulting access decision.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Identity-backed policy reflects approved directory group changes after the documented sync interval. It is consistent with the required outcome: Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C051; angle 3; architecture design; option considered: Identity-backed policy reflects approved directory group changes after the documented sync interval.
Question 204
Which measurable end state best satisfies the stated cloud identity engine directory synchronization requirement for Technology research institute? The security architecture board of Technology research institute is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Technology research institute: Cloud policy receives on-premises directory identities through a supported protected integration.
- For Technology research institute: Required events reach the SIEM through an authenticated encrypted transport.
- For Technology research institute: Identity-backed policy reflects approved directory group changes after the documented sync interval.
- For Technology research institute: Management can recover from a peer outage with known control-plane behavior and documented log-path exceptions.
Explanation
Correct Answer
C:The required result is identity-backed policy reflects approved directory group changes after the documented sync interval. Apply this control: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. Verify with: Change a test user's group assignment and verify sync state and resulting access decision.
Incorrect Answers
A:This option addresses a different design objective: On-premises identity directory bridge, not the primary control for cloud identity engine directory synchronization. It would be relevant where An enterprise's authoritative directory remains on premises and direct inbound exposure of domain controllers is forbidden. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C051; angle 4; architecture design; option considered: Cloud policy receives on-premises directory identities through a supported protected integration.
B:This option addresses a different design objective: Secure external syslog integration, not the primary control for cloud identity engine directory synchronization. It would be relevant where Compliance requires copies of select firewall events at an external SIEM but the current feed is cleartext. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C051; angle 4; architecture design; option considered: Required events reach the SIEM through an authenticated encrypted transport.
D:Panorama management HA addresses a different architectural concern, such as when a single Panorama management appliance is a change-control outage risk for managed regional firewalls. It does not establish cloud identity engine directory synchronization here. The decisive test is to change a test user's group assignment and verify sync state and resulting access decision.
Question 205
For EMEA public university, which is the most directly supported architectural control for cloud identity engine directory synchronization? After EMEA public university completed a limited security transformation pilot, reviewers observed a control gap: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For EMEA public university: Adopt a documented supported noninteractive Okta integration method and rotate app credentials under owner control.
- For EMEA public university: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
- For EMEA public university: Architect a shared Cloud Identity Engine identity source and clearly mapped policies for each supported enforcement platform.
- For EMEA public university: Design supported log forwarding with TLS-protected syslog and appropriate certificates and destination policy.
Explanation
Correct Answer
B:This directly addresses the recorded gap: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. The architectural control is Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. The decisive test is Change a test user's group assignment and verify sync state and resulting access decision. The objective is Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C052; angle 1; post-pilot control gap; option considered: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
Incorrect Answers
A:This option addresses a different design objective: Okta directory service credentials, not the primary control for cloud identity engine directory synchronization. It would be relevant where An Okta directory sync deployment needs stable unattended operation, but its interactive authorization expires repeatedly. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C052; angle 1; post-pilot control gap; option considered: Adopt a documented supported noninteractive Okta integration method and rotate app credentials under owner control.
C:This option addresses a different design objective: Cross-platform identity policy consistency, not the primary control for cloud identity engine directory synchronization. It would be relevant where NGFW and Prisma Access independently evaluate groups, producing different privileges for the same person. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C052; angle 1; post-pilot control gap; option considered: Architect a shared Cloud Identity Engine identity source and clearly mapped policies for each supported enforcement platform.
D:This option addresses a different design objective: Secure external syslog integration, not the primary control for cloud identity engine directory synchronization. It would be relevant where Compliance requires copies of select firewall events at an external SIEM but the current feed is cleartext. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C052; angle 1; post-pilot control gap; option considered: Design supported log forwarding with TLS-protected syslog and appropriate certificates and destination policy.
Question 206
Which validation most directly demonstrates cloud identity engine directory synchronization is correctly designed for EMEA public university? After EMEA public university completed a limited security transformation pilot, reviewers observed a control gap: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For EMEA public university: Change a test user's group assignment and verify sync state and resulting access decision.
- For EMEA public university: Capture a test forwarding session and verify TLS and SIEM ingestion with valid event fields.
- For EMEA public university: Run a controlled log-ingestion load test and measure drops, latency, and Panorama management responsiveness.
- For EMEA public university: Generate test threat and traffic events and confirm arrival at the correct collector destinations.
Explanation
Correct Answer
A:This checks the relevant cloud identity engine directory synchronization enforcement path rather than a distant symptom. Change a test user's group assignment and verify sync state and resulting access decision. The expected evidence is Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C052; angle 2; post-pilot control gap; option considered: Change a test user's group assignment and verify sync state and resulting access decision.
Incorrect Answers
B:This option addresses a different design objective: Secure external syslog integration, not the primary control for cloud identity engine directory synchronization. It would be relevant where Compliance requires copies of select firewall events at an external SIEM but the current feed is cleartext. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C052; angle 2; post-pilot control gap; option considered: Capture a test forwarding session and verify TLS and SIEM ingestion with valid event fields.
C:Distributed log collection addresses a different architectural concern, such as when a central Panorama server is CPU-constrained by high-volume security logs from remote regions. It does not establish cloud identity engine directory synchronization here. The decisive test is to change a test user's group assignment and verify sync state and resulting access decision.
D:Collector forwarding preferences addresses a different architectural concern, such as when new firewalls are registered in Panorama but their logs do not reach the intended regional collector group. It does not establish cloud identity engine directory synchronization here. The decisive test is to change a test user's group assignment and verify sync state and resulting access decision.
Question 207
Which design assumption should the architect REJECT when evaluating cloud identity engine directory synchronization for EMEA public university? After EMEA public university completed a limited security transformation pilot, reviewers observed a control gap: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For EMEA public university: Identity-backed policy reflects approved directory group changes after the documented sync interval.
- For EMEA public university: Manually hardcode group membership in firewall address objects as a permanent solution.
- For EMEA public university: Change a test user's group assignment and verify sync state and resulting access decision.
- For EMEA public university: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
Explanation
Correct Answer
B:Reject this assumption: Manually hardcode group membership in firewall address objects as a permanent solution. It does not establish cloud identity engine directory synchronization; the supported architecture is Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. Verify it by: Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C052; angle 3; post-pilot control gap; option considered: Manually hardcode group membership in firewall address objects as a permanent solution.
Incorrect Answers
A:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Identity-backed policy reflects approved directory group changes after the documented sync interval. It is consistent with the required outcome: Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C052; angle 3; post-pilot control gap; option considered: Identity-backed policy reflects approved directory group changes after the documented sync interval.
C:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Change a test user's group assignment and verify sync state and resulting access decision. It is consistent with the required outcome: Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C052; angle 3; post-pilot control gap; option considered: Change a test user's group assignment and verify sync state and resulting access decision.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. It is consistent with the required outcome: Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C052; angle 3; post-pilot control gap; option considered: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
Question 208
Select TWO directly linked controls for EMEA public university: the architectural remedy and its decisive validation. After EMEA public university completed a limited security transformation pilot, reviewers observed a control gap: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For EMEA public university: Adopt a documented supported noninteractive Okta integration method and rotate app credentials under owner control.
- For EMEA public university: Disable and restore the test sync agent and check freshness and mapping diagnostics.
- For EMEA public university: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
- For EMEA public university: Change a test user's group assignment and verify sync state and resulting access decision.
- For EMEA public university: Manually hardcode group membership in firewall address objects as a permanent solution.
Explanation
Correct Answer
C:This directly addresses the recorded gap: Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. The architectural control is Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior. The decisive test is Change a test user's group assignment and verify sync state and resulting access decision. The objective is Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C052; angle 4; post-pilot control gap; option considered: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
D:This checks the relevant cloud identity engine directory synchronization enforcement path rather than a distant symptom. Change a test user's group assignment and verify sync state and resulting access decision. The expected evidence is Identity-backed policy reflects approved directory group changes after the documented sync interval. Case R152-C052; angle 4; post-pilot control gap; option considered: Change a test user's group assignment and verify sync state and resulting access decision.
Incorrect Answers
A:This option addresses a different design objective: Okta directory service credentials, not the primary control for cloud identity engine directory synchronization. It would be relevant where An Okta directory sync deployment needs stable unattended operation, but its interactive authorization expires repeatedly. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C052; angle 4; post-pilot control gap; option considered: Adopt a documented supported noninteractive Okta integration method and rotate app credentials under owner control.
B:This option addresses a different design objective: On-premises identity directory bridge, not the primary control for cloud identity engine directory synchronization. It would be relevant where An enterprise's authoritative directory remains on premises and direct inbound exposure of domain controllers is forbidden. Here the necessary evidence is Change a test user's group assignment and verify sync state and resulting access decision. Case R152-C052; angle 4; post-pilot control gap; option considered: Disable and restore the test sync agent and check freshness and mapping diagnostics.
E:This is an unsafe or insufficient shortcut for cloud identity engine directory synchronization: Manually hardcode group membership in firewall address objects as a permanent solution. The scoped requirement instead calls for Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
Question 209
For Multinational retail company, which is the most directly supported architectural control for on-premises identity directory bridge? The security architecture board of Multinational retail company is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: An enterprise's authoritative directory remains on premises and direct inbound exposure of domain controllers is forbidden. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Multinational retail company: Design supported log forwarding with TLS-protected syslog and appropriate certificates and destination policy.
- For Multinational retail company: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
- For Multinational retail company: Plan a collector forwarding or downstream deduplication strategy using stable event identifiers.
- For Multinational retail company: Choose the supported Cloud Identity Agent directory synchronization pattern with appropriate outbound connectivity.
Explanation
Correct Answer
D:This directly addresses the recorded gap: An enterprise's authoritative directory remains on premises and direct inbound exposure of domain controllers is forbidden. The architectural control is Choose the supported Cloud Identity Agent directory synchronization pattern with appropriate outbound connectivity. The decisive test is Disable and restore the test sync agent and check freshness and mapping diagnostics. The objective is Cloud policy receives on-premises directory identities through a supported protected integration. Case R152-C053; angle 1; architecture design; option considered: Choose the supported Cloud Identity Agent directory synchronization pattern with appropriate outbound connectivity.
Incorrect Answers
A:This option addresses a different design objective: Secure external syslog integration, not the primary control for on-premises identity directory bridge. It would be relevant where Compliance requires copies of select firewall events at an external SIEM but the current feed is cleartext. Here the necessary evidence is Disable and restore the test sync agent and check freshness and mapping diagnostics. Case R152-C053; angle 1; architecture design; option considered: Design supported log forwarding with TLS-protected syslog and appropriate certificates and destination policy.
B:This option addresses a different design objective: Cloud Identity Engine directory synchronization, not the primary control for on-premises identity directory bridge. It would be relevant where Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. Here the necessary evidence is Disable and restore the test sync agent and check freshness and mapping diagnostics. Case R152-C053; angle 1; architecture design; option considered: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
C:This option addresses a different design objective: Log duplication in redundant collectors, not the primary control for on-premises identity directory bridge. It would be relevant where A security analytics pipeline double counts events when both redundant collector copies are forwarded. Here the necessary evidence is Disable and restore the test sync agent and check freshness and mapping diagnostics. Case R152-C053; angle 1; architecture design; option considered: Plan a collector forwarding or downstream deduplication strategy using stable event identifiers.
Question 210
Which validation most directly demonstrates on-premises identity directory bridge is correctly designed for Multinational retail company? The security architecture board of Multinational retail company is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: An enterprise's authoritative directory remains on premises and direct inbound exposure of domain controllers is forbidden. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Multinational retail company: Disable and restore the test sync agent and check freshness and mapping diagnostics.
- For Multinational retail company: Generate test threat and traffic events and confirm arrival at the correct collector destinations.
- For Multinational retail company: Perform a planned failover exercise while reviewing management access and configuration synchronization.
- For Multinational retail company: Run a controlled log-ingestion load test and measure drops, latency, and Panorama management responsiveness.
Explanation
Correct Answer
A:This checks the relevant on-premises identity directory bridge enforcement path rather than a distant symptom. Disable and restore the test sync agent and check freshness and mapping diagnostics. The expected evidence is Cloud policy receives on-premises directory identities through a supported protected integration. Case R152-C053; angle 2; architecture design; option considered: Disable and restore the test sync agent and check freshness and mapping diagnostics.
Incorrect Answers
B:This option addresses a different design objective: Collector forwarding preferences, not the primary control for on-premises identity directory bridge. It would be relevant where New firewalls are registered in Panorama but their logs do not reach the intended regional collector group. Here the necessary evidence is Disable and restore the test sync agent and check freshness and mapping diagnostics. Case R152-C053; angle 2; architecture design; option considered: Generate test threat and traffic events and confirm arrival at the correct collector destinations.
C:This option addresses a different design objective: Panorama management HA, not the primary control for on-premises identity directory bridge. It would be relevant where A single Panorama management appliance is a change-control outage risk for managed regional firewalls. Here the necessary evidence is Disable and restore the test sync agent and check freshness and mapping diagnostics. Case R152-C053; angle 2; architecture design; option considered: Perform a planned failover exercise while reviewing management access and configuration synchronization.
D:Distributed log collection addresses a different architectural concern, such as when a central Panorama server is CPU-constrained by high-volume security logs from remote regions. It does not establish on-premises identity directory bridge here. The decisive test is to disable and restore the test sync agent and check freshness and mapping diagnostics.
Palo Alto Networks Network Security Architect (NetSec-Architect) Practice Tests