100% Latest & Updated Palo Alto Networks NetSec-Architect Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 190
Which validation most directly demonstrates scm management scoping is correctly designed for Multinational retail company? After Multinational retail company completed a limited security transformation pilot, reviewers observed a control gap: A multinational organization needs centralized security policy with regional policy exceptions and clear administration boundaries. 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 Multinational retail company: Use the same test identities against both enforcement points and compare policy results.
- For Multinational retail company: Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
- For Multinational retail company: Change a test user's group assignment and verify sync state and resulting access decision.
- For Multinational retail company: Observe a scheduled sync past the previous interactive token window and review authentication audit events.
Explanation
Correct Answer
B:This checks the relevant scm management scoping enforcement path rather than a distant symptom. Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. The expected evidence is Global standards remain consistent while regional administrators cannot alter other regions' scope. Case R152-C048; angle 2; post-pilot control gap; option considered: Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
Incorrect Answers
A:Cross-platform identity policy consistency addresses a different architectural concern, such as when NGFW and Prisma Access independently evaluate groups, producing different privileges for the same person. It does not establish scm management scoping here. The decisive test is to have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
C:This option addresses a different design objective: Cloud Identity Engine directory synchronization, not the primary control for scm management scoping. It would be relevant where Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. Here the necessary evidence is Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. Case R152-C048; angle 2; post-pilot control gap; option considered: Change a test user's group assignment and verify sync state and resulting access decision.
D:Okta directory service credentials addresses a different architectural concern, such as when an Okta directory sync deployment needs stable unattended operation, but its interactive authorization expires repeatedly. It does not establish scm management scoping here. The decisive test is to have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
Question 191
Which design assumption should the architect REJECT when evaluating scm management scoping for Multinational retail company? After Multinational retail company completed a limited security transformation pilot, reviewers observed a control gap: A multinational organization needs centralized security policy with regional policy exceptions and clear administration boundaries. 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 Multinational retail company: Grant all administrators a global superuser role to avoid planning delegation.
- For Multinational retail company: Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides.
- For Multinational retail company: Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
- For Multinational retail company: Global standards remain consistent while regional administrators cannot alter other regions' scope.
Explanation
Correct Answer
A:Reject this assumption: Grant all administrators a global superuser role to avoid planning delegation. It does not establish scm management scoping; the supported architecture is Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides. Verify it by: Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. Case R152-C048; angle 3; post-pilot control gap; option considered: Grant all administrators a global superuser role to avoid planning delegation.
Incorrect Answers
B:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides. It is consistent with the required outcome: Global standards remain consistent while regional administrators cannot alter other regions' scope. Case R152-C048; angle 3; post-pilot control gap; option considered: Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides.
C:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. It is consistent with the required outcome: Global standards remain consistent while regional administrators cannot alter other regions' scope. Case R152-C048; angle 3; post-pilot control gap; option considered: Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Global standards remain consistent while regional administrators cannot alter other regions' scope. It is consistent with the required outcome: Global standards remain consistent while regional administrators cannot alter other regions' scope. Case R152-C048; angle 3; post-pilot control gap; option considered: Global standards remain consistent while regional administrators cannot alter other regions' scope.
Question 192
Select TWO directly linked controls for Multinational retail company: the architectural remedy and its decisive validation. After Multinational retail company completed a limited security transformation pilot, reviewers observed a control gap: A multinational organization needs centralized security policy with regional policy exceptions and clear administration boundaries. 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 Multinational retail company: Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides.
- For Multinational retail company: Place dedicated log collectors and appropriate collector groups near relevant firewall populations.
- For Multinational retail company: Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
- For Multinational retail company: Grant all administrators a global superuser role to avoid planning delegation.
- For Multinational retail company: Generate a labeled log event and verify that the SIEM records it once or recognizes the duplicate copies.
Explanation
Correct Answer
A:This directly addresses the recorded gap: A multinational organization needs centralized security policy with regional policy exceptions and clear administration boundaries. The architectural control is Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides. The decisive test is Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. The objective is Global standards remain consistent while regional administrators cannot alter other regions' scope. Case R152-C048; angle 4; post-pilot control gap; option considered: Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides.
C:This checks the relevant scm management scoping enforcement path rather than a distant symptom. Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. The expected evidence is Global standards remain consistent while regional administrators cannot alter other regions' scope. Case R152-C048; angle 4; post-pilot control gap; option considered: Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace.
Incorrect Answers
B:This option addresses a different design objective: Distributed log collection, not the primary control for scm management scoping. It would be relevant where A central Panorama server is CPU-constrained by high-volume security logs from remote regions. Here the necessary evidence is Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. Case R152-C048; angle 4; post-pilot control gap; option considered: Place dedicated log collectors and appropriate collector groups near relevant firewall populations.
D:This is an unsafe or insufficient shortcut for scm management scoping: Grant all administrators a global superuser role to avoid planning delegation. The scoped requirement instead calls for Design Strata Cloud Manager management scope and RBAC appropriate to shared baselines and regional overrides. Case R152-C048; angle 4; post-pilot control gap; option considered: Grant all administrators a global superuser role to avoid planning delegation.
E:This option addresses a different design objective: Log duplication in redundant collectors, not the primary control for scm management scoping. It would be relevant where A security analytics pipeline double counts events when both redundant collector copies are forwarded. Here the necessary evidence is Have two scoped administrators attempt authorized and out-of-scope policy changes in a test workspace. Case R152-C048; angle 4; post-pilot control gap; option considered: Generate a labeled log event and verify that the SIEM records it once or recognizes the duplicate copies.
Question 193
For Cloud-native manufacturing firm, which is the most directly supported architectural control for strata logging service logging? The security architecture board of Cloud-native manufacturing firm is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: A cloud-managed branch fleet has inconsistent log retention and central investigations miss devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
- For Cloud-native manufacturing firm: Architect a shared Cloud Identity Engine identity source and clearly mapped policies for each supported enforcement platform.
- For Cloud-native manufacturing firm: Design a supported Panorama HA pair with tested synchronization and operational failover responsibilities.
- For Cloud-native manufacturing firm: Configure supported collector group log redundancy with model/disk and capacity requirements documented.
Explanation
Correct Answer
A: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-C049; angle 1; architecture design; option considered: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
Incorrect Answers
B:Cross-platform identity policy consistency addresses a different architectural concern, such as when NGFW and Prisma Access independently evaluate groups, producing different privileges for the same person. 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.
C:This option addresses a different design objective: Panorama management HA, not the primary control for strata logging service logging. 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 Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C049; angle 1; architecture design; option considered: Design a supported Panorama HA pair with tested synchronization and operational failover responsibilities.
D:Collector log redundancy addresses a different architectural concern, such as when a collector failure causes missing audit records even though two collector appliances were purchased. 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 194
Which validation most directly demonstrates strata logging service logging is correctly designed for Cloud-native manufacturing firm? The security architecture board of Cloud-native manufacturing firm is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: A cloud-managed branch fleet has inconsistent log retention and central investigations miss devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
- For Cloud-native manufacturing firm: Change a test user's group assignment and verify sync state and resulting access decision.
- For Cloud-native manufacturing firm: Perform a planned failover exercise while reviewing management access and configuration synchronization.
- For Cloud-native manufacturing firm: Sign in as a known test user and correlate authentication, mapping and policy logs end to end.
Explanation
Correct Answer
A: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-C049; angle 2; architecture design; option considered: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
Incorrect Answers
B:This option addresses a different design objective: Cloud Identity Engine directory synchronization, not the primary control for strata logging service logging. It would be relevant where Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. Here the necessary evidence is Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C049; angle 2; architecture design; option considered: Change a test user's group assignment and verify sync state and resulting access decision.
C:This option addresses a different design objective: Panorama management HA, not the primary control for strata logging service logging. 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 Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C049; angle 2; architecture design; option considered: Perform a planned failover exercise while reviewing management access and configuration synchronization.
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-C049; angle 2; architecture design; option considered: Sign in as a known test user and correlate authentication, mapping and policy logs end to end.
Question 195
Which design assumption should the architect REJECT when evaluating strata logging service logging for Cloud-native manufacturing firm? The security architecture board of Cloud-native manufacturing firm is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: A cloud-managed branch fleet has inconsistent log retention and central investigations miss devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Infer that enabling cloud management also guarantees infinite centralized log retention.
- For Cloud-native manufacturing firm: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
- For Cloud-native manufacturing firm: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
- For Cloud-native manufacturing firm: Investigators can retrieve expected events centrally under the approved retention design.
Explanation
Correct Answer
A:Reject this assumption: Infer that enabling cloud management also guarantees infinite centralized log retention. It does not establish strata logging service logging; the supported architecture is Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources. Verify it by: Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C049; angle 3; architecture design; option considered: Infer that enabling cloud management also guarantees infinite centralized log retention.
Incorrect Answers
B:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Generate labeled events from two firewall regions and validate central ingestion and retention behavior. It is consistent with the required outcome: Investigators can retrieve expected events centrally under the approved retention design. Case R152-C049; angle 3; architecture design; option considered: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
C:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources. It is consistent with the required outcome: Investigators can retrieve expected events centrally under the approved retention design. Case R152-C049; angle 3; architecture design; option considered: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Investigators can retrieve expected events centrally under the approved retention design. It is consistent with the required outcome: Investigators can retrieve expected events centrally under the approved retention design. Case R152-C049; angle 3; architecture design; option considered: Investigators can retrieve expected events centrally under the approved retention design.
Question 196
Select THREE linked elements for Cloud-native manufacturing firm: a supported architecture, the direct test, and the required outcome. The security architecture board of Cloud-native manufacturing firm is preparing a new Centralized Management and IAM program. The stakeholders have given the following specific requirement: A cloud-managed branch fleet has inconsistent log retention and central investigations miss devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
- For Cloud-native manufacturing firm: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
- For Cloud-native manufacturing firm: Required events reach the SIEM through an authenticated encrypted transport.
- For Cloud-native manufacturing firm: Plan a collector forwarding or downstream deduplication strategy using stable event identifiers.
- For Cloud-native manufacturing firm: Investigators can retrieve expected events centrally under the approved retention design.
- For Cloud-native manufacturing firm: Infer that enabling cloud management also guarantees infinite centralized log retention.
Explanation
Correct Answer
A: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-C049; angle 4; architecture design; option considered: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
B: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-C049; angle 4; architecture design; option considered: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
E: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-C049; angle 4; architecture design; option considered: Investigators can retrieve expected events centrally under the approved retention design.
Incorrect Answers
C:This option addresses a different design objective: Secure external syslog integration, not the primary control for strata logging service logging. 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 Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C049; angle 4; architecture design; option considered: Required events reach the SIEM through an authenticated encrypted transport.
D: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 strata logging service logging here. The decisive test is to generate labeled events from two firewall regions and validate central ingestion and retention behavior.
F: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-C049; angle 4; architecture design; option considered: Infer that enabling cloud management also guarantees infinite centralized log retention.
Question 197
For National health network, which is the most directly supported architectural control for strata logging service logging? 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: Use Cloud Identity Engine directory synchronization and examine source directory, refresh, and group-mapping behavior.
- For National health network: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
- For National health network: Design supported log forwarding with TLS-protected syslog and appropriate certificates and destination policy.
- For National health network: Place dedicated log collectors and appropriate collector groups near relevant firewall populations.
Explanation
Correct Answer
B: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 1; 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 option addresses a different design objective: Cloud Identity Engine directory synchronization, not the primary control for strata logging service logging. It would be relevant where Cloud-managed firewalls enforce stale group membership after a directory organizational restructure. Here the necessary evidence is Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C050; angle 1; post-pilot control gap; 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: Secure external syslog integration, not the primary control for strata logging service logging. 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 Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C050; angle 1; post-pilot control gap; option considered: Design supported log forwarding with TLS-protected syslog and appropriate certificates and destination policy.
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 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 198
Which validation most directly demonstrates strata logging service logging is correctly designed for National health network? 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: Sign in as a known test user and correlate authentication, mapping and policy logs end to end.
- For National health network: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
- For National health network: Perform a planned failover exercise while reviewing management access and configuration synchronization.
- For National health network: Observe a scheduled sync past the previous interactive token window and review authentication audit events.
Explanation
Correct Answer
B: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 2; post-pilot control gap; option considered: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
Incorrect Answers
A: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 2; post-pilot control gap; option considered: Sign in as a known test user and correlate authentication, mapping and policy logs end to end.
C:This option addresses a different design objective: Panorama management HA, not the primary control for strata logging service logging. 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 Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C050; angle 2; post-pilot control gap; option considered: Perform a planned failover exercise while reviewing management access and configuration synchronization.
D:Okta directory service credentials addresses a different architectural concern, such as when an Okta directory sync deployment needs stable unattended operation, but its interactive authorization expires repeatedly. 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 199
Which design assumption should the architect REJECT when evaluating strata logging service logging for National health network? 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: Investigators can retrieve expected events centrally under the approved retention design.
- For National health network: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
- For National health network: Infer that enabling cloud management also guarantees infinite centralized log retention.
- For National health network: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
Explanation
Correct Answer
C:Reject this assumption: Infer that enabling cloud management also guarantees infinite centralized log retention. It does not establish strata logging service logging; the supported architecture is Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources. Verify it by: Generate labeled events from two firewall regions and validate central ingestion and retention behavior. Case R152-C050; angle 3; post-pilot control gap; option considered: Infer that enabling cloud management also guarantees infinite centralized log retention.
Incorrect Answers
A:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Investigators can retrieve expected events centrally under the approved retention design. It is consistent with the required outcome: Investigators can retrieve expected events centrally under the approved retention design. Case R152-C050; angle 3; post-pilot control gap; option considered: Investigators can retrieve expected events centrally under the approved retention design.
B:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources. It is consistent with the required outcome: Investigators can retrieve expected events centrally under the approved retention design. Case R152-C050; angle 3; post-pilot control gap; option considered: Architect licensed Strata Logging Service collection and appropriate retention/integration for relevant NGFW and Prisma Access sources.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Generate labeled events from two firewall regions and validate central ingestion and retention behavior. It is consistent with the required outcome: Investigators can retrieve expected events centrally under the approved retention design. Case R152-C050; angle 3; post-pilot control gap; option considered: Generate labeled events from two firewall regions and validate central ingestion and retention behavior.
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.
Palo Alto Networks Network Security Architect (NetSec-Architect) Practice Tests