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 68

Question 670

A bank needs to classify smart-building devices behind a separately managed virtual switching layer. Suppose the team implements this unsafe shortcut: Assume one data-center NGFW log stream includes application traffic that never crosses that firewall. Which concrete security or availability failure is most likely?

  1. Unagentable IoT assets remain invisible and continue receiving broad default network trust
  2. Virtualized east-west assets remain unknown to risk and policy engines
  3. Compromised devices can move laterally into sensitive patient records services
  4. Long-lived uncontrolled devices become attack pivots despite known exposure

Answer & Explanations

Correct answer: B

A.

That outcome arises from a different failure: Unagentable IoT assets remain invisible and continue receiving broad default network trust. The related situation is: A hospital inventory needs to identify unagentable infusion pumps across many clinical VLANs. In the present case: A bank needs to classify smart-building devices behind a separately managed virtual switching layer. The more pertinent consequence is: Virtualized east-west assets remain unknown to risk and policy engines. Prevent it by: Deploy supported virtual metadata collection where an appliance cannot directly observe relevant virtual-network traffic.

B.

Virtualized east-west assets remain unknown to risk and policy engines. This follows when the team chooses the shortcut: Assume one data-center NGFW log stream includes application traffic that never crosses that firewall. The situation is: A bank needs to classify smart-building devices behind a separately managed virtual switching layer. The correction is: Deploy supported virtual metadata collection where an appliance cannot directly observe relevant virtual-network traffic. The observable test is: Compare authorized sample device observations before and after collector onboarding into the device inventory.

C.

That outcome arises from a different failure: Compromised devices can move laterally into sensitive patient records services. The related situation is: An intensive-care ward requires smart monitors to reach telemetry servers but not finance databases. In the present case: A bank needs to classify smart-building devices behind a separately managed virtual switching layer. The more pertinent consequence is: Virtualized east-west assets remain unknown to risk and policy engines. Prevent it by: Deploy supported virtual metadata collection where an appliance cannot directly observe relevant virtual-network traffic.

D.

That outcome arises from a different failure: Long-lived uncontrolled devices become attack pivots despite known exposure. The related situation is: A hospital cannot immediately update a critical operating-room device and must restrict its network. In the present case: A bank needs to classify smart-building devices behind a separately managed virtual switching layer. The more pertinent consequence is: Virtualized east-west assets remain unknown to risk and policy engines. Prevent it by: Deploy supported virtual metadata collection where an appliance cannot directly observe relevant virtual-network traffic.

Question 671

A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. Which network security architecture decision best satisfies the business and technical requirements?

  1. Architect a Device Security governance loop linking discovery, risk prioritization, policy enforcement and asset-owner remediation evidence
  2. Deploy supported virtual metadata collection where an appliance cannot directly observe relevant virtual-network traffic
  3. Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility
  4. Place supported Device Security visibility feeds at representative network inspection points before enabling risk-based enforcement

Answer & Explanations

Correct answer: C

A.

The alternative action addresses a different condition: A healthcare network needs documented remediation of high-risk clinical IoT findings. Its reasoning is: A list of discovered devices alone does not reduce risk; policy outcomes and remediation records demonstrate continuous control effectiveness. Here the case is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The more direct response is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

B.

The alternative action addresses a different condition: A SaaS operator hosts IoT gateways in a virtual cluster without a direct hardware firewall choke point. Its reasoning is: Metadata collectors extend behavioral visibility to remote or virtualized segments while still requiring a defensible source of flow information. Here the case is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The more direct response is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

C.

Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. The case describes: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The reason this response fits is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context. Confirm it with: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

D.

This action would be appropriate when: A hospital inventory needs to identify unagentable infusion pumps across many clinical VLANs. It follows from: Discovery correlates network behavior and device attributes without requiring endpoint agents on embedded equipment, enabling classification before access policy. The current case instead states: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The response it requires is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

Question 672

A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. An architect proposes: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. Which technical explanation most directly supports that architecture?

  1. Discovery correlates network behavior and device attributes without requiring endpoint agents on embedded equipment, enabling classification before access policy
  2. Device Security classification links IoT type and risk context to NGFW access controls while preserving equipment-specific service dependencies
  3. Legacy device risk may be reduced by segmentation and monitored allowlists when endpoint patching or authentication is infeasible
  4. Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context

Answer & Explanations

Correct answer: D

A.

This offered mechanism is relevant to Architect passive discovery of unmanaged IoT devices: Discovery correlates network behavior and device attributes without requiring endpoint agents on embedded equipment, enabling classification before access policy. It explains the different task: Place supported Device Security visibility feeds at representative network inspection points before enabling risk-based enforcement. The current condition is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. For that condition the operative principle is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

B.

This offered mechanism is relevant to Enforce segment-specific policies for classified medical IoT: Device Security classification links IoT type and risk context to NGFW access controls while preserving equipment-specific service dependencies. It explains the different task: Assign risk-aware Device-ID policies to discovered medical or industrial equipment with explicit allowed communication paths. The current condition is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. For that condition the operative principle is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

C.

This offered mechanism is relevant to Govern IoT risk exceptions with compensating controls: Legacy device risk may be reduced by segmentation and monitored allowlists when endpoint patching or authentication is infeasible. It explains the different task: Use scoped monitored policy exceptions for high-risk equipment that cannot be patched immediately. The current condition is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. For that condition the operative principle is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

D.

Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context. This causal relationship matters in: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. It supports the action: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. Test the result by: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

Question 673

A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Verify that a remote scanner's device identity, site and session reach central inventory and security policy
  2. Record a documented risk exception and confirm only required application flows remain permitted
  3. Generate benign device traffic across two zones and confirm asset classification appears from both intended paths
  4. Trace a test device in an unmonitored segment and confirm the revised design produces a single explainable asset identity

Answer & Explanations

Correct answer: A

A.

Verify that a remote scanner's device identity, site and session reach central inventory and security policy. This evidence tests whether the response, Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility, addresses the specific condition: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The mechanism being tested is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

B.

That test checks a different intervention: Use scoped monitored policy exceptions for high-risk equipment that cannot be patched immediately. Its applicable setting is: A hospital cannot immediately update a critical operating-room device and must restrict its network. It would not directly establish the result required by: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The specific acceptance check here is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

C.

That test checks a different intervention: Install authorized passive sensor or mirrored feed where target IoT traffic is actually observable without breaking production paths. Its applicable setting is: A manufacturing campus needs discovery of machine-to-machine traffic never routed to the internet. It would not directly establish the result required by: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The specific acceptance check here is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

D.

That test checks a different intervention: Compare supported sensor sources from NGFW, Prisma SD-WAN and virtual collectors to eliminate blind spots and redundant ingest. Its applicable setting is: A retailer has NGFW logs in headquarters but needs inventory coverage for warehouse branch IoT. It would not directly establish the result required by: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The specific acceptance check here is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

Question 674

A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. Which tempting shortcut would most directly undermine the required architecture control?

  1. Add multiple mirrored feeds from one VLAN and claim enterprise-wide device inventory completeness
  2. Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried
  3. Whitelist one transient IP as if it permanently identifies a medical pump
  4. Continue applying privileged device-category policy indefinitely after the identity source stops updating

Answer & Explanations

Correct answer: B

A.

This shortcut would undermine Avoid duplicate or blind IoT telemetry placement for: A retailer has NGFW logs in headquarters but needs inventory coverage for warehouse branch IoT. The present situation is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. Here the unsafe move is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. That could cause: Unseen branch endpoints may access critical services without risk classification. Use: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

B.

The unsafe shortcut is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. It conflicts with the necessary control for: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The plausible consequence is: Unseen branch endpoints may access critical services without risk classification. Instead: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. Confirm with: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

C.

This shortcut would undermine Use Device-ID for stable class-aware enforcement when IPs change for: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The present situation is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. Here the unsafe move is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. That could cause: Unseen branch endpoints may access critical services without risk classification. Use: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

D.

This shortcut would undermine Design graceful behavior when Device-ID confidence is stale for: A hospital loses a sensor feed and must keep critical monitors running without trusting all new endpoints. The present situation is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. Here the unsafe move is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. That could cause: Unseen branch endpoints may access critical services without risk classification. Use: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

Question 675

A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. Suppose the team implements this unsafe shortcut: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. Which concrete security or availability failure is most likely?

  1. A spoofed or replaced device retains risky network access due to stale classification
  2. Known high-risk assets remain reachable through unsafe paths despite complete discovery
  3. Unseen branch endpoints may access critical services without risk classification
  4. Virtualized east-west assets remain unknown to risk and policy engines

Answer & Explanations

Correct answer: C

A.

That outcome arises from a different failure: A spoofed or replaced device retains risky network access due to stale classification. The related situation is: A hospital loses a sensor feed and must keep critical monitors running without trusting all new endpoints. In the present case: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The more pertinent consequence is: Unseen branch endpoints may access critical services without risk classification. Prevent it by: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

B.

That outcome arises from a different failure: Known high-risk assets remain reachable through unsafe paths despite complete discovery. The related situation is: A healthcare network needs documented remediation of high-risk clinical IoT findings. In the present case: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The more pertinent consequence is: Unseen branch endpoints may access critical services without risk classification. Prevent it by: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

C.

Unseen branch endpoints may access critical services without risk classification. This follows when the team chooses the shortcut: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. The situation is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The correction is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. The observable test is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

D.

That outcome arises from a different failure: Virtualized east-west assets remain unknown to risk and policy engines. The related situation is: A SaaS operator hosts IoT gateways in a virtual cluster without a direct hardware firewall choke point. In the present case: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The more pertinent consequence is: Unseen branch endpoints may access critical services without risk classification. Prevent it by: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

Question 676

A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Which network security architecture decision best satisfies the business and technical requirements?

  1. Install authorized passive sensor or mirrored feed where target IoT traffic is actually observable without breaking production paths
  2. Compare supported sensor sources from NGFW, Prisma SD-WAN and virtual collectors to eliminate blind spots and redundant ingest
  3. Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time
  4. Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility

Answer & Explanations

Correct answer: D

A.

That choice fits Choose NGFW tap or mirrored IoT sensor placement for east-west visibility, illustrated by: A manufacturing campus needs discovery of machine-to-machine traffic never routed to the internet. Here the material condition is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The controlling reason is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context. Apply: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

B.

This action would be appropriate when: A retailer has NGFW logs in headquarters but needs inventory coverage for warehouse branch IoT. It follows from: Different observation points expose different packet metadata, so feeding one repeated segment cannot substitute for absent site or cloud coverage. The current case instead states: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The response it requires is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

C.

The alternative action addresses a different condition: A hospital relocates smart infusion pumps between networks and needs consistent application controls. Its reasoning is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows. Here the case is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The more direct response is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

D.

The best-matched action is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. The actual need is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Here Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context. Check the result by: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

Question 677

A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. An architect proposes: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. Which technical explanation most directly supports that architecture?

  1. Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context
  2. Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows
  3. Device-ID cannot be treated as permanently trustworthy when passive evidence or asset attributes become stale; restricted fallback reduces false privilege
  4. A list of discovered devices alone does not reduce risk; policy outcomes and remediation records demonstrate continuous control effectiveness

Answer & Explanations

Correct answer: A

A.

Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context. This causal relationship matters in: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. It supports the action: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. Test the result by: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

B.

This offered mechanism is relevant to Use Device-ID for stable class-aware enforcement when IPs change: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows. It explains the different task: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. The current condition is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. For that condition the operative principle is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

C.

This offered mechanism is relevant to Design graceful behavior when Device-ID confidence is stale: Device-ID cannot be treated as permanently trustworthy when passive evidence or asset attributes become stale; restricted fallback reduces false privilege. It explains the different task: Require conservative fallback policy and manual validation when an IoT device's identity data ages or classification changes. The current condition is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. For that condition the operative principle is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

D.

This offered mechanism is relevant to Validate Device Security risk controls and reporting coverage: A list of discovered devices alone does not reduce risk; policy outcomes and remediation records demonstrate continuous control effectiveness. It explains the different task: Architect a Device Security governance loop linking discovery, risk prioritization, policy enforcement and asset-owner remediation evidence. The current condition is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. For that condition the operative principle is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

Question 678

A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Track one synthetic high-risk device finding through owner review, rule change and successful verification
  2. Verify that a remote scanner's device identity, site and session reach central inventory and security policy
  3. Compare authorized sample device observations before and after collector onboarding into the device inventory
  4. Connect a permitted test device and verify discovery, device type confidence and traffic observation from the intended source

Answer & Explanations

Correct answer: B

A.

That test checks a different intervention: Architect a Device Security governance loop linking discovery, risk prioritization, policy enforcement and asset-owner remediation evidence. Its applicable setting is: A healthcare network needs documented remediation of high-risk clinical IoT findings. It would not directly establish the result required by: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The specific acceptance check here is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

B.

Verify that a remote scanner's device identity, site and session reach central inventory and security policy. This evidence tests whether the response, Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility, addresses the specific condition: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The mechanism being tested is: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context.

C.

That test checks a different intervention: Deploy supported virtual metadata collection where an appliance cannot directly observe relevant virtual-network traffic. Its applicable setting is: A SaaS operator hosts IoT gateways in a virtual cluster without a direct hardware firewall choke point. It would not directly establish the result required by: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The specific acceptance check here is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

D.

That test checks a different intervention: Place supported Device Security visibility feeds at representative network inspection points before enabling risk-based enforcement. Its applicable setting is: A hospital inventory needs to identify unagentable infusion pumps across many clinical VLANs. It would not directly establish the result required by: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The specific acceptance check here is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

Question 679

A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Which tempting shortcut would most directly undermine the required architecture control?

  1. Require every industrial sensor to install an unsupported endpoint agent before documenting it in the asset inventory
  2. Allow every medical device to communicate with all patient database systems because it uses the hospital network
  3. Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried
  4. Mark every unpatchable device trusted permanently because the vendor does not support updates

Answer & Explanations

Correct answer: C

A.

This shortcut would undermine Architect passive discovery of unmanaged IoT devices for: A hospital inventory needs to identify unagentable infusion pumps across many clinical VLANs. The present situation is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Here the unsafe move is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. That could cause: Unseen branch endpoints may access critical services without risk classification. Use: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

B.

This shortcut would undermine Enforce segment-specific policies for classified medical IoT for: An intensive-care ward requires smart monitors to reach telemetry servers but not finance databases. The present situation is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Here the unsafe move is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. That could cause: Unseen branch endpoints may access critical services without risk classification. Use: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

C.

The unsafe shortcut is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. It conflicts with the necessary control for: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The plausible consequence is: Unseen branch endpoints may access critical services without risk classification. Instead: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. Confirm with: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

D.

This shortcut would undermine Govern IoT risk exceptions with compensating controls for: A hospital cannot immediately update a critical operating-room device and must restrict its network. The present situation is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Here the unsafe move is: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. That could cause: Unseen branch endpoints may access critical services without risk classification. Use: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

Question 680

A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. Suppose the team implements this unsafe shortcut: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. Which concrete security or availability failure is most likely?

  1. Long-lived uncontrolled devices become attack pivots despite known exposure
  2. Internal device traffic remains unclassified and risk assessment is incomplete
  3. Undiscovered branch sensors retain default access while licensing and ingest costs rise
  4. Unseen branch endpoints may access critical services without risk classification

Answer & Explanations

Correct answer: D

A.

That outcome arises from a different failure: Long-lived uncontrolled devices become attack pivots despite known exposure. The related situation is: A hospital cannot immediately update a critical operating-room device and must restrict its network. In the present case: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The more pertinent consequence is: Unseen branch endpoints may access critical services without risk classification. Prevent it by: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

B.

That outcome arises from a different failure: Internal device traffic remains unclassified and risk assessment is incomplete. The related situation is: A manufacturing campus needs discovery of machine-to-machine traffic never routed to the internet. In the present case: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The more pertinent consequence is: Unseen branch endpoints may access critical services without risk classification. Prevent it by: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

C.

That outcome arises from a different failure: Undiscovered branch sensors retain default access while licensing and ingest costs rise. The related situation is: A retailer has NGFW logs in headquarters but needs inventory coverage for warehouse branch IoT. In the present case: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The more pertinent consequence is: Unseen branch endpoints may access critical services without risk classification. Prevent it by: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility.

D.

Unseen branch endpoints may access critical services without risk classification. This follows when the team chooses the shortcut: Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried. The situation is: A retailer consolidates IoT risk view from Prisma SD-WAN and PAN-OS SD-WAN sites. The correction is: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. The observable test is: Verify that a remote scanner's device identity, site and session reach central inventory and security policy.

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