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.
Question 461
To prevent a parsing test from consuming all available system memory, what safeguard would be most applicable?
- Resource-limited sandbox
- Read-only application container
- Sandbox telemetry capture
- Sandbox escape patching
Explanation
Correct Answer
A:CPU and memory quotas bound damage from runaway or malicious workloads; this choice fits the scenario because the team must prevent a parsing test from consuming all available system memory.
Incorrect Answers
B:Immutable root filesystems restrict persistent application-layer changes while writable mounts remain separate; that is useful when the task is to prevent a workload from modifying its deployed executable tree, not the stated requirement to prevent a parsing test from consuming all available system memory.
C:Instrumented isolation produces investigation evidence without deliberately exposing end-user systems; a team would select it to observe file, process and network behavior of suspicious submissions, which does not provide the particular result to prevent a parsing test from consuming all available system memory.
D:Isolation remains dependent on patched escape surfaces and correct boundary configuration; its operational purpose is to mitigate a known host-kernel vulnerability reachable from guest code, not to achieve the specific requirement to prevent a parsing test from consuming all available system memory.
Question 462
To observe file, process and network behavior of suspicious submissions, what safeguard would be most applicable?
- Sandbox escape patching
- Sandbox telemetry capture
- Outbound sandbox policy
- Read-only application container
Explanation
Correct Answer
B:Instrumented isolation produces investigation evidence without deliberately exposing end-user systems; this mechanism directly supports the requirement to observe file, process and network behavior of suspicious submissions.
Incorrect Answers
A:Isolation remains dependent on patched escape surfaces and correct boundary configuration; although relevant to mitigate a known host-kernel vulnerability reachable from guest code, it does not by itself achieve the required task to observe file, process and network behavior of suspicious submissions.
C:Network egress restrictions reduce exfiltration and callback opportunities inside the isolated runtime; that is useful when the task is to stop a test application from making arbitrary internet connections, not the stated requirement to observe file, process and network behavior of suspicious submissions.
D:Immutable root filesystems restrict persistent application-layer changes while writable mounts remain separate; a team would select it to prevent a workload from modifying its deployed executable tree, which does not provide the particular result to observe file, process and network behavior of suspicious submissions.
Question 463
To find business applications still running a vulnerable release, what is the relevant defensive action?
- Application patch inventory
- Canary deployment
- Risk-based patch scheduling
- Test environment patch validation
Explanation
Correct Answer
A:Reliable version discovery links installed binaries to relevant advisories and fixes; it supplies the specific control needed to find business applications still running a vulnerable release.
Incorrect Answers
B:Staged release reveals regressions early and supports rollback before broad impact; although relevant to limit the first exposure of a new web-server build to a small user population, it does not by itself achieve the required task to find business applications still running a vulnerable release.
C:Exposure and exploitation likelihood influence timing beyond an identical severity label; it could help someone trying to prioritize a remotely exploitable internet-facing app over a low-impact local bug, but the problem is instead to find business applications still running a vulnerable release.
D:Preproduction testing checks business compatibility before fleet-wide installation; that is useful when the task is to verify a vendor update does not break critical authentication flows, not the stated requirement to find business applications still running a vulnerable release.
Question 464
To prioritize a remotely exploitable internet-facing app over a low-impact local bug, which option most directly provides the capability?
- Risk-based patch scheduling
- Application patch inventory
- Test environment patch validation
- Application rollback package
Explanation
Correct Answer
A:Exposure and exploitation likelihood influence timing beyond an identical severity label; that is why it addresses the operational task to prioritize a remotely exploitable internet-facing app over a low-impact local bug.
Incorrect Answers
B:Reliable version discovery links installed binaries to relevant advisories and fixes; the outcome it supports is to find business applications still running a vulnerable release, whereas this scenario asks defenders to prioritize a remotely exploitable internet-facing app over a low-impact local bug.
C:Preproduction testing checks business compatibility before fleet-wide installation; although relevant to verify a vendor update does not break critical authentication flows, it does not by itself achieve the required task to prioritize a remotely exploitable internet-facing app over a low-impact local bug.
D:Preserved deployable versions shorten recovery when a patch introduces a functional defect; it could help someone trying to restore the last approved executable after an incompatible update, but the problem is instead to prioritize a remotely exploitable internet-facing app over a low-impact local bug.
Question 465
To verify a vendor update does not break critical authentication flows, which control achieves the target outcome?
- Canary deployment
- End-of-support application removal
- Application patch inventory
- Risk-based patch scheduling
- Test environment patch validation
Explanation
Correct Answer
E:Preproduction testing checks business compatibility before fleet-wide installation; its relevant protective or investigative effect is to verify a vendor update does not break critical authentication flows.
Incorrect Answers
A:Staged release reveals regressions early and supports rollback before broad impact; the technique works for situations involving limit the first exposure of a new web-server build to a small user population, rather than this need to verify a vendor update does not break critical authentication flows.
B:Replacing unsupported binaries avoids accumulating unremediable vulnerabilities; its mechanism supports eliminate a client app for which security patches are no longer supplied, while the requested control must be able to verify a vendor update does not break critical authentication flows.
C:Reliable version discovery links installed binaries to relevant advisories and fixes; the outcome it supports is to find business applications still running a vulnerable release, whereas this scenario asks defenders to verify a vendor update does not break critical authentication flows.
D:Exposure and exploitation likelihood influence timing beyond an identical severity label; although relevant to prioritize a remotely exploitable internet-facing app over a low-impact local bug, it does not by itself achieve the required task to verify a vendor update does not break critical authentication flows.
Question 466
To limit the first exposure of a new web-server build to a small user population, which solution should be adopted?
- Application rollback package
- Risk-based patch scheduling
- Canary deployment
- Test environment patch validation
Explanation
Correct Answer
C:Staged release reveals regressions early and supports rollback before broad impact; the requested outcome is precisely to limit the first exposure of a new web-server build to a small user population.
Incorrect Answers
A:Preserved deployable versions shorten recovery when a patch introduces a functional defect; it addresses the different need to restore the last approved executable after an incompatible update, leaving the requested ability to limit the first exposure of a new web-server build to a small user population unresolved.
B:Exposure and exploitation likelihood influence timing beyond an identical severity label; the technique works for situations involving prioritize a remotely exploitable internet-facing app over a low-impact local bug, rather than this need to limit the first exposure of a new web-server build to a small user population.
D:Preproduction testing checks business compatibility before fleet-wide installation; the outcome it supports is to verify a vendor update does not break critical authentication flows, whereas this scenario asks defenders to limit the first exposure of a new web-server build to a small user population.
Question 467
To restore the last approved executable after an incompatible update, which of the available controls is suitable?
- Patch authenticity verification
- Test environment patch validation
- Application rollback package
- End-of-support application removal
Explanation
Correct Answer
C:Preserved deployable versions shorten recovery when a patch introduces a functional defect; this choice fits the scenario because the team must restore the last approved executable after an incompatible update.
Incorrect Answers
A:Trusted signature and checksum checks protect the software delivery path against tampering; applying it would serve reject an update archive not signed by the expected publisher without directly satisfying the goal to restore the last approved executable after an incompatible update.
B:Preproduction testing checks business compatibility before fleet-wide installation; it addresses the different need to verify a vendor update does not break critical authentication flows, leaving the requested ability to restore the last approved executable after an incompatible update unresolved.
D:Replacing unsupported binaries avoids accumulating unremediable vulnerabilities; its mechanism supports eliminate a client app for which security patches are no longer supplied, while the requested control must be able to restore the last approved executable after an incompatible update.
Question 468
To reject an update archive not signed by the expected publisher, which option is the direct technical match?
- Application rollback package
- Patch authenticity verification
- Test environment patch validation
- Software composition analysis
Explanation
Correct Answer
B:Trusted signature and checksum checks protect the software delivery path against tampering; this mechanism directly supports the requirement to reject an update archive not signed by the expected publisher.
Incorrect Answers
A:Preserved deployable versions shorten recovery when a patch introduces a functional defect; its operational purpose is to restore the last approved executable after an incompatible update, not to achieve the specific requirement to reject an update archive not signed by the expected publisher.
C:Preproduction testing checks business compatibility before fleet-wide installation; it addresses the different need to verify a vendor update does not break critical authentication flows, leaving the requested ability to reject an update archive not signed by the expected publisher unresolved.
D:Dependency graphs and version correlation reveal flaws not obvious from the top-level application name; the technique works for situations involving identify a vulnerable transitive dependency inside a deployed service, rather than this need to reject an update archive not signed by the expected publisher.
Question 469
To eliminate a client app for which security patches are no longer supplied, which approach should a application security engineer choose?
- Test environment patch validation
- Hotfix verification
- Application rollback package
- End-of-support application removal
Explanation
Correct Answer
D:Replacing unsupported binaries avoids accumulating unremediable vulnerabilities; it supplies the specific control needed to eliminate a client app for which security patches are no longer supplied.
Incorrect Answers
A:Preproduction testing checks business compatibility before fleet-wide installation; a team would select it to verify a vendor update does not break critical authentication flows, which does not provide the particular result to eliminate a client app for which security patches are no longer supplied.
B:Reproduction testing and monitored behavior provide stronger assurance than installation status alone; its operational purpose is to confirm the vulnerable code path is removed after an emergency patch, not to achieve the specific requirement to eliminate a client app for which security patches are no longer supplied.
C:Preserved deployable versions shorten recovery when a patch introduces a functional defect; applying it would serve restore the last approved executable after an incompatible update without directly satisfying the goal to eliminate a client app for which security patches are no longer supplied.
Question 470
To identify a vulnerable transitive dependency inside a deployed service, which method is designed for the task?
- Software composition analysis
- Patch authenticity verification
- Canary deployment
- Hotfix verification
- Patch exception approval
Explanation
Correct Answer
A:Dependency graphs and version correlation reveal flaws not obvious from the top-level application name; that is why it addresses the operational task to identify a vulnerable transitive dependency inside a deployed service.
Incorrect Answers
B:Trusted signature and checksum checks protect the software delivery path against tampering; a team would select it to reject an update archive not signed by the expected publisher, which does not provide the particular result to identify a vulnerable transitive dependency inside a deployed service.
C:Staged release reveals regressions early and supports rollback before broad impact; its operational purpose is to limit the first exposure of a new web-server build to a small user population, not to achieve the specific requirement to identify a vulnerable transitive dependency inside a deployed service.
D:Reproduction testing and monitored behavior provide stronger assurance than installation status alone; applying it would serve confirm the vulnerable code path is removed after an emergency patch without directly satisfying the goal to identify a vulnerable transitive dependency inside a deployed service.
E:Time-bound risk acceptance and mitigations manage exposure until a safe replacement is available; it addresses the different need to document why an incompatible application update is deferred under compensating controls, leaving the requested ability to identify a vulnerable transitive dependency inside a deployed service unresolved.