Question 450
During Willow Retail's post-change review, desktop intrusion sequence was selected to investigate a suspicious unsigned executable on a managed Windows laptop. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- IoT devices may provide limited local telemetry and require network corroboration.
- A known filename alone is not sufficient evidence of compromise.
- A running service with an unfamiliar name is not necessarily malicious.
- Same display name on different endpoints may denote different principals.
Explanation
Correct Answer
B:The residual risk for this case is that a known filename alone is not sufficient evidence of compromise. This matters even after the measure to investigate a suspicious unsigned executable on a managed Windows laptop appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to iot camera compromise under the different requirement to scope unexpected connections from a managed surveillance camera. The current case instead requires managing the risk that a known filename alone is not sufficient evidence of compromise.
C:That caution belongs to linux persistence case under the different requirement to investigate an unfamiliar service that persists across server reboots. The current case instead requires managing the risk that a known filename alone is not sufficient evidence of compromise.
D:That caution belongs to cross-platform intrusion correlation under the different requirement to correlate one identity's suspicious access across Windows macOS and Linux hosts. The current case instead requires managing the risk that a known filename alone is not sufficient evidence of compromise.
Question 451
Northstar Manufacturing's security operations team must investigate an unfamiliar service that persists across server reboots. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- IoT camera compromise
- Laptop remote administration misuse
- Linux persistence case
- Mobile-device policy breach
Explanation
Correct Answer
C:Linux persistence case addresses this case because the team should inspect service configuration executable hashes and authorization history. The direct verification is that timeline ties an unapproved service definition to observed execution.
Incorrect Answers
A:IoT camera compromise would address a different operational issue: scope unexpected connections from a managed surveillance camera. The separate task is to compare firmware and network observations to the device's approved recorder flows, rather than the requested outcome to investigate an unfamiliar service that persists across server reboots.
B:Laptop remote administration misuse would address a different operational issue: investigate repeated remote-management sessions to an employee laptop. The separate task is to join identity approval remote-access logs and endpoint session start events, rather than the requested outcome to investigate an unfamiliar service that persists across server reboots.
D:Mobile-device policy breach would address a different operational issue: assess a managed phone accessing confidential resources without required posture. The separate task is to correlate MDM compliance state identity access and application audit events, rather than the requested outcome to investigate an unfamiliar service that persists across server reboots.
Question 452
An authorized responder at Meridian Analytics has selected the linux persistence case approach to investigate an unfamiliar service that persists across server reboots. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Compare firmware and network observations to the device's approved recorder flows.
- Join identity approval remote-access logs and endpoint session start events.
- Correlate MDM compliance state identity access and application audit events.
- Inspect service configuration executable hashes and authorization history.
Explanation
Correct Answer
D:To investigate an unfamiliar service that persists across server reboots, this step operationalizes linux persistence case. In particular, inspect service configuration executable hashes and authorization history; acceptance requires that timeline ties an unapproved service definition to observed execution.
Incorrect Answers
A:This step implements iot camera compromise, aimed at scope unexpected connections from a managed surveillance camera. It does not carry out the needed step for linux persistence case, where responders must inspect service configuration executable hashes and authorization history.
B:This step implements laptop remote administration misuse, aimed at investigate repeated remote-management sessions to an employee laptop. It does not carry out the needed step for linux persistence case, where responders must inspect service configuration executable hashes and authorization history.
C:This step implements mobile-device policy breach, aimed at assess a managed phone accessing confidential resources without required posture. It does not carry out the needed step for linux persistence case, where responders must inspect service configuration executable hashes and authorization history.
Question 453
Highland Operations has performed this action as part of linux persistence case: Inspect service configuration executable hashes and authorization history. The requirement is to investigate an unfamiliar service that persists across server reboots. Which observation actually confirms the intended result?
- Timeline ties an unapproved service definition to observed execution.
- Unexpected destinations and configuration drift are documented with timestamps.
- Case identifies originating account approval and executed remote tasks.
- Logs identify rejected or allowed access for the affected mobile identity.
Explanation
Correct Answer
A:The relevant acceptance signal is that timeline ties an unapproved service definition to observed execution. It verifies the requested result to investigate an unfamiliar service that persists across server reboots rather than merely measuring unrelated activity.
Incorrect Answers
B:This is an acceptance observation for iot camera compromise, which deals with scope unexpected connections from a managed surveillance camera. It does not verify that timeline ties an unapproved service definition to observed execution in the specified case.
C:This is an acceptance observation for laptop remote administration misuse, which deals with investigate repeated remote-management sessions to an employee laptop. It does not verify that timeline ties an unapproved service definition to observed execution in the specified case.
D:This is an acceptance observation for mobile-device policy breach, which deals with assess a managed phone accessing confidential resources without required posture. It does not verify that timeline ties an unapproved service definition to observed execution in the specified case.
Question 454
During Lakeside Finance's post-change review, linux persistence case was selected to investigate an unfamiliar service that persists across server reboots. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- IoT devices may provide limited local telemetry and require network corroboration.
- A running service with an unfamiliar name is not necessarily malicious.
- Installed management software alone is not proof of unauthorized activity.
- Mobile network location alone does not establish device compliance.
Explanation
Correct Answer
B:The residual risk for this case is that a running service with an unfamiliar name is not necessarily malicious. This matters even after the measure to investigate an unfamiliar service that persists across server reboots appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to iot camera compromise under the different requirement to scope unexpected connections from a managed surveillance camera. The current case instead requires managing the risk that a running service with an unfamiliar name is not necessarily malicious.
C:That caution belongs to laptop remote administration misuse under the different requirement to investigate repeated remote-management sessions to an employee laptop. The current case instead requires managing the risk that a running service with an unfamiliar name is not necessarily malicious.
D:That caution belongs to mobile-device policy breach under the different requirement to assess a managed phone accessing confidential resources without required posture. The current case instead requires managing the risk that a running service with an unfamiliar name is not necessarily malicious.
Question 455
Cedar Health's security operations team must assess a managed phone accessing confidential resources without required posture. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Linux persistence case
- Desktop intrusion sequence
- Mobile-device policy breach
- IoT camera compromise
Explanation
Correct Answer
C:Mobile-device policy breach addresses this case because the team should correlate MDM compliance state identity access and application audit events. The direct verification is that logs identify rejected or allowed access for the affected mobile identity.
Incorrect Answers
A:Linux persistence case would address a different operational issue: investigate an unfamiliar service that persists across server reboots. The separate task is to inspect service configuration executable hashes and authorization history, rather than the requested outcome to assess a managed phone accessing confidential resources without required posture.
B:Desktop intrusion sequence would address a different operational issue: investigate a suspicious unsigned executable on a managed Windows laptop. The separate task is to collect process lineage persistence artifacts and security-event timeline, rather than the requested outcome to assess a managed phone accessing confidential resources without required posture.
D:IoT camera compromise would address a different operational issue: scope unexpected connections from a managed surveillance camera. The separate task is to compare firmware and network observations to the device's approved recorder flows, rather than the requested outcome to assess a managed phone accessing confidential resources without required posture.
Question 456
An authorized responder at Mariner Logistics has selected the mobile-device policy breach approach to assess a managed phone accessing confidential resources without required posture. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Inspect service configuration executable hashes and authorization history.
- Collect process lineage persistence artifacts and security-event timeline.
- Compare firmware and network observations to the device's approved recorder flows.
- Correlate MDM compliance state identity access and application audit events.
Explanation
Correct Answer
D:To assess a managed phone accessing confidential resources without required posture, this step operationalizes mobile-device policy breach. In particular, correlate MDM compliance state identity access and application audit events; acceptance requires that logs identify rejected or allowed access for the affected mobile identity.
Incorrect Answers
A:This step implements linux persistence case, aimed at investigate an unfamiliar service that persists across server reboots. It does not carry out the needed step for mobile-device policy breach, where responders must correlate MDM compliance state identity access and application audit events.
B:This step implements desktop intrusion sequence, aimed at investigate a suspicious unsigned executable on a managed Windows laptop. It does not carry out the needed step for mobile-device policy breach, where responders must correlate MDM compliance state identity access and application audit events.
C:This step implements iot camera compromise, aimed at scope unexpected connections from a managed surveillance camera. It does not carry out the needed step for mobile-device policy breach, where responders must correlate MDM compliance state identity access and application audit events.
Question 457
Pioneer Research has performed this action as part of mobile-device policy breach: Correlate MDM compliance state identity access and application audit events. The requirement is to assess a managed phone accessing confidential resources without required posture. Which observation actually confirms the intended result?
- Logs identify rejected or allowed access for the affected mobile identity.
- Timeline ties an unapproved service definition to observed execution.
- Case evidence links the binary's execution to its parent and persistence path.
- Unexpected destinations and configuration drift are documented with timestamps.
Explanation
Correct Answer
A:The relevant acceptance signal is that logs identify rejected or allowed access for the affected mobile identity. It verifies the requested result to assess a managed phone accessing confidential resources without required posture rather than merely measuring unrelated activity.
Incorrect Answers
B:This is an acceptance observation for linux persistence case, which deals with investigate an unfamiliar service that persists across server reboots. It does not verify that logs identify rejected or allowed access for the affected mobile identity in the specified case.
C:This is an acceptance observation for desktop intrusion sequence, which deals with investigate a suspicious unsigned executable on a managed Windows laptop. It does not verify that logs identify rejected or allowed access for the affected mobile identity in the specified case.
D:This is an acceptance observation for iot camera compromise, which deals with scope unexpected connections from a managed surveillance camera. It does not verify that logs identify rejected or allowed access for the affected mobile identity in the specified case.
Question 458
During Willow Retail's post-change review, mobile-device policy breach was selected to assess a managed phone accessing confidential resources without required posture. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- A running service with an unfamiliar name is not necessarily malicious.
- Mobile network location alone does not establish device compliance.
- A known filename alone is not sufficient evidence of compromise.
- IoT devices may provide limited local telemetry and require network corroboration.
Explanation
Correct Answer
B:The residual risk for this case is that mobile network location alone does not establish device compliance. This matters even after the measure to assess a managed phone accessing confidential resources without required posture appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to linux persistence case under the different requirement to investigate an unfamiliar service that persists across server reboots. The current case instead requires managing the risk that mobile network location alone does not establish device compliance.
C:That caution belongs to desktop intrusion sequence under the different requirement to investigate a suspicious unsigned executable on a managed Windows laptop. The current case instead requires managing the risk that mobile network location alone does not establish device compliance.
D:That caution belongs to iot camera compromise under the different requirement to scope unexpected connections from a managed surveillance camera. The current case instead requires managing the risk that mobile network location alone does not establish device compliance.
Question 459
Northstar Manufacturing's security operations team must scope unexpected connections from a managed surveillance camera. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Cross-platform intrusion correlation
- Linux persistence case
- IoT camera compromise
- Laptop remote administration misuse
Explanation
Correct Answer
C:IoT camera compromise addresses this case because the team should compare firmware and network observations to the device's approved recorder flows. The direct verification is that unexpected destinations and configuration drift are documented with timestamps.
Incorrect Answers
A:Cross-platform intrusion correlation would address a different operational issue: correlate one identity's suspicious access across Windows macOS and Linux hosts. The separate task is to normalize account IDs event times and endpoint telemetry before building a case, rather than the requested outcome to scope unexpected connections from a managed surveillance camera.
B:Linux persistence case would address a different operational issue: investigate an unfamiliar service that persists across server reboots. The separate task is to inspect service configuration executable hashes and authorization history, rather than the requested outcome to scope unexpected connections from a managed surveillance camera.
D:Laptop remote administration misuse would address a different operational issue: investigate repeated remote-management sessions to an employee laptop. The separate task is to join identity approval remote-access logs and endpoint session start events, rather than the requested outcome to scope unexpected connections from a managed surveillance camera.
Question 460
An authorized responder at Meridian Analytics has selected the IOT camera compromise approach to scope unexpected connections from a managed surveillance camera. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Normalize account IDs event times and endpoint telemetry before building a case.
- Inspect service configuration executable hashes and authorization history.
- Join identity approval remote-access logs and endpoint session start events.
- Compare firmware and network observations to the device's approved recorder flows.
Explanation
Correct Answer
D:To scope unexpected connections from a managed surveillance camera, this step operationalizes IOT camera compromise. In particular, compare firmware and network observations to the device's approved recorder flows; acceptance requires that unexpected destinations and configuration drift are documented with timestamps.
Incorrect Answers
A:This step implements cross-platform intrusion correlation, aimed at correlate one identity's suspicious access across Windows macOS and Linux hosts. It does not carry out the needed step for IOT camera compromise, where responders must compare firmware and network observations to the device's approved recorder flows.
B:This step implements linux persistence case, aimed at investigate an unfamiliar service that persists across server reboots. It does not carry out the needed step for IOT camera compromise, where responders must compare firmware and network observations to the device's approved recorder flows.
C:This step implements laptop remote administration misuse, aimed at investigate repeated remote-management sessions to an employee laptop. It does not carry out the needed step for IOT camera compromise, where responders must compare firmware and network observations to the device's approved recorder flows.
Performing Cybersecurity Using Cisco Security Technologies (CBRCOR) (350-201) Practice Tests