ECCouncil 312-38 (Certified Network Defender) Practice Test 5

Question 40

To verify that deployable artifacts originated from an approved build workflow, which mechanism best fits?

  1. Cloud access key rotation
  2. Software bill of materials
  3. Cloud metadata isolation
  4. Dependency pinning
  5. Signed build provenance

Explanation

Correct Answer

E:

Cryptographically verifiable attestations link outputs to a known builder and input revision; the requested outcome is precisely to verify that deployable artifacts originated from an approved build workflow.

Incorrect Answers

A:

Revocation and replacement cut off further use of the exposed secret; removal of the public copy alone is insufficient; that is useful when the task is to replace a credential discovered in a public repository, not the stated requirement to verify that deployable artifacts originated from an approved build workflow.

B:

A component inventory enables targeted exposure analysis instead of guessing where a library was bundled; a team would select it to identify which deployed applications contain a vulnerable dependency, which does not provide the particular result to verify that deployable artifacts originated from an approved build workflow.

C:

Restricting metadata paths and using hardened token flows reduces credential theft from vulnerable workloads; its operational purpose is to limit server-side request forgery from reaching instance identity tokens, not to achieve the specific requirement to verify that deployable artifacts originated from an approved build workflow.

D:

Version and integrity locks keep resolution stable until maintainers deliberately approve an update; applying it would serve prevent an unexpected upstream package version entering a reproducible build without directly satisfying the goal to verify that deployable artifacts originated from an approved build workflow.

Question 41

To identify which deployed applications contain a vulnerable dependency, which measure best meets the requirement?

  1. Dependency pinning
  2. Signed build provenance
  3. Cloud metadata isolation
  4. Software bill of materials

Explanation

Correct Answer

D:

A component inventory enables targeted exposure analysis instead of guessing where a library was bundled; this choice fits the scenario because the team must identify which deployed applications contain a vulnerable dependency.

Incorrect Answers

A:

Version and integrity locks keep resolution stable until maintainers deliberately approve an update; it could help someone trying to prevent an unexpected upstream package version entering a reproducible build, but the problem is instead to identify which deployed applications contain a vulnerable dependency.

B:

Cryptographically verifiable attestations link outputs to a known builder and input revision; that is useful when the task is to verify that deployable artifacts originated from an approved build workflow, not the stated requirement to identify which deployed applications contain a vulnerable dependency.

C:

Restricting metadata paths and using hardened token flows reduces credential theft from vulnerable workloads; a team would select it to limit server-side request forgery from reaching instance identity tokens, which does not provide the particular result to identify which deployed applications contain a vulnerable dependency.

Question 42

To prevent an unexpected upstream package version entering a reproducible build, what control should be selected?

  1. Cloud metadata isolation
  2. Dependency pinning
  3. Signed build provenance
  4. Cloud access key rotation

Explanation

Correct Answer

B:

Version and integrity locks keep resolution stable until maintainers deliberately approve an update; this mechanism directly supports the requirement to prevent an unexpected upstream package version entering a reproducible build.

Incorrect Answers

A:

Restricting metadata paths and using hardened token flows reduces credential theft from vulnerable workloads; although relevant to limit server-side request forgery from reaching instance identity tokens, it does not by itself achieve the required task to prevent an unexpected upstream package version entering a reproducible build.

C:

Cryptographically verifiable attestations link outputs to a known builder and input revision; that is useful when the task is to verify that deployable artifacts originated from an approved build workflow, not the stated requirement to prevent an unexpected upstream package version entering a reproducible build.

D:

Revocation and replacement cut off further use of the exposed secret; removal of the public copy alone is insufficient; a team would select it to replace a credential discovered in a public repository, which does not provide the particular result to prevent an unexpected upstream package version entering a reproducible build.

Question 43

To reject a binary whose publisher signature does not validate, which security control is most appropriate?

  1. Third-party access review
  2. Dependency pinning
  3. Code-signature verification
  4. Software bill of materials

Explanation

Correct Answer

C:

Signature validation tests code origin and tamper evidence, assuming the signing key and trust chain remain trustworthy; it supplies the specific control needed to reject a binary whose publisher signature does not validate.

Incorrect Answers

A:

Time-bounded least-privilege accounts limit supplier paths after legitimate support activity ends; the outcome it supports is to reduce persistent vendor access beyond an agreed maintenance window, whereas this scenario asks defenders to reject a binary whose publisher signature does not validate.

B:

Version and integrity locks keep resolution stable until maintainers deliberately approve an update; although relevant to prevent an unexpected upstream package version entering a reproducible build, it does not by itself achieve the required task to reject a binary whose publisher signature does not validate.

D:

A component inventory enables targeted exposure analysis instead of guessing where a library was bundled; that is useful when the task is to identify which deployed applications contain a vulnerable dependency, not the stated requirement to reject a binary whose publisher signature does not validate.

Question 44

To prevent an unexpected upstream package version entering a reproducible build, to reject a binary whose publisher signature does not validate, and to reduce persistent vendor access beyond an agreed maintenance window, which THREE measures should the team select? Choose THREE.

  1. CI/CD protected branches
  2. Third-party access review
  3. Dependency pinning
  4. Software bill of materials
  5. Signed build provenance
  6. Code-signature verification

Explanation

Correct Answers

B:

Time-bounded least-privilege accounts limit supplier paths after legitimate support activity ends; it satisfies the distinct requirement to reduce persistent vendor access beyond an agreed maintenance window within the multi-control task.

C:

Version and integrity locks keep resolution stable until maintainers deliberately approve an update; it satisfies the distinct requirement to prevent an unexpected upstream package version entering a reproducible build within the multi-control task.

F:

Signature validation tests code origin and tamper evidence, assuming the signing key and trust chain remain trustworthy; it satisfies the distinct requirement to reject a binary whose publisher signature does not validate within the multi-control task.

Incorrect Answers

A:

Mandatory review and protected refs constrain pipeline modifications that could insert malicious build steps; its mechanism supports prevent unreviewed changes to production build definitions, while the requested control must be able to prevent an unexpected upstream package version entering a reproducible build, to reject a binary whose publisher signature does not validate, and to reduce persistent vendor access beyond an agreed maintenance window.

D:

A component inventory enables targeted exposure analysis instead of guessing where a library was bundled; it could help someone trying to identify which deployed applications contain a vulnerable dependency, but the problem is instead to prevent an unexpected upstream package version entering a reproducible build, to reject a binary whose publisher signature does not validate, and to reduce persistent vendor access beyond an agreed maintenance window.

E:

Cryptographically verifiable attestations link outputs to a known builder and input revision; that is useful when the task is to verify that deployable artifacts originated from an approved build workflow, not the stated requirement to prevent an unexpected upstream package version entering a reproducible build, to reject a binary whose publisher signature does not validate, and to reduce persistent vendor access beyond an agreed maintenance window.

Question 45

To avoid a single firewall failure exposing every protected asset, what would a network defender implement or use?

  1. MITRE ATT&CK mapping
  2. Threat modeling
  3. Kill-chain disruption
  4. Zero-trust verification
  5. Defense in depth

Explanation

Correct Answer

E:

Overlapping controls at identity, endpoint, network and data layers reduce dependence on one prevention mechanism; its relevant protective or investigative effect is to avoid a single firewall failure exposing every protected asset.

Incorrect Answers

A:

Behavior mapping connects telemetry to testable detection opportunities rather than relying only on malware names; the technique works for situations involving classify observed adversary behavior into recognized tactics and techniques, rather than this need to avoid a single firewall failure exposing every protected asset.

B:

Structured analysis of assets, trust boundaries and attacker goals guides controls during design; its mechanism supports identify likely attack paths before a new service is deployed, while the requested control must be able to avoid a single firewall failure exposing every protected asset.

C:

Breaking an earlier attack phase can prevent later stages even if other activity remains undetected; the outcome it supports is to choose a defensive checkpoint before payload execution or objective completion, whereas this scenario asks defenders to avoid a single firewall failure exposing every protected asset.

D:

Continuous authorization avoids treating mere presence on a private subnet as proof of trust; although relevant to require each resource request to be evaluated against identity and context, it does not by itself achieve the required task to avoid a single firewall failure exposing every protected asset.

Question 46

To require each resource request to be evaluated against identity and context, which practice addresses that objective?

  1. Threat modeling
  2. Zero-trust verification
  3. Attack surface reduction
  4. Defense in depth

Explanation

Correct Answer

B:

Continuous authorization avoids treating mere presence on a private subnet as proof of trust; the requested outcome is precisely to require each resource request to be evaluated against identity and context.

Incorrect Answers

A:

Structured analysis of assets, trust boundaries and attacker goals guides controls during design; it addresses the different need to identify likely attack paths before a new service is deployed, leaving the requested ability to require each resource request to be evaluated against identity and context unresolved.

C:

Shrinking reachable and executable components leaves fewer opportunities for initial access and escalation; its mechanism supports remove unnecessary exposed services and privileged entry points, while the requested control must be able to require each resource request to be evaluated against identity and context.

D:

Overlapping controls at identity, endpoint, network and data layers reduce dependence on one prevention mechanism; the outcome it supports is to avoid a single firewall failure exposing every protected asset, whereas this scenario asks defenders to require each resource request to be evaluated against identity and context.

Question 47

To classify observed adversary behavior into recognized tactics and techniques, which tool, policy, or technique is appropriate?

  1. Kill-chain disruption
  2. Zero-trust verification
  3. Threat modeling
  4. MITRE ATT&CK mapping

Explanation

Correct Answer

D:

Behavior mapping connects telemetry to testable detection opportunities rather than relying only on malware names; this choice fits the scenario because the team must classify observed adversary behavior into recognized tactics and techniques.

Incorrect Answers

A:

Breaking an earlier attack phase can prevent later stages even if other activity remains undetected; applying it would serve choose a defensive checkpoint before payload execution or objective completion without directly satisfying the goal to classify observed adversary behavior into recognized tactics and techniques.

B:

Continuous authorization avoids treating mere presence on a private subnet as proof of trust; it addresses the different need to require each resource request to be evaluated against identity and context, leaving the requested ability to classify observed adversary behavior into recognized tactics and techniques unresolved.

C:

Structured analysis of assets, trust boundaries and attacker goals guides controls during design; the technique works for situations involving identify likely attack paths before a new service is deployed, rather than this need to classify observed adversary behavior into recognized tactics and techniques.

Question 48

To identify likely attack paths before a new service is deployed, what safeguard would be most applicable?

  1. Threat modeling
  2. MITRE ATT&CK mapping
  3. Compensating controls
  4. Defense in depth

Explanation

Correct Answer

A:

Structured analysis of assets, trust boundaries and attacker goals guides controls during design; this mechanism directly supports the requirement to identify likely attack paths before a new service is deployed.

Incorrect Answers

B:

Behavior mapping connects telemetry to testable detection opportunities rather than relying only on malware names; applying it would serve classify observed adversary behavior into recognized tactics and techniques without directly satisfying the goal to identify likely attack paths before a new service is deployed.

C:

Temporary segmentation, monitoring or access limits lower exposure until a durable fix is available; it addresses the different need to treat a vulnerability when immediate patching is operationally impossible, leaving the requested ability to identify likely attack paths before a new service is deployed unresolved.

D:

Overlapping controls at identity, endpoint, network and data layers reduce dependence on one prevention mechanism; the technique works for situations involving avoid a single firewall failure exposing every protected asset, rather than this need to identify likely attack paths before a new service is deployed.

Question 49

To choose a defensive checkpoint before payload execution or objective completion, what is the relevant defensive action?

  1. Kill-chain disruption
  2. Purple-team exercises
  3. Threat modeling
  4. MITRE ATT&CK mapping

Explanation

Correct Answer

A:

Breaking an earlier attack phase can prevent later stages even if other activity remains undetected; it supplies the specific control needed to choose a defensive checkpoint before payload execution or objective completion.

Incorrect Answers

B:

Cooperative simulation validates whether observable behavior produces useful alerts and timely investigation; its operational purpose is to improve detections by jointly testing attacker emulation and defender response, not to achieve the specific requirement to choose a defensive checkpoint before payload execution or objective completion.

C:

Structured analysis of assets, trust boundaries and attacker goals guides controls during design; applying it would serve identify likely attack paths before a new service is deployed without directly satisfying the goal to choose a defensive checkpoint before payload execution or objective completion.

D:

Behavior mapping connects telemetry to testable detection opportunities rather than relying only on malware names; it addresses the different need to classify observed adversary behavior into recognized tactics and techniques, leaving the requested ability to choose a defensive checkpoint before payload execution or objective completion unresolved.

Question 50

To remove unnecessary exposed services and privileged entry points, which option most directly provides the capability?

  1. Kill-chain disruption
  2. Compensating controls
  3. Zero-trust verification
  4. Attack surface reduction
  5. Threat modeling

Explanation

Correct Answer

D:

Shrinking reachable and executable components leaves fewer opportunities for initial access and escalation; that is why it addresses the operational task to remove unnecessary exposed services and privileged entry points.

Incorrect Answers

A:

Breaking an earlier attack phase can prevent later stages even if other activity remains undetected; that is useful when the task is to choose a defensive checkpoint before payload execution or objective completion, not the stated requirement to remove unnecessary exposed services and privileged entry points.

B:

Temporary segmentation, monitoring or access limits lower exposure until a durable fix is available; a team would select it to treat a vulnerability when immediate patching is operationally impossible, which does not provide the particular result to remove unnecessary exposed services and privileged entry points.

C:

Continuous authorization avoids treating mere presence on a private subnet as proof of trust; its operational purpose is to require each resource request to be evaluated against identity and context, not to achieve the specific requirement to remove unnecessary exposed services and privileged entry points.

E:

Structured analysis of assets, trust boundaries and attacker goals guides controls during design; it addresses the different need to identify likely attack paths before a new service is deployed, leaving the requested ability to remove unnecessary exposed services and privileged entry points unresolved.

Certified Network Defender (312-38) Practice Tests