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 69

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.

Question 681

A hospital relocates smart infusion pumps between networks and needs consistent application controls. Which network security architecture decision best satisfies the business and technical requirements?

  1. Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time
  2. Place supported Device Security visibility feeds at representative network inspection points before enabling risk-based enforcement
  3. Assign risk-aware Device-ID policies to discovered medical or industrial equipment with explicit allowed communication paths
  4. Use scoped monitored policy exceptions for high-risk equipment that cannot be patched immediately

Answer & Explanations

Correct answer: A

A.

Apply: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. For the reported condition: A hospital relocates smart infusion pumps between networks and needs consistent application controls. This is appropriate because Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows. Acceptance evidence: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

B.

The alternative action addresses a different condition: A hospital inventory needs to identify unagentable infusion pumps across many clinical VLANs. Its reasoning is: Discovery correlates network behavior and device attributes without requiring endpoint agents on embedded equipment, enabling classification before access policy. Here the case is: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The more direct response is: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

C.

That choice fits Enforce segment-specific policies for classified medical IoT, illustrated by: An intensive-care ward requires smart monitors to reach telemetry servers but not finance databases. Here the material condition is: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The controlling reason is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows. Apply: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

D.

This action would be appropriate when: A hospital cannot immediately update a critical operating-room device and must restrict its network. It follows from: Legacy device risk may be reduced by segmentation and monitored allowlists when endpoint patching or authentication is infeasible. The current case instead states: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The response it requires is: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

Question 682

A hospital relocates smart infusion pumps between networks and needs consistent application controls. An architect proposes: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. Which technical explanation most directly supports that architecture?

  1. Legacy device risk may be reduced by segmentation and monitored allowlists when endpoint patching or authentication is infeasible
  2. Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows
  3. Sensor coverage depends on topology and mirrored packet completeness, not merely how many physical network switches exist
  4. Different observation points expose different packet metadata, so feeding one repeated segment cannot substitute for absent site or cloud coverage

Answer & Explanations

Correct answer: B

A.

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 hospital relocates smart infusion pumps between networks and needs consistent application controls. For that condition the operative principle is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

B.

Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows. This causal relationship matters in: A hospital relocates smart infusion pumps between networks and needs consistent application controls. It supports the action: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. Test the result by: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

C.

This offered mechanism is relevant to Choose NGFW tap or mirrored IoT sensor placement for east-west visibility: Sensor coverage depends on topology and mirrored packet completeness, not merely how many physical network switches exist. It explains the different task: Install authorized passive sensor or mirrored feed where target IoT traffic is actually observable without breaking production paths. The current condition is: A hospital relocates smart infusion pumps between networks and needs consistent application controls. For that condition the operative principle is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

D.

This offered mechanism is relevant to Avoid duplicate or blind IoT telemetry placement: Different observation points expose different packet metadata, so feeding one repeated segment cannot substitute for absent site or cloud coverage. It explains the different task: Compare supported sensor sources from NGFW, Prisma SD-WAN and virtual collectors to eliminate blind spots and redundant ingest. The current condition is: A hospital relocates smart infusion pumps between networks and needs consistent application controls. For that condition the operative principle is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

Question 683

A hospital relocates smart infusion pumps between networks and needs consistent application controls. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Trace a test device in an unmonitored segment and confirm the revised design produces a single explainable asset identity
  2. Compare authorized sample device observations before and after collector onboarding into the device inventory
  3. Change a pilot device's DHCP lease and verify it still matches the intended restricted policy
  4. Verify that a remote scanner's device identity, site and session reach central inventory and security policy

Answer & Explanations

Correct answer: C

A.

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 hospital relocates smart infusion pumps between networks and needs consistent application controls. The specific acceptance check here is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

B.

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 hospital relocates smart infusion pumps between networks and needs consistent application controls. The specific acceptance check here is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

C.

Change a pilot device's DHCP lease and verify it still matches the intended restricted policy. This evidence tests whether the response, Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time, addresses the specific condition: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The mechanism being tested is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

D.

That test checks a different intervention: Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility. Its applicable setting is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. It would not directly establish the result required by: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The specific acceptance check here is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

Question 684

A hospital relocates smart infusion pumps between networks and needs consistent application controls. Which tempting shortcut would most directly undermine the required architecture control?

  1. Conclude a healthy WAN SLA metric proves that every device behind the edge is inventoried
  2. Declare IoT security complete as soon as a dashboard displays device counts
  3. Continue applying privileged device-category policy indefinitely after the identity source stops updating
  4. Whitelist one transient IP as if it permanently identifies a medical pump

Answer & Explanations

Correct answer: D

A.

This shortcut would undermine Correlate IoT visibility from Prisma and PAN-OS SD-WAN branches for: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. The present situation is: A hospital relocates smart infusion pumps between networks and needs consistent application controls. Here the unsafe move is: Whitelist one transient IP as if it permanently identifies a medical pump. That could cause: A reused address grants inappropriate access to an unrelated endpoint. Use: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

B.

This shortcut would undermine Validate Device Security risk controls and reporting coverage for: A healthcare network needs documented remediation of high-risk clinical IoT findings. The present situation is: A hospital relocates smart infusion pumps between networks and needs consistent application controls. Here the unsafe move is: Whitelist one transient IP as if it permanently identifies a medical pump. That could cause: A reused address grants inappropriate access to an unrelated endpoint. Use: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

C.

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 hospital relocates smart infusion pumps between networks and needs consistent application controls. Here the unsafe move is: Whitelist one transient IP as if it permanently identifies a medical pump. That could cause: A reused address grants inappropriate access to an unrelated endpoint. Use: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

D.

The unsafe shortcut is: Whitelist one transient IP as if it permanently identifies a medical pump. It conflicts with the necessary control for: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The plausible consequence is: A reused address grants inappropriate access to an unrelated endpoint. Instead: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. Confirm with: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

Question 685

A hospital relocates smart infusion pumps between networks and needs consistent application controls. Suppose the team implements this unsafe shortcut: Whitelist one transient IP as if it permanently identifies a medical pump. Which concrete security or availability failure is most likely?

  1. A reused address grants inappropriate access to an unrelated endpoint
  2. A spoofed or replaced device retains risky network access due to stale classification
  3. Unagentable IoT assets remain invisible and continue receiving broad default network trust
  4. Compromised devices can move laterally into sensitive patient records services

Answer & Explanations

Correct answer: A

A.

A reused address grants inappropriate access to an unrelated endpoint. This follows when the team chooses the shortcut: Whitelist one transient IP as if it permanently identifies a medical pump. The situation is: A hospital relocates smart infusion pumps between networks and needs consistent application controls. The correction is: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. The observable test is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

B.

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 hospital relocates smart infusion pumps between networks and needs consistent application controls. The more pertinent consequence is: A reused address grants inappropriate access to an unrelated endpoint. Prevent it by: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

C.

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 hospital relocates smart infusion pumps between networks and needs consistent application controls. The more pertinent consequence is: A reused address grants inappropriate access to an unrelated endpoint. Prevent it by: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

D.

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 hospital relocates smart infusion pumps between networks and needs consistent application controls. The more pertinent consequence is: A reused address grants inappropriate access to an unrelated endpoint. Prevent it by: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

Question 686

A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. Which network security architecture decision best satisfies the business and technical requirements?

  1. Deploy supported virtual metadata collection where an appliance cannot directly observe relevant virtual-network traffic
  2. Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time
  3. Integrate supported branch edge telemetry with Device Security classification for remote-site risk visibility
  4. Architect a Device Security governance loop linking discovery, risk prioritization, policy enforcement and asset-owner remediation evidence

Answer & Explanations

Correct answer: B

A.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The more direct response is: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

B.

Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. The case describes: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The reason this response fits is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows. Confirm it with: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

C.

This action would be appropriate when: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. It follows from: Branch SD-WAN monitoring can expose asset traffic not observed at the data-center edge, supporting more complete security context. The current case instead states: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The response it requires is: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

D.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The more direct response is: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

Question 687

A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. An architect proposes: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. Which technical explanation most directly supports that architecture?

  1. A list of discovered devices alone does not reduce risk; policy outcomes and remediation records demonstrate continuous control effectiveness
  2. Device-ID cannot be treated as permanently trustworthy when passive evidence or asset attributes become stale; restricted fallback reduces false privilege
  3. Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows
  4. Discovery correlates network behavior and device attributes without requiring endpoint agents on embedded equipment, enabling classification before access policy

Answer & Explanations

Correct answer: C

A.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. For that condition the operative principle is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

B.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. For that condition the operative principle is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

C.

Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows. This causal relationship matters in: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. It supports the action: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. Test the result by: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

D.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. For that condition the operative principle is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

Question 688

A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. Which observable test most directly confirms the proposed architecture meets its intended security and availability outcomes?

  1. Connect a permitted test device and verify discovery, device type confidence and traffic observation from the intended source
  2. Test a known device's required management flow and a denied lateral workstation connection in policy logs
  3. Record a documented risk exception and confirm only required application flows remain permitted
  4. Change a pilot device's DHCP lease and verify it still matches the intended restricted policy

Answer & Explanations

Correct answer: D

A.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The specific acceptance check here is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

B.

That test checks a different intervention: Assign risk-aware Device-ID policies to discovered medical or industrial equipment with explicit allowed communication paths. Its applicable setting is: An intensive-care ward requires smart monitors to reach telemetry servers but not finance databases. It would not directly establish the result required by: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The specific acceptance check here is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

C.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The specific acceptance check here is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

D.

Change a pilot device's DHCP lease and verify it still matches the intended restricted policy. This evidence tests whether the response, Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time, addresses the specific condition: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The mechanism being tested is: Device identity and category persist conceptually across address assignment changes when supported discovery is reliable, avoiding brittle network-based allows.

Question 689

A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. Which tempting shortcut would most directly undermine the required architecture control?

  1. Whitelist one transient IP as if it permanently identifies a medical pump
  2. Mark every unpatchable device trusted permanently because the vendor does not support updates
  3. Place one sensor at internet egress and assume it sees isolated east-west plant-controller communication
  4. Add multiple mirrored feeds from one VLAN and claim enterprise-wide device inventory completeness

Answer & Explanations

Correct answer: A

A.

The unsafe shortcut is: Whitelist one transient IP as if it permanently identifies a medical pump. It conflicts with the necessary control for: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The plausible consequence is: A reused address grants inappropriate access to an unrelated endpoint. Instead: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. Confirm with: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

B.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. Here the unsafe move is: Whitelist one transient IP as if it permanently identifies a medical pump. That could cause: A reused address grants inappropriate access to an unrelated endpoint. Use: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

C.

This shortcut would undermine Choose NGFW tap or mirrored IoT sensor placement for east-west visibility for: A manufacturing campus needs discovery of machine-to-machine traffic never routed to the internet. The present situation is: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. Here the unsafe move is: Whitelist one transient IP as if it permanently identifies a medical pump. That could cause: A reused address grants inappropriate access to an unrelated endpoint. Use: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

D.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. Here the unsafe move is: Whitelist one transient IP as if it permanently identifies a medical pump. That could cause: A reused address grants inappropriate access to an unrelated endpoint. Use: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

Question 690

A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. Suppose the team implements this unsafe shortcut: Whitelist one transient IP as if it permanently identifies a medical pump. Which concrete security or availability failure is most likely?

  1. Undiscovered branch sensors retain default access while licensing and ingest costs rise
  2. A reused address grants inappropriate access to an unrelated endpoint
  3. Virtualized east-west assets remain unknown to risk and policy engines
  4. Unseen branch endpoints may access critical services without risk classification

Answer & Explanations

Correct answer: B

A.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The more pertinent consequence is: A reused address grants inappropriate access to an unrelated endpoint. Prevent it by: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

B.

A reused address grants inappropriate access to an unrelated endpoint. This follows when the team chooses the shortcut: Whitelist one transient IP as if it permanently identifies a medical pump. The situation is: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The correction is: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time. The observable test is: Change a pilot device's DHCP lease and verify it still matches the intended restricted policy.

C.

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 manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The more pertinent consequence is: A reused address grants inappropriate access to an unrelated endpoint. Prevent it by: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

D.

That outcome arises from a different failure: Unseen branch endpoints may access critical services without risk classification. The related situation is: A logistics provider identifies warehouse scanners across hundreds of low-bandwidth branches. In the present case: A manufacturer replaces a barcode scanner without carrying over the old scanner's IP-level trust. The more pertinent consequence is: A reused address grants inappropriate access to an unrelated endpoint. Prevent it by: Design Device-ID policy matching from trusted device attributes rather than static DHCP addresses that change over time.

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