100% Latest & Updated Palo Alto Networks NetSec-Architect Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 570
Which validation most directly demonstrates device metadata collector coverage is correctly designed for European medical campus? The security architecture board of European medical campus is preparing a new Securing IoT Environments program. The stakeholders have given the following specific requirement: Remote switches and wireless segments are invisible to the central Device Security asset model. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For European medical campus: Fail the panel over to a different site subnet and validate permitted control traffic and device mapping.
- For European medical campus: Compare known device inventories against collected protocol metadata and site identifiers.
- For European medical campus: Evaluate an approved camera flow and a medical control flow against reviewed risk-based rules.
- For European medical campus: Replay approved camera telemetry and anomalous destinations in a safe test segment.
Explanation
Correct Answer
B:This checks the relevant device metadata collector coverage enforcement path rather than a distant symptom. Compare known device inventories against collected protocol metadata and site identifiers. The expected evidence is Remote assets are correctly associated with their sites and observed behavior. Case R152-C143; angle 2; architecture design; option considered: Compare known device inventories against collected protocol metadata and site identifiers.
Incorrect Answers
A:This option addresses a different design objective: Device-ID after address change, not the primary control for device metadata collector coverage. It would be relevant where A building access panel loses its IP address while moving to a backup network and is wrongly denied. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C143; angle 2; architecture design; option considered: Fail the panel over to a different site subnet and validate permitted control traffic and device mapping.
C:This option addresses a different design objective: IoT risk-based policy sequencing, not the primary control for device metadata collector coverage. It would be relevant where A site imported all IoT policy recommendations without evaluating life-safety or business criticality. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C143; angle 2; architecture design; option considered: Evaluate an approved camera flow and a medical control flow against reviewed risk-based rules.
D:This option addresses a different design objective: Device profile drift response, not the primary control for device metadata collector coverage. It would be relevant where A previously trusted smart camera starts initiating DNS and outbound destinations outside its expected behavior. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C143; angle 2; architecture design; option considered: Replay approved camera telemetry and anomalous destinations in a safe test segment.
Question 571
Which design assumption should the architect REJECT when evaluating device metadata collector coverage for European medical campus? The security architecture board of European medical campus is preparing a new Securing IoT Environments program. The stakeholders have given the following specific requirement: Remote switches and wireless segments are invisible to the central Device Security asset model. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For European medical campus: Compare known device inventories against collected protocol metadata and site identifiers.
- For European medical campus: Move all asset IPs into a spreadsheet and label the list live device telemetry.
- For European medical campus: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
- For European medical campus: Remote assets are correctly associated with their sites and observed behavior.
Explanation
Correct Answer
B:Reject this assumption: Move all asset IPs into a spreadsheet and label the list live device telemetry. It does not establish device metadata collector coverage; the supported architecture is Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. Verify it by: Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C143; angle 3; architecture design; option considered: Move all asset IPs into a spreadsheet and label the list live device telemetry.
Incorrect Answers
A:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Compare known device inventories against collected protocol metadata and site identifiers. It is consistent with the required outcome: Remote assets are correctly associated with their sites and observed behavior. Case R152-C143; angle 3; architecture design; option considered: Compare known device inventories against collected protocol metadata and site identifiers.
C:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. It is consistent with the required outcome: Remote assets are correctly associated with their sites and observed behavior. Case R152-C143; angle 3; architecture design; option considered: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Remote assets are correctly associated with their sites and observed behavior. It is consistent with the required outcome: Remote assets are correctly associated with their sites and observed behavior. Case R152-C143; angle 3; architecture design; option considered: Remote assets are correctly associated with their sites and observed behavior.
Question 572
Select TWO directly linked controls for European medical campus: the architectural remedy and its decisive validation. The security architecture board of European medical campus is preparing a new Securing IoT Environments program. The stakeholders have given the following specific requirement: Remote switches and wireless segments are invisible to the central Device Security asset model. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For European medical campus: Generate a known local device conversation and verify it is observed at the collection point.
- For European medical campus: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
- For European medical campus: Compare known device inventories against collected protocol metadata and site identifiers.
- For European medical campus: Move all asset IPs into a spreadsheet and label the list live device telemetry.
- For European medical campus: Deploy supported Device Security passive discovery using existing network telemetry and nonintrusive collection sources.
Explanation
Correct Answer
B:This directly addresses the recorded gap: Remote switches and wireless segments are invisible to the central Device Security asset model. The architectural control is Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. The decisive test is Compare known device inventories against collected protocol metadata and site identifiers. The objective is Remote assets are correctly associated with their sites and observed behavior. Case R152-C143; angle 4; architecture design; option considered: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
C:This checks the relevant device metadata collector coverage enforcement path rather than a distant symptom. Compare known device inventories against collected protocol metadata and site identifiers. The expected evidence is Remote assets are correctly associated with their sites and observed behavior. Case R152-C143; angle 4; architecture design; option considered: Compare known device inventories against collected protocol metadata and site identifiers.
Incorrect Answers
A:This option addresses a different design objective: Network sensor placement, not the primary control for device metadata collector coverage. It would be relevant where IoT discovery sensors placed on an internet edge miss east-west exchanges between campus operational VLANs. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C143; angle 4; architecture design; option considered: Generate a known local device conversation and verify it is observed at the collection point.
D:This is an unsafe or insufficient shortcut for device metadata collector coverage: Move all asset IPs into a spreadsheet and label the list live device telemetry. The scoped requirement instead calls for Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. Case R152-C143; angle 4; architecture design; option considered: Move all asset IPs into a spreadsheet and label the list live device telemetry.
E:Passive asset inventory addresses a different architectural concern, such as when hospitals have unmanaged pumps that cannot accept scanning agents, and asset inventory is incomplete. It does not establish device metadata collector coverage here. The decisive test is to compare known device inventories against collected protocol metadata and site identifiers.
Question 573
For Multinational retail company, which is the most directly supported architectural control for device metadata collector coverage? After Multinational retail company completed a limited security transformation pilot, reviewers observed a control gap: Remote switches and wireless segments are invisible to the central Device Security asset model. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For Multinational retail company: Choose traffic observation points that see the relevant switch, firewall and industrial device metadata.
- For Multinational retail company: Develop an approved application-specific Device-ID rule for the pump profile with a monitored exception process.
- For Multinational retail company: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
- For Multinational retail company: Design Device-ID policy that references approved device attributes with site scope and mapping freshness checks.
Explanation
Correct Answer
C:This directly addresses the recorded gap: Remote switches and wireless segments are invisible to the central Device Security asset model. The architectural control is Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. The decisive test is Compare known device inventories against collected protocol metadata and site identifiers. The objective is Remote assets are correctly associated with their sites and observed behavior. Case R152-C144; angle 1; post-pilot control gap; option considered: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
Incorrect Answers
A:This option addresses a different design objective: Network sensor placement, not the primary control for device metadata collector coverage. It would be relevant where IoT discovery sensors placed on an internet edge miss east-west exchanges between campus operational VLANs. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C144; angle 1; post-pilot control gap; option considered: Choose traffic observation points that see the relevant switch, firewall and industrial device metadata.
B:This option addresses a different design objective: Medical IoT least privilege, not the primary control for device metadata collector coverage. It would be relevant where An infusion pump needs vendor cloud telemetry but should never initiate unrestricted RDP to corporate servers. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C144; angle 1; post-pilot control gap; option considered: Develop an approved application-specific Device-ID rule for the pump profile with a monitored exception process.
D:This option addresses a different design objective: Device-ID after address change, not the primary control for device metadata collector coverage. It would be relevant where A building access panel loses its IP address while moving to a backup network and is wrongly denied. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C144; angle 1; post-pilot control gap; option considered: Design Device-ID policy that references approved device attributes with site scope and mapping freshness checks.
Question 574
Which validation most directly demonstrates device metadata collector coverage is correctly designed for Multinational retail company? After Multinational retail company completed a limited security transformation pilot, reviewers observed a control gap: Remote switches and wireless segments are invisible to the central Device Security asset model. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For Multinational retail company: Fail the panel over to a different site subnet and validate permitted control traffic and device mapping.
- For Multinational retail company: Compare known device inventories against collected protocol metadata and site identifiers.
- For Multinational retail company: Check supported models and licenses in the proposed deployment and validate a test device-based rule.
- For Multinational retail company: Allow the documented telemetry endpoint and deny an unauthorized administrative connection.
Explanation
Correct Answer
B:This checks the relevant device metadata collector coverage enforcement path rather than a distant symptom. Compare known device inventories against collected protocol metadata and site identifiers. The expected evidence is Remote assets are correctly associated with their sites and observed behavior. Case R152-C144; angle 2; post-pilot control gap; option considered: Compare known device inventories against collected protocol metadata and site identifiers.
Incorrect Answers
A:This option addresses a different design objective: Device-ID after address change, not the primary control for device metadata collector coverage. It would be relevant where A building access panel loses its IP address while moving to a backup network and is wrongly denied. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C144; angle 2; post-pilot control gap; option considered: Fail the panel over to a different site subnet and validate permitted control traffic and device mapping.
C:Device-ID license boundary addresses a different architectural concern, such as when an architect assumes every firewall model can enforce device-based rules without licensing or platform assessment. It does not establish device metadata collector coverage here. The decisive test is to compare known device inventories against collected protocol metadata and site identifiers.
D:This option addresses a different design objective: Medical IoT least privilege, not the primary control for device metadata collector coverage. It would be relevant where An infusion pump needs vendor cloud telemetry but should never initiate unrestricted RDP to corporate servers. Here the necessary evidence is Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C144; angle 2; post-pilot control gap; option considered: Allow the documented telemetry endpoint and deny an unauthorized administrative connection.
Question 575
Which design assumption should the architect REJECT when evaluating device metadata collector coverage for Multinational retail company? After Multinational retail company completed a limited security transformation pilot, reviewers observed a control gap: Remote switches and wireless segments are invisible to the central Device Security asset model. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For Multinational retail company: Compare known device inventories against collected protocol metadata and site identifiers.
- For Multinational retail company: Remote assets are correctly associated with their sites and observed behavior.
- For Multinational retail company: Move all asset IPs into a spreadsheet and label the list live device telemetry.
- For Multinational retail company: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
Explanation
Correct Answer
C:Reject this assumption: Move all asset IPs into a spreadsheet and label the list live device telemetry. It does not establish device metadata collector coverage; the supported architecture is Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. Verify it by: Compare known device inventories against collected protocol metadata and site identifiers. Case R152-C144; angle 3; post-pilot control gap; option considered: Move all asset IPs into a spreadsheet and label the list live device telemetry.
Incorrect Answers
A:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Compare known device inventories against collected protocol metadata and site identifiers. It is consistent with the required outcome: Remote assets are correctly associated with their sites and observed behavior. Case R152-C144; angle 3; post-pilot control gap; option considered: Compare known device inventories against collected protocol metadata and site identifiers.
B:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Remote assets are correctly associated with their sites and observed behavior. It is consistent with the required outcome: Remote assets are correctly associated with their sites and observed behavior. Case R152-C144; angle 3; post-pilot control gap; option considered: Remote assets are correctly associated with their sites and observed behavior.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. It is consistent with the required outcome: Remote assets are correctly associated with their sites and observed behavior. Case R152-C144; angle 3; post-pilot control gap; option considered: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
Question 576
Select THREE linked elements for Multinational retail company: a supported architecture, the direct test, and the required outcome. After Multinational retail company completed a limited security transformation pilot, reviewers observed a control gap: Remote switches and wireless segments are invisible to the central Device Security asset model. The case assumes the affected flows and dependencies have been traced and all unrelated systems are functioning; choose the narrow design repair before wider deployment.
- For Multinational retail company: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
- For Multinational retail company: Use supported Device Security network segment context to distinguish overlapping-address asset populations.
- For Multinational retail company: Compare known device inventories against collected protocol metadata and site identifiers.
- For Multinational retail company: Operationally required controller access survives while unauthorized lateral traffic is denied.
- For Multinational retail company: Move all asset IPs into a spreadsheet and label the list live device telemetry.
- For Multinational retail company: Remote assets are correctly associated with their sites and observed behavior.
Explanation
Correct Answer
A:This directly addresses the recorded gap: Remote switches and wireless segments are invisible to the central Device Security asset model. The architectural control is Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. The decisive test is Compare known device inventories against collected protocol metadata and site identifiers. The objective is Remote assets are correctly associated with their sites and observed behavior. Case R152-C144; angle 4; post-pilot control gap; option considered: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites.
C:This checks the relevant device metadata collector coverage enforcement path rather than a distant symptom. Compare known device inventories against collected protocol metadata and site identifiers. The expected evidence is Remote assets are correctly associated with their sites and observed behavior. Case R152-C144; angle 4; post-pilot control gap; option considered: Compare known device inventories against collected protocol metadata and site identifiers.
F:The required result is remote assets are correctly associated with their sites and observed behavior. Apply this control: Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. Verify with: Compare known device inventories against collected protocol metadata and site identifiers.
Incorrect Answers
B:Shared subnet site identity ambiguity addresses a different architectural concern, such as when two plants reuse the same private IP range, causing aggregated Device-ID events to be assigned to the wrong equipment. It does not establish device metadata collector coverage here. The decisive test is to compare known device inventories against collected protocol metadata and site identifiers.
D:Industrial OT segmentation boundaries addresses a different architectural concern, such as when programmable controllers and engineering workstations share unrestricted policy although they have different roles. It does not establish device metadata collector coverage here. The decisive test is to compare known device inventories against collected protocol metadata and site identifiers.
E:This is an unsafe or insufficient shortcut for device metadata collector coverage: Move all asset IPs into a spreadsheet and label the list live device telemetry. The scoped requirement instead calls for Plan supported virtual metadata collection or protocol telemetry integrations from distributed sites. Case R152-C144; angle 4; post-pilot control gap; option considered: Move all asset IPs into a spreadsheet and label the list live device telemetry.
Question 577
For Cloud-native manufacturing firm, which is the most directly supported architectural control for dhcp and identity correlation? The security architecture board of Cloud-native manufacturing firm is preparing a new Securing IoT Environments program. The stakeholders have given the following specific requirement: A security team misattributes events after DHCP leases change for medical and guest devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Choose traffic observation points that see the relevant switch, firewall and industrial device metadata.
- For Cloud-native manufacturing firm: Design Device-ID policy that references approved device attributes with site scope and mapping freshness checks.
- For Cloud-native manufacturing firm: Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current.
- For Cloud-native manufacturing firm: Review Device Security behavior deviations and require approval before expanding its allowed profile.
Explanation
Correct Answer
C:This directly addresses the recorded gap: A security team misattributes events after DHCP leases change for medical and guest devices. The architectural control is Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current. The decisive test is Move a test device between two leases and confirm logs continue to reflect its identity. The objective is Security events track device context across the lease update instead of treating IP as permanent identity. Case R152-C145; angle 1; architecture design; option considered: Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current.
Incorrect Answers
A:This option addresses a different design objective: Network sensor placement, not the primary control for dhcp and identity correlation. It would be relevant where IoT discovery sensors placed on an internet edge miss east-west exchanges between campus operational VLANs. Here the necessary evidence is Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 1; architecture design; option considered: Choose traffic observation points that see the relevant switch, firewall and industrial device metadata.
B:This option addresses a different design objective: Device-ID after address change, not the primary control for dhcp and identity correlation. It would be relevant where A building access panel loses its IP address while moving to a backup network and is wrongly denied. Here the necessary evidence is Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 1; architecture design; option considered: Design Device-ID policy that references approved device attributes with site scope and mapping freshness checks.
D:This option addresses a different design objective: Device profile drift response, not the primary control for dhcp and identity correlation. It would be relevant where A previously trusted smart camera starts initiating DNS and outbound destinations outside its expected behavior. Here the necessary evidence is Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 1; architecture design; option considered: Review Device Security behavior deviations and require approval before expanding its allowed profile.
Question 578
Which validation most directly demonstrates dhcp and identity correlation is correctly designed for Cloud-native manufacturing firm? The security architecture board of Cloud-native manufacturing firm is preparing a new Securing IoT Environments program. The stakeholders have given the following specific requirement: A security team misattributes events after DHCP leases change for medical and guest devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Evaluate an approved camera flow and a medical control flow against reviewed risk-based rules.
- For Cloud-native manufacturing firm: Fail the panel over to a different site subnet and validate permitted control traffic and device mapping.
- For Cloud-native manufacturing firm: Observe the same RFC1918 address in each plant and verify the separate device contexts and enforcement.
- For Cloud-native manufacturing firm: Move a test device between two leases and confirm logs continue to reflect its identity.
Explanation
Correct Answer
D:This checks the relevant dhcp and identity correlation enforcement path rather than a distant symptom. Move a test device between two leases and confirm logs continue to reflect its identity. The expected evidence is Security events track device context across the lease update instead of treating IP as permanent identity. Case R152-C145; angle 2; architecture design; option considered: Move a test device between two leases and confirm logs continue to reflect its identity.
Incorrect Answers
A:This option addresses a different design objective: IoT risk-based policy sequencing, not the primary control for dhcp and identity correlation. It would be relevant where A site imported all IoT policy recommendations without evaluating life-safety or business criticality. Here the necessary evidence is Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 2; architecture design; option considered: Evaluate an approved camera flow and a medical control flow against reviewed risk-based rules.
B:This option addresses a different design objective: Device-ID after address change, not the primary control for dhcp and identity correlation. It would be relevant where A building access panel loses its IP address while moving to a backup network and is wrongly denied. Here the necessary evidence is Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 2; architecture design; option considered: Fail the panel over to a different site subnet and validate permitted control traffic and device mapping.
C:Shared subnet site identity ambiguity addresses a different architectural concern, such as when two plants reuse the same private IP range, causing aggregated Device-ID events to be assigned to the wrong equipment. It does not establish dhcp and identity correlation here. The decisive test is to move a test device between two leases and confirm logs continue to reflect its identity.
Question 579
Which design assumption should the architect REJECT when evaluating dhcp and identity correlation for Cloud-native manufacturing firm? The security architecture board of Cloud-native manufacturing firm is preparing a new Securing IoT Environments program. The stakeholders have given the following specific requirement: A security team misattributes events after DHCP leases change for medical and guest devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current.
- For Cloud-native manufacturing firm: Write permanent device security exceptions keyed solely to the first IP observed.
- For Cloud-native manufacturing firm: Security events track device context across the lease update instead of treating IP as permanent identity.
- For Cloud-native manufacturing firm: Move a test device between two leases and confirm logs continue to reflect its identity.
Explanation
Correct Answer
B:Reject this assumption: Write permanent device security exceptions keyed solely to the first IP observed. It does not establish dhcp and identity correlation; the supported architecture is Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current. Verify it by: Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 3; architecture design; option considered: Write permanent device security exceptions keyed solely to the first IP observed.
Incorrect Answers
A:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current. It is consistent with the required outcome: Security events track device context across the lease update instead of treating IP as permanent identity. Case R152-C145; angle 3; architecture design; option considered: Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current.
C:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Security events track device context across the lease update instead of treating IP as permanent identity. It is consistent with the required outcome: Security events track device context across the lease update instead of treating IP as permanent identity. Case R152-C145; angle 3; architecture design; option considered: Security events track device context across the lease update instead of treating IP as permanent identity.
D:This is a valid design/control/evidence statement in the specified case, not the assumption to reject. Move a test device between two leases and confirm logs continue to reflect its identity. It is consistent with the required outcome: Security events track device context across the lease update instead of treating IP as permanent identity. Case R152-C145; angle 3; architecture design; option considered: Move a test device between two leases and confirm logs continue to reflect its identity.
Question 580
Select THREE linked elements for Cloud-native manufacturing firm: a supported architecture, the direct test, and the required outcome. The security architecture board of Cloud-native manufacturing firm is preparing a new Securing IoT Environments program. The stakeholders have given the following specific requirement: A security team misattributes events after DHCP leases change for medical and guest devices. No existing change is being reverted; select the most directly justified architecture for this stated requirement.
- For Cloud-native manufacturing firm: Write permanent device security exceptions keyed solely to the first IP observed.
- For Cloud-native manufacturing firm: Develop an approved application-specific Device-ID rule for the pump profile with a monitored exception process.
- For Cloud-native manufacturing firm: Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current.
- For Cloud-native manufacturing firm: Move a test device between two leases and confirm logs continue to reflect its identity.
- For Cloud-native manufacturing firm: Security events track device context across the lease update instead of treating IP as permanent identity.
- For Cloud-native manufacturing firm: Critical unmanaged assets become visible without requiring unsupported endpoint agents.
Explanation
Correct Answer
C:This directly addresses the recorded gap: A security team misattributes events after DHCP leases change for medical and guest devices. The architectural control is Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current. The decisive test is Move a test device between two leases and confirm logs continue to reflect its identity. The objective is Security events track device context across the lease update instead of treating IP as permanent identity. Case R152-C145; angle 4; architecture design; option considered: Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current.
D:This checks the relevant dhcp and identity correlation enforcement path rather than a distant symptom. Move a test device between two leases and confirm logs continue to reflect its identity. The expected evidence is Security events track device context across the lease update instead of treating IP as permanent identity. Case R152-C145; angle 4; architecture design; option considered: Move a test device between two leases and confirm logs continue to reflect its identity.
E:The required end state is Security events track device context across the lease update instead of treating IP as permanent identity. The architect must deploy Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current. and validate using Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 4; architecture design; option considered: Security events track device context across the lease update instead of treating IP as permanent identity.
Incorrect Answers
A:This is an unsafe or insufficient shortcut for dhcp and identity correlation: Write permanent device security exceptions keyed solely to the first IP observed. The scoped requirement instead calls for Correlate device discovery context with DHCP/network metadata to keep IP-to-device mappings current.
B:Medical IoT least privilege addresses a different architectural concern, such as when an infusion pump needs vendor cloud telemetry but should never initiate unrestricted RDP to corporate servers. It does not establish dhcp and identity correlation here. The decisive test is to move a test device between two leases and confirm logs continue to reflect its identity.
F:This option addresses a different design objective: Passive asset inventory, not the primary control for dhcp and identity correlation. It would be relevant where Hospitals have unmanaged pumps that cannot accept scanning agents, and asset inventory is incomplete. Here the necessary evidence is Move a test device between two leases and confirm logs continue to reflect its identity. Case R152-C145; angle 4; architecture design; option considered: Critical unmanaged assets become visible without requiring unsupported endpoint agents.
Palo Alto Networks Network Security Architect (NetSec-Architect) Practice Tests