Palo Alto Networks NetSec-Architect Practice Test 35
Question 340
For an original educational Network Security Architect scenario, consider: A merger changes group distinguished names and periodic synchronization succeeds technically but omits the newly approved security groups. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Design a supported encrypted log-forwarding path such as syslog over TLS with certificate trust and appropriate routing and buffering considerations.
- Check: Review current hierarchy, template values, rule order, committed configuration differences and representative child devices before deployment.
- Check: Test connector failure, group rename, account disablement, sync timestamps and downstream policy decisions against a known-good directory snapshot.
- Change: Design operational health checks, sync-drift alerting and safe policy handling for stale or missing identity data in the Cloud Identity Engine path.
- Ignore synchronization errors because the directory was correct during the original deployment.
Explanation
Correct Answer
C:A successful network connection to an identity provider is not evidence that authoritative users and groups were synchronized accurately or on time. Required intervention: Design operational health checks, sync-drift alerting and safe policy handling for stale or missing identity data in the Cloud Identity Engine path.
D:A successful network connection to an identity provider is not evidence that authoritative users and groups were synchronized accurately or on time. Acceptance: Identity changes become visible within approved latency and stale state triggers investigation and appropriate fail-safe controls.
Incorrect Answers
A:Change: Design a supported encrypted log-forwarding path such as syslog over TLS with certificate trust and appropriate routing and buffering considerations. A successful network connection to an identity provider is not evidence that authoritative users and groups were synchronized accurately or on time.
B:Check: Review current hierarchy, template values, rule order, committed configuration differences and representative child devices before deployment. A successful network connection to an identity provider is not evidence that authoritative users and groups were synchronized accurately or on time.
E:A successful network connection to an identity provider is not evidence that authoritative users and groups were synchronized accurately or on time.
Question 341
A network security architect is reviewing this environment: A large enterprise adds decryption and threat logging, doubling event volume while existing collectors retain only a fraction of the required investigation window. A proposed shortcut is: Size log collectors solely from the number of firewalls and disable alerts when ingestion lag increases. What should the security architect recommend as the narrowly scoped correction? Select ONE best answer.
- Design standards-based SAML authentication or supported cloud-directory integration with explicit IdP trust, group claims, RBAC and conditional access policy.
- Size log collectors solely from the number of firewalls and disable alerts when ingestion lag increases.
- Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring.
- Architect appropriately sized distributed log collectors or collector groups with redundancy, retention planning, forwarding and health visibility.
Explanation
Correct Answer
C:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Incorrect Answers
A:Design standards-based SAML authentication or supported cloud-directory integration with explicit IdP trust, group claims, RBAC and conditional access policy. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
B:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
D:Architect appropriately sized distributed log collectors or collector groups with redundancy, retention planning, forwarding and health visibility. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Question 342
A Palo Alto Networks architecture review finds: A large enterprise adds decryption and threat logging, doubling event volume while existing collectors retain only a fraction of the required investigation window. A design team proposes: Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring. Which architecture principle most strongly supports the recommended response? Select ONE best answer.
- Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
- Transport protection and endpoint verification matter for log integrity and confidentiality; choosing a syslog port alone does not authenticate a receiver.
- Email notification, HTTP/API-style delivery and syslog are different integration patterns with distinct reliability, structure, authentication and scale properties.
- Federation relies on signed assertions and well-defined identity-provider trust; it does not automatically synchronize every group or replace authorization design.
Explanation
Correct Answer
A:Demonstrable success requires: Retained evidence meets the agreed search window and peak events remain observable without uncontrolled silent drops.
Incorrect Answers
B:Transport protection and endpoint verification matter for log integrity and confidentiality; choosing a syslog port alone does not authenticate a receiver. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
C:Email notification, HTTP/API-style delivery and syslog are different integration patterns with distinct reliability, structure, authentication and scale properties. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
D:Federation relies on signed assertions and well-defined identity-provider trust; it does not automatically synchronize every group or replace authorization design. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Question 343
The architecture board has not yet authorized configuration changes. Current evidence indicates: A large enterprise adds decryption and threat logging, doubling event volume while existing collectors retain only a fraction of the required investigation window. Which evidence best tests the architecture diagnosis before approving a disruptive change? Select ONE best answer.
- Map source log types, regions, account entitlements, data lifecycle, ingestion monitoring and allowed analyst access.
- Compare required event fields, schema mapping, retries, API credentials, throughput and downstream acknowledgement using representative test events.
- Check managed-device inventory, tenant assignments, administrative privileges, deployment workflow and accepted ownership for each site.
- Measure EPS and bytes per event by log category, compression, retention rules, collector health and SIEM intake performance under realistic peaks.
Explanation
Correct Answer
D:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Incorrect Answers
A:Map source log types, regions, account entitlements, data lifecycle, ingestion monitoring and allowed analyst access. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
B:Compare required event fields, schema mapping, retries, API credentials, throughput and downstream acknowledgement using representative test events. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
C:Check managed-device inventory, tenant assignments, administrative privileges, deployment workflow and accepted ownership for each site. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Question 344
The architecture team has implemented an approved correction and must now perform a production-safe acceptance test. Original problem: A large enterprise adds decryption and threat logging, doubling event volume while existing collectors retain only a fraction of the required investigation window. The operations owner requires positive and negative test evidence and confirmation that legitimate business workflows still function. Which acceptance result demonstrates improved security without breaking authorized workflows? Select ONE best answer.
- Approved telemetry is available for searches during normal operation and satisfies agreed retention, privacy and recovery requirements.
- Legitimate administrators authenticate through their approved IdP and receive only mapped roles, while forged or mismatched assertions are rejected.
- Retained evidence meets the agreed search window and peak events remain observable without uncontrolled silent drops.
- Every device has an accountable management owner and changes are auditable, staged and scoped to the right tenant.
Explanation
Correct Answer
C:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Incorrect Answers
A:Approved telemetry is available for searches during normal operation and satisfies agreed retention, privacy and recovery requirements. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
B:Legitimate administrators authenticate through their approved IdP and receive only mapped roles, while forged or mismatched assertions are rejected. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
D:Every device has an accountable management owner and changes are auditable, staged and scoped to the right tenant. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Question 345
A design sign-off request identifies the following problem: A large enterprise adds decryption and threat logging, doubling event volume while existing collectors retain only a fraction of the required investigation window. Which paired security change and validation should close the design review? Select ONE best answer.
- Change: Architect appropriately sized distributed log collectors or collector groups with redundancy, retention planning, forwarding and health visibility. Verify: Verify collector group membership, log redistribution or buffering behavior, ingestion rate, retention capacity and failover tests.
- Change: Define an explicit cloud-management operating model covering SCM onboarding, tenant scope, RBAC, policy ownership and staged rollout. Verify: Check managed-device inventory, tenant assignments, administrative privileges, deployment workflow and accepted ownership for each site.
- Change: Architect Strata Logging Service placement, regional constraints, supported ingestion sources, retention and recovery paths under the organization's data handling policy. Verify: Map source log types, regions, account entitlements, data lifecycle, ingestion monitoring and allowed analyst access.
- Change: Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring. Verify: Measure EPS and bytes per event by log category, compression, retention rules, collector health and SIEM intake performance under realistic peaks.
Explanation
Correct Answer
D:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced. The change is successful only when: Retained evidence meets the agreed search window and peak events remain observable without uncontrolled silent drops.
Incorrect Answers
A:Change: Architect appropriately sized distributed log collectors or collector groups with redundancy, retention planning, forwarding and health visibility. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
B:Change: Define an explicit cloud-management operating model covering SCM onboarding, tenant scope, RBAC, policy ownership and staged rollout. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
C:Change: Architect Strata Logging Service placement, regional constraints, supported ingestion sources, retention and recovery paths under the organization's data handling policy. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Question 346
A network security architect is reviewing this environment: A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts. A proposed shortcut is: Size log collectors solely from the number of firewalls and disable alerts when ingestion lag increases. What should the security architect recommend as the narrowly scoped correction? Select ONE best answer.
- Select supported SLS integration and forwarding methods based on destination capability, authentication, event schema and delivery objectives rather than one format for all use cases.
- Architect separation of duties with scoped RBAC, change approvals, break-glass accounts and audited privilege elevation across management platforms.
- Size log collectors solely from the number of firewalls and disable alerts when ingestion lag increases.
- Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring.
Explanation
Correct Answer
D:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Incorrect Answers
A:Select supported SLS integration and forwarding methods based on destination capability, authentication, event schema and delivery objectives rather than one format for all use cases. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
B:Architect separation of duties with scoped RBAC, change approvals, break-glass accounts and audited privilege elevation across management platforms. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
C:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced. Use this instead: Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring.
Question 347
A Palo Alto Networks architecture review finds: A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts. A design team proposes: Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring. Which architecture principle most strongly supports the recommended response? Select ONE best answer.
- Email notification, HTTP/API-style delivery and syslog are different integration patterns with distinct reliability, structure, authentication and scale properties.
- Identity synchronization transfers selected directory context into security services; its trust boundary, connector placement and refresh behavior matter to policy correctness.
- Transport protection and endpoint verification matter for log integrity and confidentiality; choosing a syslog port alone does not authenticate a receiver.
- Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Explanation
Correct Answer
D:Demonstrable success requires: Retained evidence meets the agreed search window and peak events remain observable without uncontrolled silent drops. This principle explains the proposed architecture, which is: Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring.
Incorrect Answers
A:Email notification, HTTP/API-style delivery and syslog are different integration patterns with distinct reliability, structure, authentication and scale properties. A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts.
B:This option addresses a different security architecture topic (Cloud Identity Engine directory synchronization) rather than the documented Audit logging capacity and retention decision.
C:Transport protection and endpoint verification matter for log integrity and confidentiality; choosing a syslog port alone does not authenticate a receiver. A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts.
Question 348
The architecture board has not yet authorized configuration changes. Current evidence indicates: A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts. Which evidence best tests the architecture diagnosis before approving a disruptive change? Select ONE best answer.
- Measure EPS and bytes per event by log category, compression, retention rules, collector health and SIEM intake performance under realistic peaks.
- Review role mappings, tenant scope, effective permissions, audit trails and permitted break-glass usage through controlled test accounts.
- Verify SAML issuer, audience, signing keys, clock skew, group claims and role mapping with valid and invalid test identities.
- Inspect Panorama peer status, synchronization, management paths, certificate trust and controlled failover behavior before approving the design.
Explanation
Correct Answer
A:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced. Confirm afterward that: Retained evidence meets the agreed search window and peak events remain observable without uncontrolled silent drops.
Incorrect Answers
B:Review role mappings, tenant scope, effective permissions, audit trails and permitted break-glass usage through controlled test accounts. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
C:Verify SAML issuer, audience, signing keys, clock skew, group claims and role mapping with valid and invalid test identities. Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
D:This option addresses a different security architecture topic (Panorama control-plane high availability) rather than the documented Audit logging capacity and retention decision.
Question 349
The architecture team has implemented an approved correction and must now perform a production-safe acceptance test. Original problem: A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts. The operations owner requires positive and negative test evidence and confirmation that legitimate business workflows still function. Which acceptance result demonstrates improved security without breaking authorized workflows? Select ONE best answer.
- Identity changes become visible within approved latency and stale state triggers investigation and appropriate fail-safe controls.
- Retained evidence meets the agreed search window and peak events remain observable without uncontrolled silent drops.
- Standard controls remain consistent and approved regional overrides apply only to intended firewalls without cross-region network breakage.
- Approved telemetry is available for searches during normal operation and satisfies agreed retention, privacy and recovery requirements.
Explanation
Correct Answer
B:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
Incorrect Answers
A:This option addresses a different security architecture topic (Identity sync incident resilience) rather than the documented Audit logging capacity and retention decision.
C:This option addresses a different security architecture topic (Panorama templates and centralized policy structure) rather than the documented Audit logging capacity and retention decision.
D:Approved telemetry is available for searches during normal operation and satisfies agreed retention, privacy and recovery requirements. A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts.
Question 350
For an original educational Network Security Architect scenario, consider: A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Size log collectors solely from the number of firewalls and disable alerts when ingestion lag increases.
- Check: Measure EPS and bytes per event by log category, compression, retention rules, collector health and SIEM intake performance under realistic peaks.
- Check: Follow a test user's login, group lookup, IP mapping, SAML assertion and firewall policy hit across mobility and logout events.
- Change: Architect appropriately sized distributed log collectors or collector groups with redundancy, retention planning, forwarding and health visibility.
- Change: Estimate log ingestion, indexing, retention and forwarding capacity with growth and peak-rate headroom, plus prioritization and monitoring.
Explanation
Correct Answer
B:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced. Acceptance: Retained evidence meets the agreed search window and peak events remain observable without uncontrolled silent drops.
E:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced. Evidence: Measure EPS and bytes per event by log category, compression, retention rules, collector health and SIEM intake performance under realistic peaks.
Incorrect Answers
A:Log infrastructure must be sized for event rate and storage retention; raw firewall throughput does not describe the volume of security telemetry produced.
C:This option addresses a different security architecture topic (User-ID versus authentication workflows) rather than the documented Audit logging capacity and retention decision.
D:Change: Architect appropriately sized distributed log collectors or collector groups with redundancy, retention planning, forwarding and health visibility. A newly acquired region pushes all device logs to a central SIEM during an incident, saturating the forwarding queue and delaying high-severity alerts.