Practice Exams:

Palo Alto Networks NetSec-Architect Dumps

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

NetSec-Architect Premium ETE File


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

Palo Alto Networks NetSec-Architect Practice Test 20

Question 190

A healthcare provider must retain threat events through a Panorama collector outage and site-link disruption. Suppose the team implements this unsafe shortcut: Enable redundant logging on a single unpaired collector and claim all audit evidence survives its disk failure. Which concrete security or availability failure is most likely?

  1. A local exception can unintentionally alter security policy across unrelated subsidiaries
  2. Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load
  3. Compliance investigations fail because the chosen log path or retention does not meet agreed controls
  4. Directory exposure and identity drift create avoidable access-control risks

Answer & Explanations

Correct answer: B

A.

That outcome arises from a different failure: A local exception can unintentionally alter security policy across unrelated subsidiaries. The related situation is: A holding company manages cloud NGFW policies for three subsidiaries sharing global protection templates. In the present case: A healthcare provider must retain threat events through a Panorama collector outage and site-link disruption. The more pertinent consequence is: Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load. Prevent it by: Size Panorama log collectors and collector groups for ingestion, retention, redundancy and supported quorum behavior.

B.

Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load. This follows when the team chooses the shortcut: Enable redundant logging on a single unpaired collector and claim all audit evidence survives its disk failure. The situation is: A healthcare provider must retain threat events through a Panorama collector outage and site-link disruption. The correction is: Size Panorama log collectors and collector groups for ingestion, retention, redundancy and supported quorum behavior. The observable test is: Simulate one collector outage and verify log continuity, collector health and retained reports within performance targets.

C.

That outcome arises from a different failure: Compliance investigations fail because the chosen log path or retention does not meet agreed controls. The related situation is: An investment firm wants standardized cloud policy administration but regulated logs must reach its SIEM. In the present case: A healthcare provider must retain threat events through a Panorama collector outage and site-link disruption. The more pertinent consequence is: Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load. Prevent it by: Size Panorama log collectors and collector groups for ingestion, retention, redundancy and supported quorum behavior.

D.

That outcome arises from a different failure: Directory exposure and identity drift create avoidable access-control risks. The related situation is: A hospital maintains Active Directory in a private data center and needs group updates in cloud-managed NGFW policies. In the present case: A healthcare provider must retain threat events through a Panorama collector outage and site-link disruption. The more pertinent consequence is: Security events may disappear when a logging node fails or the design underestimates duplicated ingestion load. Prevent it by: Size Panorama log collectors and collector groups for ingestion, retention, redundancy and supported quorum behavior.

Question 191

A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. Which network security architecture decision best satisfies the business and technical requirements?

  1. Design a synchronized Panorama HA pair at separated failure domains with planned management failover validation
  2. Size Panorama log collectors and collector groups for ingestion, retention, redundancy and supported quorum behavior
  3. Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls
  4. Design SCM folders, snippets and variables with scoped inheritance and change approval across business units

Answer & Explanations

Correct answer: C

A.

This action would be appropriate when: A national retailer centralizes policy for hundreds of NGFWs and cannot tolerate one management VM failure. It follows from: Panorama HA protects central management availability, but forwarding firewalls still require their own independent HA and policy continuity design. The current case instead states: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The response it requires is: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

B.

The alternative action addresses a different condition: A bank needs redundant firewall logs across two data centers without loss during a collector maintenance. Its reasoning is: Log collector redundancy preserves duplicate evidence during node loss, while throughput and capacity change when duplicate logs consume additional storage. Here the case is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The more direct response is: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

C.

Apply: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. For the reported condition: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. This is appropriate because the preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration. Acceptance evidence: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

D.

This action would be appropriate when: A holding company manages cloud NGFW policies for three subsidiaries sharing global protection templates. It follows from: Cloud-managed shared policy can be inherited while scoped overrides prevent one subsidiary from changing another business unit's rules. The current case instead states: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The response it requires is: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

Question 192

A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. An architect proposes: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. Which technical explanation most directly supports that architecture?

  1. Cloud-managed shared policy can be inherited while scoped overrides prevent one subsidiary from changing another business unit's rules
  2. Central logging and cloud policy administration are related but distinct services with their own connectivity, retention, access and availability constraints
  3. The on-premises agent exchanges authorized identity attributes with cloud services where directory infrastructure cannot be directly reached
  4. The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration

Answer & Explanations

Correct answer: D

A.

This offered mechanism is relevant to Separate Strata Cloud Manager administration scopes for subsidiaries: Cloud-managed shared policy can be inherited while scoped overrides prevent one subsidiary from changing another business unit's rules. It explains the different task: Design SCM folders, snippets and variables with scoped inheritance and change approval across business units. The current condition is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. For that condition the operative principle is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

B.

This offered mechanism is relevant to Design independent Strata Logging Service retention and control plane integration: Central logging and cloud policy administration are related but distinct services with their own connectivity, retention, access and availability constraints. It explains the different task: Map Strata Logging Service ingestion, analytics consumers and authorized security operations exports independently from SCM policy authoring. The current condition is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. For that condition the operative principle is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

C.

This offered mechanism is relevant to Choose Cloud Identity Engine on-premises directory synchronization: The on-premises agent exchanges authorized identity attributes with cloud services where directory infrastructure cannot be directly reached. It explains the different task: Deploy an approved Cloud Identity Engine directory-sync agent with resilient connectivity to required local directory services. The current condition is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. For that condition the operative principle is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

D.

The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration. This causal relationship matters in: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. It supports the action: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. Test the result by: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

Question 193

A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability
  2. Modify a test user group in the local directory and verify permitted group changes reach relevant policy consumers
  3. Perform a test user sign-in, group change and deprovision to check propagated access decisions
  4. Cause a controlled threat log and confirm end-to-end encrypted receipt with expected parser fields

Answer & Explanations

Correct answer: A

A.

Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability. This evidence tests whether the response, Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls, addresses the specific condition: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The mechanism being tested is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

B.

That test checks a different intervention: Deploy an approved Cloud Identity Engine directory-sync agent with resilient connectivity to required local directory services. Its applicable setting is: A hospital maintains Active Directory in a private data center and needs group updates in cloud-managed NGFW policies. It would not directly establish the result required by: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The specific acceptance check here is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

C.

That test checks a different intervention: Configure Cloud Identity Engine integration with supported Entra ID or Okta identity sources and test SAML or cloud-directory group claims. Its applicable setting is: A SaaS-heavy enterprise uses Entra ID and wants role-based NGFW and Prisma Access policy. It would not directly establish the result required by: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The specific acceptance check here is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

D.

That test checks a different intervention: Select authenticated encrypted syslog over TLS or supported log export for a central SIEM with explicit retry and monitoring design. Its applicable setting is: A health provider exports Strata logs to a regulatory SIEM across a shared transit network. It would not directly establish the result required by: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The specific acceptance check here is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

Question 194

A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. Which tempting shortcut would most directly undermine the required architecture control?

  1. Send sensitive event streams over unauthenticated plaintext links because the receiving SIEM is on a corporate subnet
  2. Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event
  3. Send full sensitive payloads to personal email aliases without classification or delivery monitoring
  4. Assume every firewall user mapping grants the same person access to manage the platform

Answer & Explanations

Correct answer: B

A.

This shortcut would undermine Forward cloud security logs reliably using secured syslog for: A health provider exports Strata logs to a regulatory SIEM across a shared transit network. The present situation is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. Here the unsafe move is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. That could cause: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Use: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

B.

The unsafe shortcut is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. It conflicts with the necessary control for: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The plausible consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Instead: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. Confirm with: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

C.

This shortcut would undermine Route security event notifications for distinct responders for: A payment company sends critical event summaries to incident response but full logs remain in its SIEM. The present situation is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. Here the unsafe move is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. That could cause: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Use: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

D.

This shortcut would undermine Design User-ID versus federated administrator authentication for: A bank needs cloud-console SSO for security engineers but workload policies use employee directory groups. The present situation is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. Here the unsafe move is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. That could cause: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Use: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

Question 195

A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. Suppose the team implements this unsafe shortcut: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. Which concrete security or availability failure is most likely?

  1. A legitimate application user may inherit administration rights without any approved identity privilege
  2. Hybrid workers receive inconsistent least-privilege controls across office and remote connections
  3. A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds
  4. Compromised or unapproved branch users can obtain access intended for privileged staff

Answer & Explanations

Correct answer: C

A.

That outcome arises from a different failure: A legitimate application user may inherit administration rights without any approved identity privilege. The related situation is: A bank needs cloud-console SSO for security engineers but workload policies use employee directory groups. In the present case: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The more pertinent consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Prevent it by: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

B.

That outcome arises from a different failure: Hybrid workers receive inconsistent least-privilege controls across office and remote connections. The related situation is: A national retailer wants office and mobile employees to follow role-aligned policies while connecting from different sites. In the present case: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The more pertinent consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Prevent it by: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

C.

A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. This follows when the team chooses the shortcut: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. The situation is: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The correction is: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. The observable test is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

D.

That outcome arises from a different failure: Compromised or unapproved branch users can obtain access intended for privileged staff. The related situation is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. In the present case: A global manufacturer sends east-coast firewall logs to regional collectors with a backup ingestion path. The more pertinent consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Prevent it by: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

Question 196

A financial services provider adds a new collector and must validate which devices actually send logs there. Which network security architecture decision best satisfies the business and technical requirements?

  1. Configure Cloud Identity Engine integration with supported Entra ID or Okta identity sources and test SAML or cloud-directory group claims
  2. Select authenticated encrypted syslog over TLS or supported log export for a central SIEM with explicit retry and monitoring design
  3. Design controlled Strata Logging Service export and alert routing using supported HTTP, email or syslog integrations suited to severity
  4. Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls

Answer & Explanations

Correct answer: D

A.

The alternative action addresses a different condition: A SaaS-heavy enterprise uses Entra ID and wants role-based NGFW and Prisma Access policy. Its reasoning is: Federated identity exchanges authenticated assertions and group information without exposing a static corporate LDAP server to arbitrary internet clients. Here the case is: A financial services provider adds a new collector and must validate which devices actually send logs there. The more direct response is: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

B.

That choice fits Forward cloud security logs reliably using secured syslog, illustrated by: A health provider exports Strata logs to a regulatory SIEM across a shared transit network. Here the material condition is: A financial services provider adds a new collector and must validate which devices actually send logs there. The controlling reason is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration. Apply: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

C.

This action would be appropriate when: A payment company sends critical event summaries to incident response but full logs remain in its SIEM. It follows from: Event notification transports vary in payload, delivery guarantees and privacy, so each destination needs defined alert meaning and failure handling. The current case instead states: A financial services provider adds a new collector and must validate which devices actually send logs there. The response it requires is: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

D.

Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. The case describes: A financial services provider adds a new collector and must validate which devices actually send logs there. The reason this response fits is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration. Confirm it with: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

Question 197

A financial services provider adds a new collector and must validate which devices actually send logs there. An architect proposes: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. Which technical explanation most directly supports that architecture?

  1. The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration
  2. Event notification transports vary in payload, delivery guarantees and privacy, so each destination needs defined alert meaning and failure handling
  3. Policy identity mapping and administrator sign-on solve different trust problems and must each have source, lifecycle and assurance controls
  4. Shared directory records do not guarantee identical policies, so each enforcement plane must receive mapped groups with verified refresh and availability

Answer & Explanations

Correct answer: A

A.

The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration. This causal relationship matters in: A financial services provider adds a new collector and must validate which devices actually send logs there. It supports the action: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. Test the result by: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

B.

This offered mechanism is relevant to Route security event notifications for distinct responders: Event notification transports vary in payload, delivery guarantees and privacy, so each destination needs defined alert meaning and failure handling. It explains the different task: Design controlled Strata Logging Service export and alert routing using supported HTTP, email or syslog integrations suited to severity. The current condition is: A financial services provider adds a new collector and must validate which devices actually send logs there. For that condition the operative principle is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

C.

This offered mechanism is relevant to Design User-ID versus federated administrator authentication: Policy identity mapping and administrator sign-on solve different trust problems and must each have source, lifecycle and assurance controls. It explains the different task: Use User-ID for policy attribution and controlled SAML-based administrator authentication for human console access. The current condition is: A financial services provider adds a new collector and must validate which devices actually send logs there. For that condition the operative principle is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

D.

This offered mechanism is relevant to Apply Cloud Identity Engine consistently to NGFW and Prisma Access: Shared directory records do not guarantee identical policies, so each enforcement plane must receive mapped groups with verified refresh and availability. It explains the different task: Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping. The current condition is: A financial services provider adds a new collector and must validate which devices actually send logs there. For that condition the operative principle is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

Question 198

A financial services provider adds a new collector and must validate which devices actually send logs there. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Use one authorized identity group in both enforcement environments and compare effective allow/deny outcomes
  2. Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability
  3. Trace an enrolled user session through branch identity mapping and check correct policy match at the intended enforcement point
  4. Fail over the Panorama management peer in a lab and confirm managed firewalls retain configuration and can reconnect to the active peer

Answer & Explanations

Correct answer: B

A.

That test checks a different intervention: Plan a common supported identity source for on-prem NGFW and Prisma Access with explicit policy group mapping. Its applicable setting is: A national retailer wants office and mobile employees to follow role-aligned policies while connecting from different sites. It would not directly establish the result required by: A financial services provider adds a new collector and must validate which devices actually send logs there. The specific acceptance check here is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

B.

Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability. This evidence tests whether the response, Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls, addresses the specific condition: A financial services provider adds a new collector and must validate which devices actually send logs there. The mechanism being tested is: The preferred forwarding path determines collector ingress and redistribution, distinct from which Panorama peer currently manages configuration.

C.

That test checks a different intervention: Design supported Cloud Identity Engine identity-to-branch policy integration for security-aware SD-WAN use cases where licensed. Its applicable setting is: A corporate branch hosts shared kiosks and employees needing different access to an internal HR service. It would not directly establish the result required by: A financial services provider adds a new collector and must validate which devices actually send logs there. The specific acceptance check here is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

D.

That test checks a different intervention: Design a synchronized Panorama HA pair at separated failure domains with planned management failover validation. Its applicable setting is: A national retailer centralizes policy for hundreds of NGFWs and cannot tolerate one management VM failure. It would not directly establish the result required by: A financial services provider adds a new collector and must validate which devices actually send logs there. The specific acceptance check here is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

Question 199

A financial services provider adds a new collector and must validate which devices actually send logs there. Which tempting shortcut would most directly undermine the required architecture control?

  1. Use a single Panorama virtual appliance and declare that all data-plane firewalls are resilient because management is centralized
  2. Enable redundant logging on a single unpaired collector and claim all audit evidence survives its disk failure
  3. Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event
  4. Edit the global default snippet to satisfy a single tenant without validating inherited effects

Answer & Explanations

Correct answer: C

A.

This shortcut would undermine Architect Panorama management HA without confusing it with data-plane HA for: A national retailer centralizes policy for hundreds of NGFWs and cannot tolerate one management VM failure. The present situation is: A financial services provider adds a new collector and must validate which devices actually send logs there. Here the unsafe move is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. That could cause: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Use: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

B.

This shortcut would undermine Design resilient distributed log collector groups for: A bank needs redundant firewall logs across two data centers without loss during a collector maintenance. The present situation is: A financial services provider adds a new collector and must validate which devices actually send logs there. Here the unsafe move is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. That could cause: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Use: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

C.

The unsafe shortcut is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. It conflicts with the necessary control for: A financial services provider adds a new collector and must validate which devices actually send logs there. The plausible consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Instead: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. Confirm with: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

D.

This shortcut would undermine Separate Strata Cloud Manager administration scopes for subsidiaries for: A holding company manages cloud NGFW policies for three subsidiaries sharing global protection templates. The present situation is: A financial services provider adds a new collector and must validate which devices actually send logs there. Here the unsafe move is: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. That could cause: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Use: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

Question 200

A financial services provider adds a new collector and must validate which devices actually send logs there. Suppose the team implements this unsafe shortcut: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. Which concrete security or availability failure is most likely?

  1. A local exception can unintentionally alter security policy across unrelated subsidiaries
  2. Compliance investigations fail because the chosen log path or retention does not meet agreed controls
  3. Directory exposure and identity drift create avoidable access-control risks
  4. A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds

Answer & Explanations

Correct answer: D

A.

That outcome arises from a different failure: A local exception can unintentionally alter security policy across unrelated subsidiaries. The related situation is: A holding company manages cloud NGFW policies for three subsidiaries sharing global protection templates. In the present case: A financial services provider adds a new collector and must validate which devices actually send logs there. The more pertinent consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Prevent it by: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

B.

That outcome arises from a different failure: Compliance investigations fail because the chosen log path or retention does not meet agreed controls. The related situation is: An investment firm wants standardized cloud policy administration but regulated logs must reach its SIEM. In the present case: A financial services provider adds a new collector and must validate which devices actually send logs there. The more pertinent consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Prevent it by: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

C.

That outcome arises from a different failure: Directory exposure and identity drift create avoidable access-control risks. The related situation is: A hospital maintains Active Directory in a private data center and needs group updates in cloud-managed NGFW policies. In the present case: A financial services provider adds a new collector and must validate which devices actually send logs there. The more pertinent consequence is: A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. Prevent it by: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls.

D.

A collector outage silently leaves investigation dashboards incomplete while the management GUI still responds. This follows when the team chooses the shortcut: Assume the HA management peer's active state automatically proves a particular Log Collector is receiving every event. The situation is: A financial services provider adds a new collector and must validate which devices actually send logs there. The correction is: Configure collector group log forwarding preference and supported failover before onboarding geographically distributed firewalls. The observable test is: Disable the preferred log path in a test and verify buffered sessions and eventual centralized log availability.

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