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

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

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

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

NetSec-Architect Premium ETE File


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

Palo Alto Networks NetSec-Architect Practice Test 15

Question 140

At fictional Willowstone Energy IT, the security design for cross-region centralized management and iam design validation during staged modernization faces: An architect-owned security exception is overwritten by a broad shared snippet in Strata Cloud Manager. Diagnostic evidence: Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. Proposed design change: Design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push. Which independent observation would demonstrate that the change met its intended outcome?

  1. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, A test policy change affects only the intended branch, and a peer branch retains its approved effective policy.
  2. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, A synthetic managed branch client is attributed to a device class and intended group while unknown devices trigger review.
  3. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, During a simulated node outage, the standby management plane takes over and can perform a controlled device-group policy workflow.
  4. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, An updated test group membership yields the same authorized and denied access result across both paths within an agreed window.

Explanation

Correct Answer

A:

Verify the change by checking: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy. The test is tied to the original clue: effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. The correction being tested is: Design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push.

Incorrect Answers

B:

An alternative check—A synthetic managed branch client is attributed to a device class and intended group while unknown devices trigger review—is not sufficient closure evidence for this fault. The relevant acceptance test is: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy. Centralized policy inheritance requires an explicit responsibility and precedence model.

C:

A different check—during a simulated node outage, the standby management plane takes over and can perform a controlled device-group policy workflow—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy. This tests the condition shown by effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application.

D:

An alternative result would show that an updated test group membership yields the same authorized and denied access result across both paths within an agreed window; it measures a different outcome. To check this fault, verify: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy. The earlier evidence was that effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application.

Question 141

For the architecture board of fictional Willowstone Energy IT, a proposed change to cross-region centralized management and iam design validation during staged modernization follows this problem: An architect-owned security exception is overwritten by a broad shared snippet in Strata Cloud Manager. Discriminating observation: Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. Which network security architecture principle best explains why the existing design is insufficient?

  1. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.
  2. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Centralized policy inheritance requires an explicit responsibility and precedence model.
  3. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Central identity and device context improve network enforcement without assuming every endpoint is a managed employee laptop.
  4. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Consistent distributed authorization requires common identity semantics and freshness across enforcement points.

Explanation

Correct Answer

B:

Centralized policy inheritance requires an explicit responsibility and precedence model. In the reported case, effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. The remedy follows that mechanism: Design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push.

Incorrect Answers

A:

At Willowstone Energy IT, the cited mechanism, identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup, does not account for the recorded clue. Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. Centralized policy inheritance requires an explicit responsibility and precedence model.

C:

At Willowstone Energy IT, the offered principle is that central identity and device context improve network enforcement without assuming every endpoint is a managed employee laptop, but this is not the mechanism shown here. This case reports that effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. Its governing principle is that centralized policy inheritance requires an explicit responsibility and precedence model.

D:

The cited mechanism, consistent distributed authorization requires common identity semantics and freshness across enforcement points, does not account for the recorded clue. Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. Centralized policy inheritance requires an explicit responsibility and precedence model.

Question 142

At fictional Willowstone Energy IT, the design team must verify failure behavior and compliance without expanding unnecessary application exposure. Architecture risk: An architect-owned security exception is overwritten by a broad shared snippet in Strata Cloud Manager. Evidence: Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. Which narrowly scoped design action AND separately measurable postchange confirmation together form the most defensible response?

  1. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Design action: Design supported identity telemetry and device mapping integration with centrally consistent controls and secured collection. Independent proof: A synthetic managed branch client is attributed to a device class and intended group while unknown devices trigger review.
  2. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Design action: Design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push. Independent proof: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy.
  3. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Design action: Architect redundant log collectors and supported forwarding/retention design across failure domains with controlled logging capacity. Independent proof: An isolated collector failure preserves ingestion and search of required test events within the stated recovery target.
  4. For Willowstone Energy IT and the scm policy inheritance creates conflicting site exception assessment, Design action: Architect consistent identity source and sync health monitoring across Cloud Identity Engine, NGFW and Prisma Access enforcement. Independent proof: An updated test group membership yields the same authorized and denied access result across both paths within an agreed window.

Explanation

Correct Answer

B:

Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. The paired correction is to design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push. Validate its effect with: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy. Centralized policy inheritance requires an explicit responsibility and precedence model.

Incorrect Answers

A:

The offered action and verification—design supported identity telemetry and device mapping integration with centrally consistent controls and secured collection—do not establish closure of the stated failure. The case evidence is that effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. The relevant response is to design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push. Check its effect against: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy.

C:

At Willowstone Energy IT, this pair does not address the recorded clue: effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. The scoped correction is to design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push. Confirm success using: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy.

D:

The offered action and verification—architect consistent identity source and sync health monitoring across Cloud Identity Engine, NGFW and Prisma Access enforcement—do not establish closure of the stated failure. The case evidence is that effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application. The relevant response is to design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push. Check its effect against: A test policy change affects only the intended branch, and a peer branch retains its approved effective policy.

Question 143

At fictional Oakbridge Retail Technology, the architecture team is responsible for centralized management and iam design, continuity, policy and architecture governance and must preserve least privilege, auditable change and measurable business availability. Risk case: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Verified finding: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Which scoped architecture decision most directly addresses the documented control gap without unnecessarily changing other services?

  1. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Architect redundant log collectors and supported forwarding/retention design across failure domains with controlled logging capacity.
  2. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Architect encrypted authenticated SLS integration, source normalization and deduplicated event forwarding with least-privilege delivery.
  3. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push.
  4. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

Explanation

Correct Answer

D:

The evidence is that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The appropriate change is to design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards, because identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup. After the change, A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.

Incorrect Answers

A:

One alternative is to architect redundant log collectors and supported forwarding/retention design across failure domains with controlled logging capacity, but this does not address the decisive finding: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Instead, the correction is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Check the result using: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.

B:

An alternative operation—architect encrypted authenticated SLS integration, source normalization and deduplicated event forwarding with least-privilege delivery—does not directly resolve the recorded failure. Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The appropriate intervention is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

C:

The proposed change—design scoped folder and snippet ownership, change-review rules and predictable inheritance before the final policy push—does not repair the condition documented in the case. The decisive evidence is that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The necessary change is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

Question 144

For fictional Oakbridge Retail Technology, architects investigating centralized management and iam design, continuity, policy and architecture governance observe this risk: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Before making broad configuration or topology changes, which finding most directly isolates the failure mechanism?

  1. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Prisma SD-WAN event and Cloud Identity Engine mapping logs show branch subnets have no trusted identity correlation source.
  2. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application.
  3. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date.
  4. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Correlation of Cloud Identity Engine timestamps shows remote-access nodes use an outdated group-membership snapshot.

Explanation

Correct Answer

C:

The record shows that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup. The corresponding correction is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

Incorrect Answers

A:

An alternative finding indicates that prisma SD-WAN event and Cloud Identity Engine mapping logs show branch subnets have no trusted identity correlation source; this is not the controlling evidence in the report. Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The appropriate correction is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

B:

A different observation—effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application—does not establish the specific fault described here. The record instead shows this: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

D:

An alternative finding indicates that correlation of Cloud Identity Engine timestamps shows remote-access nodes use an outdated group-membership snapshot; this is not the controlling evidence in the report. Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The appropriate correction is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

Question 145

At fictional Oakbridge Retail Technology, the security design for centralized management and iam design, continuity, policy and architecture governance faces: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Diagnostic evidence: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Proposed design change: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Which independent observation would demonstrate that the change met its intended outcome?

  1. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, An isolated collector failure preserves ingestion and search of required test events within the stated recovery target.
  2. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, During a simulated node outage, the standby management plane takes over and can perform a controlled device-group policy workflow.
  3. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.
  4. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, A synthetic managed branch client is attributed to a device class and intended group while unknown devices trigger review.

Explanation

Correct Answer

C:

A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. This post-change check addresses the recorded finding: cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

Incorrect Answers

A:

A different check—an isolated collector failure preserves ingestion and search of required test events within the stated recovery target—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. This tests the condition shown by cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date.

B:

An alternative result would show that during a simulated node outage, the standby management plane takes over and can perform a controlled device-group policy workflow; it measures a different outcome. To check this fault, verify: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. The earlier evidence was that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date.

D:

A different check—A synthetic managed branch client is attributed to a device class and intended group while unknown devices trigger review—would not demonstrate that this particular failure was corrected. Acceptance instead requires this result: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. This tests the condition shown by cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date.

Question 146

For the architecture board of fictional Oakbridge Retail Technology, a proposed change to centralized management and iam design, continuity, policy and architecture governance follows this problem: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Discriminating observation: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Which network security architecture principle best explains why the existing design is insufficient?

  1. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Consistent distributed authorization requires common identity semantics and freshness across enforcement points.
  2. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Security telemetry needs integrity, confidentiality and chain of custody in addition to availability.
  3. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.
  4. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Central identity and device context improve network enforcement without assuming every endpoint is a managed employee laptop.

Explanation

Correct Answer

C:

The governing principle is: Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup. The case specifically shows cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The corresponding change is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

Incorrect Answers

A:

An alternative principle holds that consistent distributed authorization requires common identity semantics and freshness across enforcement points, but this is not the mechanism shown here. This case reports that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Its governing principle is that identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

B:

The cited mechanism, security telemetry needs integrity, confidentiality and chain of custody in addition to availability, does not account for the recorded clue. Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

D:

An alternative principle holds that central identity and device context improve network enforcement without assuming every endpoint is a managed employee laptop, but this is not the mechanism shown here. This case reports that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Its governing principle is that identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

Question 147

At fictional Oakbridge Retail Technology, the design team must preserve least privilege, auditable change and measurable business availability. Architecture risk: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Evidence: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Which narrowly scoped design action AND separately measurable postchange confirmation together form the most defensible response?

  1. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Design action: Design supported identity telemetry and device mapping integration with centrally consistent controls and secured collection. Independent proof: A synthetic managed branch client is attributed to a device class and intended group while unknown devices trigger review.
  2. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Design action: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Independent proof: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.
  3. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Design action: Architect redundant log collectors and supported forwarding/retention design across failure domains with controlled logging capacity. Independent proof: An isolated collector failure preserves ingestion and search of required test events within the stated recovery target.
  4. For Oakbridge Retail Technology and the cloud identity engine directory sync misses contractors assessment, Design action: Design Panorama HA with supported synchronization, controlled failover roles and an explicit restoration procedure. Independent proof: During a simulated node outage, the standby management plane takes over and can perform a controlled device-group policy workflow.

Explanation

Correct Answer

B:

The proposed action is to design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Independent verification is: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. That pair addresses the actual recorded clue: cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date.

Incorrect Answers

A:

This pair does not resolve the recorded clue: cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The scoped correction is to design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Confirm success using: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.

C:

That alternative would test a different outcome: architect redundant log collectors and supported forwarding/retention design across failure domains with controlled logging capacity. Here, cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The paired response is to design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Its acceptance check is: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.

D:

At Oakbridge Retail Technology, this pair does not address the recorded clue: cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The scoped correction is to design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Confirm success using: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.

Question 148

At fictional Asteria Health Partners, the architecture team is responsible for cross-region centralized management and iam design validation during staged modernization and must verify failure behavior and compliance without expanding unnecessary application exposure. Risk case: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Verified finding: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Which scoped architecture decision most directly addresses the documented control gap without unnecessarily changing other services?

  1. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Design supported identity telemetry and device mapping integration with centrally consistent controls and secured collection.
  2. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Design Cloud Identity Engine and authentication profile claim mapping using stable unique identities with signed assertions and group context.
  3. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.
  4. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Architect encrypted authenticated SLS integration, source normalization and deduplicated event forwarding with least-privilege delivery.

Explanation

Correct Answer

C:

Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup. The direct correction is to design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Verify the outcome with: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.

Incorrect Answers

A:

The proposed change—design supported identity telemetry and device mapping integration with centrally consistent controls and secured collection—does not repair the condition documented in the case. The decisive evidence is that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The necessary change is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

B:

One alternative is to design Cloud Identity Engine and authentication profile claim mapping using stable unique identities with signed assertions and group context, but this does not address the decisive finding: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Instead, the correction is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Check the result using: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.

D:

The proposed change—architect encrypted authenticated SLS integration, source normalization and deduplicated event forwarding with least-privilege delivery—does not repair the condition documented in the case. The decisive evidence is that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The necessary change is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

Question 149

For fictional Asteria Health Partners, architects investigating cross-region centralized management and iam design validation during staged modernization observe this risk: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Before making broad configuration or topology changes, which finding most directly isolates the failure mechanism?

  1. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application.
  2. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Strata Logging Service forwarding settings show unsigned receiver configuration and no TLS peer validation for the selected integration.
  3. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Prisma SD-WAN event and Cloud Identity Engine mapping logs show branch subnets have no trusted identity correlation source.
  4. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date.

Explanation

Correct Answer

D:

The evidence shows that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup. The direct correction is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

Incorrect Answers

A:

A competing observation indicates that effective configuration and commit diff show global folder snippet precedence overrides the intended branch policy for one application, which points away from this case. The distinguishing evidence is: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. That is consistent with the mechanism: identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

B:

An alternative finding indicates that strata Logging Service forwarding settings show unsigned receiver configuration and no TLS peer validation for the selected integration; this is not the controlling evidence in the report. Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. The appropriate correction is: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards.

C:

A different observation—prisma SD-WAN event and Cloud Identity Engine mapping logs show branch subnets have no trusted identity correlation source—does not establish the specific fault described here. The record instead shows this: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

Question 150

At fictional Asteria Health Partners, the security design for cross-region centralized management and iam design validation during staged modernization faces: Contractors recently removed from the identity provider still appear entitled in security enforcement after a directory sync delay. Diagnostic evidence: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Proposed design change: Design monitored directory synchronization with appropriate Entra/Okta/SAML source authority, redundancy and stale-identity safeguards. Which independent observation would demonstrate that the change met its intended outcome?

  1. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, A test policy change affects only the intended branch, and a peer branch retains its approved effective policy.
  2. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized.
  3. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, During a simulated node outage, the standby management plane takes over and can perform a controlled device-group policy workflow.
  4. For Asteria Health Partners and the cloud identity engine directory sync misses contractors assessment, An updated test group membership yields the same authorized and denied access result across both paths within an agreed window.

Explanation

Correct Answer

B:

Verify the result with: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. This tests the correction against the actual evidence: Cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

Incorrect Answers

A:

An alternative check—A test policy change affects only the intended branch, and a peer branch retains its approved effective policy—is not sufficient closure evidence for this fault. The relevant acceptance test is: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

C:

At Asteria Health Partners, the suggested result is that during a simulated node outage, the standby management plane takes over and can perform a controlled device-group policy workflow; it measures a different outcome. To check this fault, verify: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. The earlier evidence was that cloud Identity Engine connector health shows the on-premises directory agent is stalled while the SaaS identity source remains up to date.

D:

An alternative check—an updated test group membership yields the same authorized and denied access result across both paths within an agreed window—is not sufficient closure evidence for this fault. The relevant acceptance test is: A revoked test identity disappears from policy mappings in the target interval while permitted users remain synchronized. Identity mapping freshness is a necessary property of least-privilege policy, not a one-time integration setup.

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