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

Question 470

To identify a vulnerable transitive dependency inside a deployed service, which method is designed for the task?

  1. Software composition analysis
  2. Patch authenticity verification
  3. Canary deployment
  4. Hotfix verification
  5. 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.

Question 471

To temporarily block exploit requests while source-code remediation is pending, what technique should the team use?

  1. Runtime virtual patching
  2. Hotfix verification
  3. Patch exception approval
  4. Software composition analysis

Explanation

Correct Answer

A:

WAF or inspection rules can reduce reachable exploit paths but do not repair underlying code; its relevant protective or investigative effect is to temporarily block exploit requests while source-code remediation is pending.

Incorrect Answers

B:

Reproduction testing and monitored behavior provide stronger assurance than installation status alone; that is useful when the task is to confirm the vulnerable code path is removed after an emergency patch, not the stated requirement to temporarily block exploit requests while source-code remediation is pending.

C:

Time-bound risk acceptance and mitigations manage exposure until a safe replacement is available; a team would select it to document why an incompatible application update is deferred under compensating controls, which does not provide the particular result to temporarily block exploit requests while source-code remediation is pending.

D:

Dependency graphs and version correlation reveal flaws not obvious from the top-level application name; its operational purpose is to identify a vulnerable transitive dependency inside a deployed service, not to achieve the specific requirement to temporarily block exploit requests while source-code remediation is pending.

Question 472

To confirm the vulnerable code path is removed after an emergency patch and to document why an incompatible application update is deferred under compensating controls, which TWO measures should the defender select? Choose TWO.

  1. Patch authenticity verification
  2. Software composition analysis
  3. Hotfix verification
  4. Runtime virtual patching
  5. Patch exception approval

Explanation

Correct Answers

C:

Reproduction testing and monitored behavior provide stronger assurance than installation status alone; its contribution to the combined design is specifically to confirm the vulnerable code path is removed after an emergency patch.

E:

Time-bound risk acceptance and mitigations manage exposure until a safe replacement is available; its contribution to the combined design is specifically to document why an incompatible application update is deferred under compensating controls.

Incorrect Answers

A:

Trusted signature and checksum checks protect the software delivery path against tampering; although relevant to reject an update archive not signed by the expected publisher, it does not by itself achieve the required task to confirm the vulnerable code path is removed after an emergency patch and to document why an incompatible application update is deferred under compensating controls.

B:

Dependency graphs and version correlation reveal flaws not obvious from the top-level application name; it could help someone trying to identify a vulnerable transitive dependency inside a deployed service, but the problem is instead to confirm the vulnerable code path is removed after an emergency patch and to document why an incompatible application update is deferred under compensating controls.

D:

WAF or inspection rules can reduce reachable exploit paths but do not repair underlying code; a team would select it to temporarily block exploit requests while source-code remediation is pending, which does not provide the particular result to confirm the vulnerable code path is removed after an emergency patch and to document why an incompatible application update is deferred under compensating controls.

Question 473

To document why an incompatible application update is deferred under compensating controls, which protective or investigative measure applies?

  1. Runtime virtual patching
  2. Hotfix verification
  3. Risk-based patch scheduling
  4. Patch exception approval

Explanation

Correct Answer

D:

Time-bound risk acceptance and mitigations manage exposure until a safe replacement is available; this choice fits the scenario because the team must document why an incompatible application update is deferred under compensating controls.

Incorrect Answers

A:

WAF or inspection rules can reduce reachable exploit paths but do not repair underlying code; the outcome it supports is to temporarily block exploit requests while source-code remediation is pending, whereas this scenario asks defenders to document why an incompatible application update is deferred under compensating controls.

B:

Reproduction testing and monitored behavior provide stronger assurance than installation status alone; although relevant to confirm the vulnerable code path is removed after an emergency patch, it does not by itself achieve the required task to document why an incompatible application update is deferred under compensating controls.

C:

Exposure and exploitation likelihood influence timing beyond an identical severity label. This can help to prioritize a remotely exploitable internet-facing app over a low-impact local bug, but it does not provide the particular mechanism required to document why an incompatible application update is deferred under compensating controls.

Question 474

To block suspicious query manipulation in incoming HTTP request parameters, what is the most direct option?

  1. WAF cross-site scripting rule
  2. WAF rate-based rule
  3. WAF SQL injection rule
  4. WAF path allowlist

Explanation

Correct Answer

C:

Application-layer inspection examines request syntax but prepared queries remain the primary code-level defense; this mechanism directly supports the requirement to block suspicious query manipulation in incoming HTTP request parameters.

Incorrect Answers

A:

Payload inspection catches recognizable injection attempts while contextual output encoding prevents execution; its mechanism supports flag malicious script markup in submitted web fields, while the requested control must be able to block suspicious query manipulation in incoming HTTP request parameters.

B:

Request-rate policies address volume but require thresholds that account for shared clients and proxies; the outcome it supports is to limit repeated requests from an abusive source to a login endpoint, whereas this scenario asks defenders to block suspicious query manipulation in incoming HTTP request parameters.

D:

Explicit path controls reduce unwanted endpoint exposure at the application gateway; it could help someone trying to permit only documented routes into a restricted management web application, but the problem is instead to block suspicious query manipulation in incoming HTTP request parameters.

Question 475

To flag malicious script markup in submitted web fields, what should defenders select?

  1. WAF rate-based rule
  2. WAF SQL injection rule
  3. WAF path allowlist
  4. WAF cross-site scripting rule
  5. WAF false-positive tuning
  6. WAF bot challenge

Explanation

Correct Answer

D:

Payload inspection catches recognizable injection attempts while contextual output encoding prevents execution; it supplies the specific control needed to flag malicious script markup in submitted web fields.

Incorrect Answers

A:

Request-rate policies address volume but require thresholds that account for shared clients and proxies; the technique works for situations involving limit repeated requests from an abusive source to a login endpoint, rather than this need to flag malicious script markup in submitted web fields.

B:

Application-layer inspection examines request syntax but prepared queries remain the primary code-level defense; its mechanism supports block suspicious query manipulation in incoming HTTP request parameters, while the requested control must be able to flag malicious script markup in submitted web fields.

C:

Explicit path controls reduce unwanted endpoint exposure at the application gateway; the outcome it supports is to permit only documented routes into a restricted management web application, whereas this scenario asks defenders to flag malicious script markup in submitted web fields.

E:

Rule exclusions or parameter scoping can preserve protection while handling known safe input patterns; it could help someone trying to stop a legitimate JSON API call being blocked by a broad rule, but the problem is instead to flag malicious script markup in submitted web fields.

F:

Challenges and reputation signals increase bot friction while not establishing user authorization; that is useful when the task is to differentiate automated credential attempts from normal user interactions, not the stated requirement to flag malicious script markup in submitted web fields.

Question 476

To limit repeated requests from an abusive source to a login endpoint, which mechanism best fits?

  1. Reverse-proxy header sanitization
  2. WAF rate-based rule
  3. WAF cross-site scripting rule
  4. WAF path allowlist

Explanation

Correct Answer

B:

Request-rate policies address volume but require thresholds that account for shared clients and proxies; that is why it addresses the operational task to limit repeated requests from an abusive source to a login endpoint.

Incorrect Answers

A:

A trusted proxy strips and regenerates sensitive headers before passing requests to application code; it addresses the different need to stop clients spoofing upstream identity or forwarding headers, leaving the requested ability to limit repeated requests from an abusive source to a login endpoint unresolved.

C:

Payload inspection catches recognizable injection attempts while contextual output encoding prevents execution; its mechanism supports flag malicious script markup in submitted web fields, while the requested control must be able to limit repeated requests from an abusive source to a login endpoint.

D:

Explicit path controls reduce unwanted endpoint exposure at the application gateway; the outcome it supports is to permit only documented routes into a restricted management web application, whereas this scenario asks defenders to limit repeated requests from an abusive source to a login endpoint.

Question 477

To differentiate automated credential attempts from normal user interactions, which measure best meets the requirement?

  1. WAF rate-based rule
  2. Reverse-proxy header sanitization
  3. WAF bot challenge
  4. WAF SQL injection rule

Explanation

Correct Answer

C:

Challenges and reputation signals increase bot friction while not establishing user authorization; its relevant protective or investigative effect is to differentiate automated credential attempts from normal user interactions.

Incorrect Answers

A:

Request-rate policies address volume but require thresholds that account for shared clients and proxies; applying it would serve limit repeated requests from an abusive source to a login endpoint without directly satisfying the goal to differentiate automated credential attempts from normal user interactions.

B:

A trusted proxy strips and regenerates sensitive headers before passing requests to application code; it addresses the different need to stop clients spoofing upstream identity or forwarding headers, leaving the requested ability to differentiate automated credential attempts from normal user interactions unresolved.

D:

Application-layer inspection examines request syntax but prepared queries remain the primary code-level defense; its mechanism supports block suspicious query manipulation in incoming HTTP request parameters, while the requested control must be able to differentiate automated credential attempts from normal user interactions.

Question 478

To permit only documented routes into a restricted management web application, what control should be selected?

  1. WAF rate-based rule
  2. WAF path allowlist
  3. Reverse-proxy header sanitization
  4. WAF TLS termination

Explanation

Correct Answer

B:

Explicit path controls reduce unwanted endpoint exposure at the application gateway; the requested outcome is precisely to permit only documented routes into a restricted management web application.

Incorrect Answers

A:

Request-rate policies address volume but require thresholds that account for shared clients and proxies; its operational purpose is to limit repeated requests from an abusive source to a login endpoint, not to achieve the specific requirement to permit only documented routes into a restricted management web application.

C:

A trusted proxy strips and regenerates sensitive headers before passing requests to application code; it addresses the different need to stop clients spoofing upstream identity or forwarding headers, leaving the requested ability to permit only documented routes into a restricted management web application unresolved.

D:

The gateway needs approved key or termination capability and must resecure its upstream connection appropriately; the technique works for situations involving inspect encrypted web requests at a designated application gateway, rather than this need to permit only documented routes into a restricted management web application.

Question 479

To stop a legitimate JSON API call being blocked by a broad rule, which security control is most appropriate?

  1. HTTP security headers
  2. API gateway authentication
  3. WAF bot challenge
  4. WAF false-positive tuning

Explanation

Correct Answer

D:

Rule exclusions or parameter scoping can preserve protection while handling known safe input patterns; this choice fits the scenario because the team must stop a legitimate JSON API call being blocked by a broad rule.

Incorrect Answers

A:

Security response headers affect browser enforcement and complement server-side authentication checks; a team would select it to instruct browsers to limit framing, content sourcing and transport downgrade, which does not provide the particular result to stop a legitimate JSON API call being blocked by a broad rule.

B:

Gateway verification can reject unauthenticated calls but fine-grained business authorization remains essential; its operational purpose is to require valid tokens before exposing business API operations, not to achieve the specific requirement to stop a legitimate JSON API call being blocked by a broad rule.

C:

Challenges and reputation signals increase bot friction while not establishing user authorization; applying it would serve differentiate automated credential attempts from normal user interactions without directly satisfying the goal to stop a legitimate JSON API call being blocked by a broad rule.

Question 480

To stop clients spoofing upstream identity or forwarding headers, what would a application security engineer implement or use?

  1. Reverse-proxy header sanitization
  2. WAF TLS termination
  3. HTTP security headers
  4. WAF false-positive tuning
  5. WAF managed rule updates

Explanation

Correct Answer

A:

A trusted proxy strips and regenerates sensitive headers before passing requests to application code; this mechanism directly supports the requirement to stop clients spoofing upstream identity or forwarding headers.

Incorrect Answers

B:

The gateway needs approved key or termination capability and must resecure its upstream connection appropriately; a team would select it to inspect encrypted web requests at a designated application gateway, which does not provide the particular result to stop clients spoofing upstream identity or forwarding headers.

C:

Security response headers affect browser enforcement and complement server-side authentication checks; its operational purpose is to instruct browsers to limit framing, content sourcing and transport downgrade, not to achieve the specific requirement to stop clients spoofing upstream identity or forwarding headers.

D:

Rule exclusions or parameter scoping can preserve protection while handling known safe input patterns; applying it would serve stop a legitimate JSON API call being blocked by a broad rule without directly satisfying the goal to stop clients spoofing upstream identity or forwarding headers.

E:

Rule maintenance reduces known-pattern gaps without providing a guarantee against application logic flaws; it addresses the different need to keep inspection signatures aligned with emerging web exploit patterns, leaving the requested ability to stop clients spoofing upstream identity or forwarding headers unresolved.

Certified Network Defender (312-38) Practice Tests