Question 450
To find obsolete applications still running after retirement approval, which protective or investigative measure applies?
- Privilege-restricted application
- Execution block audit mode
- Application inventory reconciliation
- Library loading control
- Package repository allowlist
Explanation
Correct Answer
C:Comparing actual executable inventory to approved catalogs exposes drift and unsupported software; this mechanism directly supports the requirement to find obsolete applications still running after retirement approval.
Incorrect Answers
A:Least-privilege execution limits damage from compromise while preserving needed user functions; that is useful when the task is to run an externally supplied utility without local administrator rights, not the stated requirement to find obsolete applications still running after retirement approval.
B:Audit-only events reveal potential operational breakage without immediately denying legitimate processes; a team would select it to test an application-control policy before enforcing it everywhere, which does not provide the particular result to find obsolete applications still running after retirement approval.
D:Search-path and dependency restrictions address sideloading even when the main executable is approved; applying it would serve prevent signed applications from importing untrusted local DLLs without directly satisfying the goal to find obsolete applications still running after retirement approval.
E:Approved sources and integrity validation restrict dependency supply-chain exposure; it addresses the different need to stop developers installing arbitrary unreviewed packages in builds, leaving the requested ability to find obsolete applications still running after retirement approval unresolved.
Question 451
To test an application-control policy before enforcing it everywhere, which protective or investigative measure applies?
- Privilege-restricted application
- Execution block audit mode
- Library loading control
- Code signing pipeline
Explanation
Correct Answer
B:Audit-only events reveal potential operational breakage without immediately denying legitimate processes; it supplies the specific control needed to test an application-control policy before enforcing it everywhere.
Incorrect Answers
A:Least-privilege execution limits damage from compromise while preserving needed user functions; it could help someone trying to run an externally supplied utility without local administrator rights, but the problem is instead to test an application-control policy before enforcing it everywhere.
C:Search-path and dependency restrictions address sideloading even when the main executable is approved; a team would select it to prevent signed applications from importing untrusted local DLLs, which does not provide the particular result to test an application-control policy before enforcing it everywhere.
D:Publisher signatures link deliverables to controlled private keys and expose unauthorized modification; its operational purpose is to authenticate distributed business application packages before installation, not to achieve the specific requirement to test an application-control policy before enforcing it everywhere.
Question 452
To run a document viewer with reduced filesystem and network privileges, what is the most direct option?
- Process sandbox
- Disposable browser environment
- Container runtime isolation
- Micro-VM sandbox
Explanation
Correct Answer
A:Sandbox boundaries limit capabilities available to untrusted parsed content after exploitation; that is why it addresses the operational task to run a document viewer with reduced filesystem and network privileges.
Incorrect Answers
B:Isolated sessions are discarded after use, constraining persistence and local resource access; it could help someone trying to keep potentially hostile websites away from the primary workstation OS, but the problem is instead to run a document viewer with reduced filesystem and network privileges.
C:Kernel isolation narrows process reach but shares the host kernel and needs defense in depth; that is useful when the task is to run untrusted services with limited namespaces and capabilities, not the stated requirement to run a document viewer with reduced filesystem and network privileges.
D:Hardware virtualization strengthens separation relative to an ordinary shared-kernel process sandbox; a team would select it to isolate code using a lightweight dedicated guest kernel boundary, which does not provide the particular result to run a document viewer with reduced filesystem and network privileges.
Question 453
To keep potentially hostile websites away from the primary workstation OS, what should defenders select?
- Process sandbox
- Outbound sandbox policy
- Disposable browser environment
- Micro-VM sandbox
Explanation
Correct Answer
C:Isolated sessions are discarded after use, constraining persistence and local resource access; its relevant protective or investigative effect is to keep potentially hostile websites away from the primary workstation OS.
Incorrect Answers
A:Sandbox boundaries limit capabilities available to untrusted parsed content after exploitation; the outcome it supports is to run a document viewer with reduced filesystem and network privileges, whereas this scenario asks defenders to keep potentially hostile websites away from the primary workstation OS.
B:Network egress restrictions reduce exfiltration and callback opportunities inside the isolated runtime; although relevant to stop a test application from making arbitrary internet connections, it does not by itself achieve the required task to keep potentially hostile websites away from the primary workstation OS.
D:Hardware virtualization strengthens separation relative to an ordinary shared-kernel process sandbox; that is useful when the task is to isolate code using a lightweight dedicated guest kernel boundary, not the stated requirement to keep potentially hostile websites away from the primary workstation OS.
Question 454
To run untrusted services with limited namespaces and capabilities, which mechanism best fits?
- Outbound sandbox policy
- Application-specific filesystem access
- Container runtime isolation
- Disposable browser environment
Explanation
Correct Answer
C:Kernel isolation narrows process reach but shares the host kernel and needs defense in depth; the requested outcome is precisely to run untrusted services with limited namespaces and capabilities.
Incorrect Answers
A:Network egress restrictions reduce exfiltration and callback opportunities inside the isolated runtime; its mechanism supports stop a test application from making arbitrary internet connections, while the requested control must be able to run untrusted services with limited namespaces and capabilities.
B:Filesystem confinement limits the data a compromised conversion process can alter or read; the outcome it supports is to allow a media converter to write only one output directory, whereas this scenario asks defenders to run untrusted services with limited namespaces and capabilities.
D:Isolated sessions are discarded after use, constraining persistence and local resource access; it could help someone trying to keep potentially hostile websites away from the primary workstation OS, but the problem is instead to run untrusted services with limited namespaces and capabilities.
Question 455
To isolate code using a lightweight dedicated guest kernel boundary, which measure best meets the requirement?
- Micro-VM sandbox
- Outbound sandbox policy
- Application-specific filesystem access
- Container runtime isolation
- Read-only application container
Explanation
Correct Answer
A:Hardware virtualization strengthens separation relative to an ordinary shared-kernel process sandbox; this choice fits the scenario because the team must isolate code using a lightweight dedicated guest kernel boundary.
Incorrect Answers
B:Network egress restrictions reduce exfiltration and callback opportunities inside the isolated runtime; its mechanism supports stop a test application from making arbitrary internet connections, while the requested control must be able to isolate code using a lightweight dedicated guest kernel boundary.
C:Filesystem confinement limits the data a compromised conversion process can alter or read; the outcome it supports is to allow a media converter to write only one output directory, whereas this scenario asks defenders to isolate code using a lightweight dedicated guest kernel boundary.
D:Kernel isolation narrows process reach but shares the host kernel and needs defense in depth; although relevant to run untrusted services with limited namespaces and capabilities, it does not by itself achieve the required task to isolate code using a lightweight dedicated guest kernel boundary.
E:Immutable root filesystems restrict persistent application-layer changes while writable mounts remain separate; it could help someone trying to prevent a workload from modifying its deployed executable tree, but the problem is instead to isolate code using a lightweight dedicated guest kernel boundary.
Question 456
To allow a media converter to write only one output directory, what control should be selected?
- Micro-VM sandbox
- Ephemeral sandbox lifecycle
- Sandbox escape patching
- Process sandbox
- Application-specific filesystem access
- Outbound sandbox policy
Explanation
Correct Answer
E:Filesystem confinement limits the data a compromised conversion process can alter or read; this mechanism directly supports the requirement to allow a media converter to write only one output directory.
Incorrect Answers
A:Hardware virtualization strengthens separation relative to an ordinary shared-kernel process sandbox; it addresses the different need to isolate code using a lightweight dedicated guest kernel boundary, leaving the requested ability to allow a media converter to write only one output directory unresolved.
B:Throwaway environments prevent long-term accumulation of attacker modifications and artifacts; the technique works for situations involving delete risky downloaded-content changes after analysis completes, rather than this need to allow a media converter to write only one output directory.
C:Isolation remains dependent on patched escape surfaces and correct boundary configuration; its mechanism supports mitigate a known host-kernel vulnerability reachable from guest code, while the requested control must be able to allow a media converter to write only one output directory.
D:Sandbox boundaries limit capabilities available to untrusted parsed content after exploitation; the outcome it supports is to run a document viewer with reduced filesystem and network privileges, whereas this scenario asks defenders to allow a media converter to write only one output directory.
F:Network egress restrictions reduce exfiltration and callback opportunities inside the isolated runtime; it could help someone trying to stop a test application from making arbitrary internet connections, but the problem is instead to allow a media converter to write only one output directory.
Question 457
To stop a test application from making arbitrary internet connections, which security control is most appropriate?
- Ephemeral sandbox lifecycle
- Outbound sandbox policy
- Sandbox escape patching
- Container runtime isolation
Explanation
Correct Answer
B:Network egress restrictions reduce exfiltration and callback opportunities inside the isolated runtime; it supplies the specific control needed to stop a test application from making arbitrary internet connections.
Incorrect Answers
A:Throwaway environments prevent long-term accumulation of attacker modifications and artifacts; applying it would serve delete risky downloaded-content changes after analysis completes without directly satisfying the goal to stop a test application from making arbitrary internet connections.
C:Isolation remains dependent on patched escape surfaces and correct boundary configuration; the technique works for situations involving mitigate a known host-kernel vulnerability reachable from guest code, rather than this need to stop a test application from making arbitrary internet connections.
D:Kernel isolation narrows process reach but shares the host kernel and needs defense in depth; its mechanism supports run untrusted services with limited namespaces and capabilities, while the requested control must be able to stop a test application from making arbitrary internet connections.
Question 458
To delete risky downloaded-content changes after analysis completes, what would a application security engineer implement or use?
- Outbound sandbox policy
- Ephemeral sandbox lifecycle
- Read-only application container
- Application-specific filesystem access
Explanation
Correct Answer
B:Throwaway environments prevent long-term accumulation of attacker modifications and artifacts; that is why it addresses the operational task to delete risky downloaded-content changes after analysis completes.
Incorrect Answers
A:Network egress restrictions reduce exfiltration and callback opportunities inside the isolated runtime; its operational purpose is to stop a test application from making arbitrary internet connections, not to achieve the specific requirement to delete risky downloaded-content changes after analysis completes.
C:Immutable root filesystems restrict persistent application-layer changes while writable mounts remain separate; it addresses the different need to prevent a workload from modifying its deployed executable tree, leaving the requested ability to delete risky downloaded-content changes after analysis completes unresolved.
D:Filesystem confinement limits the data a compromised conversion process can alter or read; the technique works for situations involving allow a media converter to write only one output directory, rather than this need to delete risky downloaded-content changes after analysis completes.
Question 459
An untrusted document previewer runs in a sandbox, but it can still invoke a privileged host service over a local interprocess channel. The security team wants to prevent unapproved messages from crossing that boundary while retaining sandbox execution. Which control best addresses the gap?
- Sandbox telemetry capture
- Read-only application container
- Container CPU usage quota
- Restrict sandbox-to-host IPC endpoints with a policy
Explanation
Correct Answer
D:An IPC boundary policy limits which broker interfaces and message types a sandboxed process may use. Removing unauthorized host-service access prevents privilege crossing while allowing approved preview functionality.
Incorrect Answers
A:Sandbox telemetry captures activity and may help investigators identify unexpected service calls. Observation does not by itself prevent an untrusted previewer from sending commands to a privileged host-side endpoint.
B:A read-only container restricts modifications to its designated filesystem layers. It does not automatically block an IPC socket or broker service that grants access across a process-trust boundary.
C:A CPU quota limits resource consumption and can help protect service availability. It does not specify which privileged interprocess endpoints an untrusted document preview process may contact.
Question 460
To mitigate a known host-kernel vulnerability reachable from guest code and to prevent a parsing test from consuming all available system memory, which TWO measures should the defender select? Choose TWO.
- Ephemeral sandbox lifecycle
- Application-specific filesystem access
- Sandbox telemetry capture
- Resource-limited sandbox
- Sandbox escape patching
Explanation
Correct Answers
D:CPU and memory quotas bound damage from runaway or malicious workloads; its contribution to the combined design is specifically to prevent a parsing test from consuming all available system memory.
E:Isolation remains dependent on patched escape surfaces and correct boundary configuration; its contribution to the combined design is specifically to mitigate a known host-kernel vulnerability reachable from guest code.
Incorrect Answers
A:Throwaway environments prevent long-term accumulation of attacker modifications and artifacts; that is useful when the task is to delete risky downloaded-content changes after analysis completes, not the stated requirement to mitigate a known host-kernel vulnerability reachable from guest code and to prevent a parsing test from consuming all available system memory.
B:Filesystem confinement limits the data a compromised conversion process can alter or read; a team would select it to allow a media converter to write only one output directory, which does not provide the particular result to mitigate a known host-kernel vulnerability reachable from guest code and to prevent a parsing test from consuming all available system memory.
C:Instrumented isolation produces investigation evidence without deliberately exposing end-user systems; its operational purpose is to observe file, process and network behavior of suspicious submissions, not to achieve the specific requirement to mitigate a known host-kernel vulnerability reachable from guest code and to prevent a parsing test from consuming all available system memory.