Question 270
To avoid treating a restore point as a reliable recovery from destructive ransomware, which measure best meets the requirement?
- Windows Event ID 4688 auditing
- System Restore limitation
- Windows Firewall log review
- Defender isolation action
- VSS snapshot controls
Explanation
Correct Answer
B:Restore points can be deleted or compromised and do not replace tested offline backups; this mechanism directly supports the requirement to avoid treating a restore point as a reliable recovery from destructive ransomware.
Incorrect Answers
A:Process creation records relate executables to parent context when command-line inclusion is configured; that is useful when the task is to trace suspicious process creation and command-line behavior, not the stated requirement to avoid treating a restore point as a reliable recovery from destructive ransomware.
C:Host filtering logs distinguish endpoint policy drops from perimeter network failures; its operational purpose is to explain why a particular inbound TCP connection was blocked locally, not to achieve the specific requirement to avoid treating a restore point as a reliable recovery from destructive ransomware.
D:EDR-mediated network containment reduces spread yet permits designated management communication; applying it would serve disconnect a suspected compromised workstation while preserving investigation options without directly satisfying the goal to avoid treating a restore point as a reliable recovery from destructive ransomware.
E:Monitoring snapshot destruction helps identify ransomware preparation before recovery options disappear; it addresses the different need to detect hostile deletion of shadow copies after malicious execution, leaving the requested ability to avoid treating a restore point as a reliable recovery from destructive ransomware unresolved.
Question 271
To detect hostile deletion of shadow copies after malicious execution, what control should be selected?
- Scheduled task auditing
- VSS snapshot controls
- Defender isolation action
- Windows Event ID 4672 review
Explanation
Correct Answer
B:Monitoring snapshot destruction helps identify ransomware preparation before recovery options disappear; it supplies the specific control needed to detect hostile deletion of shadow copies after malicious execution.
Incorrect Answers
A:Task registration and execution events reveal execution paths that recur without interactive user actions; it could help someone trying to discover persistence established through a newly created privileged task, but the problem is instead to detect hostile deletion of shadow copies after malicious execution.
C:EDR-mediated network containment reduces spread yet permits designated management communication; a team would select it to disconnect a suspected compromised workstation while preserving investigation options, which does not provide the particular result to detect hostile deletion of shadow copies after malicious execution.
D:Special-privilege logon events highlight elevated token assignments when audit policy captures them; its operational purpose is to identify sessions receiving sensitive administrative privileges, not to achieve the specific requirement to detect hostile deletion of shadow copies after malicious execution.
Question 272
To explain why a particular inbound TCP connection was blocked locally, which security control is most appropriate?
- Defender isolation action
- Windows Firewall log review
- VSS snapshot controls
- Registry autorun review
Explanation
Correct Answer
B:Host filtering logs distinguish endpoint policy drops from perimeter network failures; that is why it addresses the operational task to explain why a particular inbound TCP connection was blocked locally.
Incorrect Answers
A:EDR-mediated network containment reduces spread yet permits designated management communication; although relevant to disconnect a suspected compromised workstation while preserving investigation options, it does not by itself achieve the required task to explain why a particular inbound TCP connection was blocked locally.
C:Monitoring snapshot destruction helps identify ransomware preparation before recovery options disappear; that is useful when the task is to detect hostile deletion of shadow copies after malicious execution, not the stated requirement to explain why a particular inbound TCP connection was blocked locally.
D:Startup registry entries can launch programs at logon or boot, requiring signed-file and change-context analysis; a team would select it to find malicious persistence in common Run and service startup locations, which does not provide the particular result to explain why a particular inbound TCP connection was blocked locally.
Question 273
To discover persistence established through a newly created privileged task, what would a Windows endpoint administrator implement or use?
- VSS snapshot controls
- Windows Firewall log review
- Scheduled task auditing
- Windows recovery environment control
Explanation
Correct Answer
C:Task registration and execution events reveal execution paths that recur without interactive user actions; its relevant protective or investigative effect is to discover persistence established through a newly created privileged task.
Incorrect Answers
A:Monitoring snapshot destruction helps identify ransomware preparation before recovery options disappear; the outcome it supports is to detect hostile deletion of shadow copies after malicious execution, whereas this scenario asks defenders to discover persistence established through a newly created privileged task.
B:Host filtering logs distinguish endpoint policy drops from perimeter network failures; although relevant to explain why a particular inbound TCP connection was blocked locally, it does not by itself achieve the required task to discover persistence established through a newly created privileged task.
D:Firmware, drive encryption and physical access restrictions limit offline manipulation of workstation data; that is useful when the task is to stop unauthorized boot into alternative recovery tooling on protected laptops, not the stated requirement to discover persistence established through a newly created privileged task.
Question 274
To find malicious persistence in common Run and service startup locations, which practice addresses that objective?
- VSS snapshot controls
- Registry autorun review
- System Restore limitation
- Scheduled task auditing
Explanation
Correct Answer
B:Startup registry entries can launch programs at logon or boot, requiring signed-file and change-context analysis; the requested outcome is precisely to find malicious persistence in common Run and service startup locations.
Incorrect Answers
A:Monitoring snapshot destruction helps identify ransomware preparation before recovery options disappear; its mechanism supports detect hostile deletion of shadow copies after malicious execution, while the requested control must be able to find malicious persistence in common Run and service startup locations.
C:Restore points can be deleted or compromised and do not replace tested offline backups; although relevant to avoid treating a restore point as a reliable recovery from destructive ransomware, it does not by itself achieve the required task to find malicious persistence in common Run and service startup locations.
D:Task registration and execution events reveal execution paths that recur without interactive user actions; it could help someone trying to discover persistence established through a newly created privileged task, but the problem is instead to find malicious persistence in common Run and service startup locations.
Question 275
To stop unauthorized boot into alternative recovery tooling on protected laptops, what is the relevant defensive action?
- System Restore limitation
- Windows recovery environment control
- Registry autorun review
- VSS snapshot controls
- Scheduled task auditing
Explanation
Correct Answer
B:Firmware, drive encryption and physical access restrictions limit offline manipulation of workstation data; this choice fits the scenario because the team must stop unauthorized boot into alternative recovery tooling on protected laptops.
Incorrect Answers
A:Restore points can be deleted or compromised and do not replace tested offline backups; the technique works for situations involving avoid treating a restore point as a reliable recovery from destructive ransomware, rather than this need to stop unauthorized boot into alternative recovery tooling on protected laptops.
C:Startup registry entries can launch programs at logon or boot, requiring signed-file and change-context analysis; the outcome it supports is to find malicious persistence in common Run and service startup locations, whereas this scenario asks defenders to stop unauthorized boot into alternative recovery tooling on protected laptops.
D:Monitoring snapshot destruction helps identify ransomware preparation before recovery options disappear; although relevant to detect hostile deletion of shadow copies after malicious execution, it does not by itself achieve the required task to stop unauthorized boot into alternative recovery tooling on protected laptops.
E:Task registration and execution events reveal execution paths that recur without interactive user actions; it could help someone trying to discover persistence established through a newly created privileged task, but the problem is instead to stop unauthorized boot into alternative recovery tooling on protected laptops.
Question 276
To delegate only package-update privileges to a Linux operations group, which option most directly provides the capability?
- PAM password quality
- PAM faillock
- SSH AllowGroups restriction
- sudoers least privilege
Explanation
Correct Answer
D:Command-scoped sudo rules reduce the need for unrestricted root shells and can be logged for accountability; this mechanism directly supports the requirement to delegate only package-update privileges to a Linux operations group.
Incorrect Answers
A:PAM policy modules enforce complexity or quality checks when participating authentication services call them; it addresses the different need to reject weak passwords during local account changes, leaving the requested ability to delegate only package-update privileges to a Linux operations group unresolved.
B:Failure counting can slow online guessing while administrators account for denial-of-service and unlock behavior; the technique works for situations involving temporarily restrict repeated unsuccessful Linux account authentication, rather than this need to delegate only package-update privileges to a Linux operations group.
C:sshd membership checks provide an additional admission layer beyond file permissions or network connectivity; its mechanism supports limit which existing Linux accounts may initiate remote shell access, while the requested control must be able to delegate only package-update privileges to a Linux operations group.
Question 277
To reject weak passwords during local account changes, which control achieves the target outcome?
- Account expiration
- sudoers least privilege
- PAM password quality
- PAM faillock
Explanation
Correct Answer
C:PAM policy modules enforce complexity or quality checks when participating authentication services call them; it supplies the specific control needed to reject weak passwords during local account changes.
Incorrect Answers
A:Account aging disables credentials at a configured date, avoiding forgotten long-lived access; applying it would serve remove login capability from temporary contractor accounts after project closure without directly satisfying the goal to reject weak passwords during local account changes.
B:Command-scoped sudo rules reduce the need for unrestricted root shells and can be logged for accountability; it addresses the different need to delegate only package-update privileges to a Linux operations group, leaving the requested ability to reject weak passwords during local account changes unresolved.
D:Failure counting can slow online guessing while administrators account for denial-of-service and unlock behavior; its mechanism supports temporarily restrict repeated unsuccessful Linux account authentication, while the requested control must be able to reject weak passwords during local account changes.
Question 278
To temporarily restrict repeated unsuccessful Linux account authentication, which solution should be adopted?
- PAM password quality
- sudoers least privilege
- PAM faillock
- SSH root-login prohibition
Explanation
Correct Answer
C:Failure counting can slow online guessing while administrators account for denial-of-service and unlock behavior; that is why it addresses the operational task to temporarily restrict repeated unsuccessful Linux account authentication.
Incorrect Answers
A:PAM policy modules enforce complexity or quality checks when participating authentication services call them; its operational purpose is to reject weak passwords during local account changes, not to achieve the specific requirement to temporarily restrict repeated unsuccessful Linux account authentication.
B:Command-scoped sudo rules reduce the need for unrestricted root shells and can be logged for accountability; applying it would serve delegate only package-update privileges to a Linux operations group without directly satisfying the goal to temporarily restrict repeated unsuccessful Linux account authentication.
D:Disabling direct root SSH entry improves attribution and reduces direct attack opportunities against a shared identity; the technique works for situations involving force administrators to enter through named accounts before elevation, rather than this need to temporarily restrict repeated unsuccessful Linux account authentication.
Question 279
To avoid reusable passwords for administrator remote access, which of the available controls is suitable?
- Account expiration
- SSH public-key login
- SSH root-login prohibition
- File permission chmod
Explanation
Correct Answer
B:SSH challenges users to demonstrate private-key possession while encrypting the management session; its relevant protective or investigative effect is to avoid reusable passwords for administrator remote access.
Incorrect Answers
A:Account aging disables credentials at a configured date, avoiding forgotten long-lived access; a team would select it to remove login capability from temporary contractor accounts after project closure, which does not provide the particular result to avoid reusable passwords for administrator remote access.
C:Disabling direct root SSH entry improves attribution and reduces direct attack opportunities against a shared identity; applying it would serve force administrators to enter through named accounts before elevation without directly satisfying the goal to avoid reusable passwords for administrator remote access.
D:POSIX permission bits determine access for the file owner, group and others independently of a firewall; it addresses the different need to remove group and world write privileges from a sensitive configuration file, leaving the requested ability to avoid reusable passwords for administrator remote access unresolved.
Question 280
To force administrators to enter through named accounts before elevation, which option is the direct technical match?
- SSH root-login prohibition
- Account expiration
- POSIX ACL management
- SSH AllowGroups restriction
- PAM faillock
Explanation
Correct Answer
A:Disabling direct root SSH entry improves attribution and reduces direct attack opportunities against a shared identity; the requested outcome is precisely to force administrators to enter through named accounts before elevation.
Incorrect Answers
B:Account aging disables credentials at a configured date, avoiding forgotten long-lived access; a team would select it to remove login capability from temporary contractor accounts after project closure, which does not provide the particular result to force administrators to enter through named accounts before elevation.
C:Extended ACL entries supplement traditional owner/group/other bits with per-principal permissions; its operational purpose is to give one additional service identity file access without broad group membership, not to achieve the specific requirement to force administrators to enter through named accounts before elevation.
D:sshd membership checks provide an additional admission layer beyond file permissions or network connectivity; applying it would serve limit which existing Linux accounts may initiate remote shell access without directly satisfying the goal to force administrators to enter through named accounts before elevation.
E:Failure counting can slow online guessing while administrators account for denial-of-service and unlock behavior; it addresses the different need to temporarily restrict repeated unsuccessful Linux account authentication, leaving the requested ability to force administrators to enter through named accounts before elevation unresolved.