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

Question 490

To prevent developers from routinely reading production authentication secrets, which option is the direct technical match?

  1. Secure configuration externalization
  2. Application log access controls
  3. Dependency SBOM update
  4. SAST integration
  5. Security regression tests

Explanation

Correct Answer

B:

Least-privilege access to logs reduces secondary data exposure from diagnostic systems; the requested outcome is precisely to prevent developers from routinely reading production authentication secrets.

Incorrect Answers

A:

Secret managers and deployment injection separate environment credentials from application artifacts; that is useful when the task is to avoid embedding database passwords in a compiled executable, not the stated requirement to prevent developers from routinely reading production authentication secrets.

C:

Current component manifests enable affected-version lookup and faster exposure decisions; its operational purpose is to identify new libraries introduced by a supplier's application revision, not to achieve the specific requirement to prevent developers from routinely reading production authentication secrets.

D:

Static analysis examines code structure and dependencies without needing live HTTP traffic; applying it would serve find insecure source-code flows before an application is deployed without directly satisfying the goal to prevent developers from routinely reading production authentication secrets.

E:

Automated negative tests verify access restrictions after each relevant code change; it addresses the different need to ensure a previously repaired authorization bypass does not reappear, leaving the requested ability to prevent developers from routinely reading production authentication secrets unresolved.

Question 491

To avoid embedding database passwords in a compiled executable, which approach should a application security engineer choose?

  1. Secrets scanning
  2. Application health monitoring
  3. Dependency SBOM update
  4. Secure configuration externalization

Explanation

Correct Answer

D:

Secret managers and deployment injection separate environment credentials from application artifacts; this choice fits the scenario because the team must avoid embedding database passwords in a compiled executable.

Incorrect Answers

A:

Precommit or pipeline scanning identifies high-risk credential strings before builds distribute them; it could help someone trying to stop private API keys being committed into a source repository, but the problem is instead to avoid embedding database passwords in a compiled executable.

B:

Runtime telemetry links unusual failures to request context but needs correlation to establish malicious intent; that is useful when the task is to detect a crash loop caused by an attempted malicious request sequence, not the stated requirement to avoid embedding database passwords in a compiled executable.

C:

Current component manifests enable affected-version lookup and faster exposure decisions; a team would select it to identify new libraries introduced by a supplier's application revision, which does not provide the particular result to avoid embedding database passwords in a compiled executable.

Question 492

To detect a crash loop caused by an attempted malicious request sequence, which method is designed for the task?

  1. Application log access controls
  2. Application health monitoring
  3. Secure release signoff
  4. API request schema validation

Explanation

Correct Answer

B:

Runtime telemetry links unusual failures to request context but needs correlation to establish malicious intent; this mechanism directly supports the requirement to detect a crash loop caused by an attempted malicious request sequence.

Incorrect Answers

A:

Least-privilege access to logs reduces secondary data exposure from diagnostic systems; although relevant to prevent developers from routinely reading production authentication secrets, it does not by itself achieve the required task to detect a crash loop caused by an attempted malicious request sequence.

C:

Release gates connect risk findings and change evidence to deployability decisions; that is useful when the task is to require authorized security and operations approval for a production build, not the stated requirement to detect a crash loop caused by an attempted malicious request sequence.

D:

Strict input contracts reduce parsing ambiguity and malformed-operation exposure; a team would select it to reject unexpected data types before a backend processes untrusted messages, which does not provide the particular result to detect a crash loop caused by an attempted malicious request sequence.

Question 493

To reject unexpected data types before a backend processes untrusted messages, what technique should the team use?

  1. Secure release signoff
  2. Secure configuration externalization
  3. Application health monitoring
  4. API request schema validation

Explanation

Correct Answer

D:

Strict input contracts reduce parsing ambiguity and malformed-operation exposure; it supplies the specific control needed to reject unexpected data types before a backend processes untrusted messages.

Incorrect Answers

A:

Release gates connect risk findings and change evidence to deployability decisions; the outcome it supports is to require authorized security and operations approval for a production build, whereas this scenario asks defenders to reject unexpected data types before a backend processes untrusted messages.

B:

Secret managers and deployment injection separate environment credentials from application artifacts; although relevant to avoid embedding database passwords in a compiled executable, it does not by itself achieve the required task to reject unexpected data types before a backend processes untrusted messages.

C:

Runtime telemetry links unusual failures to request context but needs correlation to establish malicious intent; it could help someone trying to detect a crash loop caused by an attempted malicious request sequence, but the problem is instead to reject unexpected data types before a backend processes untrusted messages.

Question 494

To require authorized security and operations approval for a production build, which protective or investigative measure applies?

  1. API request schema validation
  2. Penetration-test retest
  3. Application log access controls
  4. Dependency SBOM update
  5. Application health monitoring
  6. Secure release signoff

Explanation

Correct Answer

F:

Release gates connect risk findings and change evidence to deployability decisions; that is why it addresses the operational task to require authorized security and operations approval for a production build.

Incorrect Answers

A:

Strict input contracts reduce parsing ambiguity and malformed-operation exposure; its mechanism supports reject unexpected data types before a backend processes untrusted messages, while the requested control must be able to require authorized security and operations approval for a production build.

B:

Targeted verification checks the exact exploitation path rather than closing the ticket on assertion alone; the outcome it supports is to confirm a reported application weakness is no longer exploitable after repair, whereas this scenario asks defenders to require authorized security and operations approval for a production build.

C:

Least-privilege access to logs reduces secondary data exposure from diagnostic systems; although relevant to prevent developers from routinely reading production authentication secrets, it does not by itself achieve the required task to require authorized security and operations approval for a production build.

D:

Current component manifests enable affected-version lookup and faster exposure decisions; it could help someone trying to identify new libraries introduced by a supplier's application revision, but the problem is instead to require authorized security and operations approval for a production build.

E:

Runtime telemetry links unusual failures to request context but needs correlation to establish malicious intent; that is useful when the task is to detect a crash loop caused by an attempted malicious request sequence, not the stated requirement to require authorized security and operations approval for a production build.

Question 495

To confirm a reported application weakness is no longer exploitable after repair, which mechanism best fits?

  1. API request schema validation
  2. Secure configuration externalization
  3. Secure release signoff
  4. Application health monitoring
  5. Penetration-test retest

Explanation

Correct Answer

E:

Targeted verification checks the exact exploitation path rather than closing the ticket on assertion alone; its relevant protective or investigative effect is to confirm a reported application weakness is no longer exploitable after repair.

Incorrect Answers

A:

Strict input contracts reduce parsing ambiguity and malformed-operation exposure; the technique works for situations involving reject unexpected data types before a backend processes untrusted messages, rather than this need to confirm a reported application weakness is no longer exploitable after repair.

B:

Secret managers and deployment injection separate environment credentials from application artifacts; its mechanism supports avoid embedding database passwords in a compiled executable, while the requested control must be able to confirm a reported application weakness is no longer exploitable after repair.

C:

Release gates connect risk findings and change evidence to deployability decisions; the outcome it supports is to require authorized security and operations approval for a production build, whereas this scenario asks defenders to confirm a reported application weakness is no longer exploitable after repair.

D:

Runtime telemetry links unusual failures to request context but needs correlation to establish malicious intent; although relevant to detect a crash loop caused by an attempted malicious request sequence, it does not by itself achieve the required task to confirm a reported application weakness is no longer exploitable after repair.

Question 496

To mark customer records as confidential across storage and collaboration tools, which measure best meets the requirement?

  1. Data owner authorization
  2. Data minimization
  3. Data classification labels
  4. Need-to-know access

Explanation

Correct Answer

C:

Consistent labels guide retention, sharing and encryption policies according to information sensitivity; the requested outcome is precisely to mark customer records as confidential across storage and collaboration tools.

Incorrect Answers

A:

Ownership decisions align permissions with legitimate purpose rather than the storage administrator's convenience; it addresses the different need to require business approval before a new team accesses financial datasets, leaving the requested ability to mark customer records as confidential across storage and collaboration tools unresolved.

B:

Reducing unnecessary personal data lowers breach consequences and retention obligations; the technique works for situations involving collect only required customer identifiers in a network monitoring workflow, rather than this need to mark customer records as confidential across storage and collaboration tools.

D:

Purpose-specific permission limits restrict data access even among authenticated employees; the outcome it supports is to prevent broad staff visibility into an investigation case repository, whereas this scenario asks defenders to mark customer records as confidential across storage and collaboration tools.

Question 497

To require business approval before a new team accesses financial datasets, what control should be selected?

  1. Data owner authorization
  2. Privacy by design
  3. Need-to-know access
  4. Data lineage mapping

Explanation

Correct Answer

A:

Ownership decisions align permissions with legitimate purpose rather than the storage administrator's convenience; this choice fits the scenario because the team must require business approval before a new team accesses financial datasets.

Incorrect Answers

B:

Early purpose, access and retention decisions reduce costly retrofit risks; it addresses the different need to integrate privacy protections before a new telemetry collection feature launches, leaving the requested ability to require business approval before a new team accesses financial datasets unresolved.

C:

Purpose-specific permission limits restrict data access even among authenticated employees; the technique works for situations involving prevent broad staff visibility into an investigation case repository, rather than this need to require business approval before a new team accesses financial datasets.

D:

Lineage records show propagation so controls apply beyond the initial database; its mechanism supports identify downstream reports that reuse a sensitive source table, while the requested control must be able to require business approval before a new team accesses financial datasets.

Question 498

To prevent broad staff visibility into an investigation case repository, which security control is most appropriate?

  1. Data classification labels
  2. Data owner authorization
  3. Privacy by design
  4. Need-to-know access

Explanation

Correct Answer

D:

Purpose-specific permission limits restrict data access even among authenticated employees; this mechanism directly supports the requirement to prevent broad staff visibility into an investigation case repository.

Incorrect Answers

A:

Consistent labels guide retention, sharing and encryption policies according to information sensitivity; its operational purpose is to mark customer records as confidential across storage and collaboration tools, not to achieve the specific requirement to prevent broad staff visibility into an investigation case repository.

B:

Ownership decisions align permissions with legitimate purpose rather than the storage administrator's convenience; applying it would serve require business approval before a new team accesses financial datasets without directly satisfying the goal to prevent broad staff visibility into an investigation case repository.

C:

Early purpose, access and retention decisions reduce costly retrofit risks; it addresses the different need to integrate privacy protections before a new telemetry collection feature launches, leaving the requested ability to prevent broad staff visibility into an investigation case repository unresolved.

Question 499

To collect only required customer identifiers in a network monitoring workflow, what would a data protection engineer implement or use?

  1. Data residency assessment
  2. Data minimization
  3. Data access recertification
  4. Privacy by design

Explanation

Correct Answer

B:

Reducing unnecessary personal data lowers breach consequences and retention obligations; it supplies the specific control needed to collect only required customer identifiers in a network monitoring workflow.

Incorrect Answers

A:

Residency review accounts for primary copies, backups and supplier processing regions; a team would select it to determine where regulated records physically reside and replicate, which does not provide the particular result to collect only required customer identifiers in a network monitoring workflow.

C:

Periodic authorization review identifies entitlements no longer justified by current duties; applying it would serve remove stale read grants from a shared analytics platform without directly satisfying the goal to collect only required customer identifiers in a network monitoring workflow.

D:

Early purpose, access and retention decisions reduce costly retrofit risks; it addresses the different need to integrate privacy protections before a new telemetry collection feature launches, leaving the requested ability to collect only required customer identifiers in a network monitoring workflow unresolved.

Question 500

To identify downstream reports that reuse a sensitive source table, which practice addresses that objective?

  1. Data access recertification
  2. Data lineage mapping
  3. Data minimization
  4. Data handling standard
  5. Need-to-know access

Explanation

Correct Answer

B:

Lineage records show propagation so controls apply beyond the initial database; that is why it addresses the operational task to identify downstream reports that reuse a sensitive source table.

Incorrect Answers

A:

Periodic authorization review identifies entitlements no longer justified by current duties; that is useful when the task is to remove stale read grants from a shared analytics platform, not the stated requirement to identify downstream reports that reuse a sensitive source table.

C:

Reducing unnecessary personal data lowers breach consequences and retention obligations; its operational purpose is to collect only required customer identifiers in a network monitoring workflow, not to achieve the specific requirement to identify downstream reports that reuse a sensitive source table.

D:

Handling rules translate classification levels into concrete permitted operations; applying it would serve define how internal and public datasets may be transferred or printed without directly satisfying the goal to identify downstream reports that reuse a sensitive source table.

E:

Purpose-specific permission limits restrict data access even among authenticated employees; it addresses the different need to prevent broad staff visibility into an investigation case repository, leaving the requested ability to identify downstream reports that reuse a sensitive source table unresolved.

Certified Network Defender (312-38) Practice Tests