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

Question 780

To detect a branch firewall that suddenly stops sending any events, which method is designed for the task?

  1. Logging pipeline health alert
  2. Sensitive log redaction
  3. Log parsing normalization
  4. Alert severity calibration
  5. Security event correlation

Explanation

Correct Answer

A:

Ingestion-heartbeat monitoring distinguishes quiet systems from failed collection paths; this mechanism directly supports the requirement to detect a branch firewall that suddenly stops sending any events.

Incorrect Answers

B:

Field-level sanitization preserves useful events without accumulating additional high-value secrets; a team would select it to avoid storing session tokens or full personal records in diagnostic messages, which does not provide the particular result to detect a branch firewall that suddenly stops sending any events.

C:

Normalization aligns source, action, timestamp and identity attributes for consistent searching; its operational purpose is to map different firewall vendor fields into a common event schema, not to achieve the specific requirement to detect a branch firewall that suddenly stops sending any events.

D:

Tuned severity considers asset importance, confidence and observable impact instead of raw event counts; applying it would serve reduce priority inflation from frequent low-impact authentication failures without directly satisfying the goal to detect a branch firewall that suddenly stops sending any events.

E:

Correlating multiple log sources supplies context unavailable in isolated single-product alerts; it addresses the different need to link one identity's failed VPN logins to subsequent server access, leaving the requested ability to detect a branch firewall that suddenly stops sending any events unresolved.

Question 781

To avoid storing session tokens or full personal records in diagnostic messages, which method is designed for the task?

  1. Logging pipeline health alert
  2. Sensitive log redaction
  3. Security event correlation
  4. Log integrity signatures

Explanation

Correct Answer

B:

Field-level sanitization preserves useful events without accumulating additional high-value secrets; it supplies the specific control needed to avoid storing session tokens or full personal records in diagnostic messages.

Incorrect Answers

A:

Ingestion-heartbeat monitoring distinguishes quiet systems from failed collection paths; it could help someone trying to detect a branch firewall that suddenly stops sending any events, but the problem is instead to avoid storing session tokens or full personal records in diagnostic messages.

C:

Correlating multiple log sources supplies context unavailable in isolated single-product alerts; a team would select it to link one identity's failed VPN logins to subsequent server access, which does not provide the particular result to avoid storing session tokens or full personal records in diagnostic messages.

D:

Cryptographic verification establishes tamper evidence when keys and original digest records are protected; its operational purpose is to detect altered exported audit records through independently verifiable signatures, not to achieve the specific requirement to avoid storing session tokens or full personal records in diagnostic messages.

Question 782

To identify a successful Windows account sign-in and its logon type, what technique should the team use?

  1. Windows Security Event 4624
  2. Windows Security Event 4720
  3. Windows Security Event 4625
  4. Windows Security Event 4732

Explanation

Correct Answer

A:

Security audit fields differentiate interactive, network and service logons for investigation; that is why it addresses the operational task to identify a successful Windows account sign-in and its logon type.

Incorrect Answers

B:

Account-management auditing records identity creation that may precede persistence or privilege escalation; it could help someone trying to detect a newly created user account in an audited Windows environment, but the problem is instead to identify a successful Windows account sign-in and its logon type.

C:

Failure records support password-attack analysis with account, source and logon context; that is useful when the task is to examine rejected Windows authentication attempts with failure status details, not the stated requirement to identify a successful Windows account sign-in and its logon type.

D:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; a team would select it to find a principal added to a local or domain-local security group, which does not provide the particular result to identify a successful Windows account sign-in and its logon type.

Question 783

To examine rejected Windows authentication attempts with failure status details, which protective or investigative measure applies?

  1. Windows Security Event 4625
  2. Windows Security Event 4732
  3. Windows Security Event 4624
  4. Windows Security Event 4728

Explanation

Correct Answer

A:

Failure records support password-attack analysis with account, source and logon context; its relevant protective or investigative effect is to examine rejected Windows authentication attempts with failure status details.

Incorrect Answers

B:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; although relevant to find a principal added to a local or domain-local security group, it does not by itself achieve the required task to examine rejected Windows authentication attempts with failure status details.

C:

Security audit fields differentiate interactive, network and service logons for investigation; it could help someone trying to identify a successful Windows account sign-in and its logon type, but the problem is instead to examine rejected Windows authentication attempts with failure status details.

D:

Group-change events help catch unauthorized entitlement growth in Active Directory; that is useful when the task is to identify a member added to a privileged security-enabled global group, not the stated requirement to examine rejected Windows authentication attempts with failure status details.

Question 784

To detect a newly created user account in an audited Windows environment, what is the most direct option?

  1. Windows Security Event 4732
  2. Windows Security Event 4688
  3. Windows Security Event 4720
  4. Windows Security Event 4625

Explanation

Correct Answer

C:

Account-management auditing records identity creation that may precede persistence or privilege escalation; the requested outcome is precisely to detect a newly created user account in an audited Windows environment.

Incorrect Answers

A:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; its mechanism supports find a principal added to a local or domain-local security group, while the requested control must be able to detect a newly created user account in an audited Windows environment.

B:

Process creation audit data supports execution-chain reconstruction when appropriate policy is configured; the outcome it supports is to observe process launches and optional command-line arguments on Windows hosts, whereas this scenario asks defenders to detect a newly created user account in an audited Windows environment.

D:

Failure records support password-attack analysis with account, source and logon context; it could help someone trying to examine rejected Windows authentication attempts with failure status details, but the problem is instead to detect a newly created user account in an audited Windows environment.

Question 785

To identify a member added to a privileged security-enabled global group, what should defenders select?

  1. Windows Security Event 4688
  2. Windows Security Event 4732
  3. Windows Security Event 1102
  4. Windows Security Event 4728
  5. Windows Security Event 4625

Explanation

Correct Answer

D:

Group-change events help catch unauthorized entitlement growth in Active Directory; this choice fits the scenario because the team must identify a member added to a privileged security-enabled global group.

Incorrect Answers

A:

Process creation audit data supports execution-chain reconstruction when appropriate policy is configured; the technique works for situations involving observe process launches and optional command-line arguments on Windows hosts, rather than this need to identify a member added to a privileged security-enabled global group.

B:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; its mechanism supports find a principal added to a local or domain-local security group, while the requested control must be able to identify a member added to a privileged security-enabled global group.

C:

An audit-log-clear event can indicate evidence suppression, although administrative maintenance must be checked; the outcome it supports is to investigate deliberate clearing of the Windows Security event log, whereas this scenario asks defenders to identify a member added to a privileged security-enabled global group.

E:

Failure records support password-attack analysis with account, source and logon context; it could help someone trying to examine rejected Windows authentication attempts with failure status details, but the problem is instead to identify a member added to a privileged security-enabled global group.

Question 786

To find a principal added to a local or domain-local security group, which mechanism best fits?

  1. Windows Security Event 1102
  2. Windows Security Event 4768
  3. Windows Security Event 4728
  4. Windows Security Event 4732

Explanation

Correct Answer

D:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; this mechanism directly supports the requirement to find a principal added to a local or domain-local security group.

Incorrect Answers

A:

An audit-log-clear event can indicate evidence suppression, although administrative maintenance must be checked; it addresses the different need to investigate deliberate clearing of the Windows Security event log, leaving the requested ability to find a principal added to a local or domain-local security group unresolved.

B:

TGT request events support authentication trend analysis and credential-attack investigation; the technique works for situations involving track Kerberos ticket-granting ticket requests at domain controllers, rather than this need to find a principal added to a local or domain-local security group.

C:

Group-change events help catch unauthorized entitlement growth in Active Directory; its mechanism supports identify a member added to a privileged security-enabled global group, while the requested control must be able to find a principal added to a local or domain-local security group.

Question 787

To observe process launches and optional command-line arguments on Windows hosts, which measure best meets the requirement?

  1. Windows Security Event 4688
  2. Windows Security Event 4768
  3. Windows Security Event 4732
  4. Windows Event Forwarding subscriptions

Explanation

Correct Answer

A:

Process creation audit data supports execution-chain reconstruction when appropriate policy is configured; it supplies the specific control needed to observe process launches and optional command-line arguments on Windows hosts.

Incorrect Answers

B:

TGT request events support authentication trend analysis and credential-attack investigation; it addresses the different need to track Kerberos ticket-granting ticket requests at domain controllers, leaving the requested ability to observe process launches and optional command-line arguments on Windows hosts unresolved.

C:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; the technique works for situations involving find a principal added to a local or domain-local security group, rather than this need to observe process launches and optional command-line arguments on Windows hosts.

D:

WEF subscriptions aggregate client logs without relying entirely on a third-party host agent; its mechanism supports collect selected endpoint Windows events on a managed central collector, while the requested control must be able to observe process launches and optional command-line arguments on Windows hosts.

Question 788

To investigate deliberate clearing of the Windows Security event log, what control should be selected?

  1. Windows Security Event 4732
  2. Windows Security Event 1102
  3. Windows Security Event 4624
  4. Windows Security Event 4728

Explanation

Correct Answer

B:

An audit-log-clear event can indicate evidence suppression, although administrative maintenance must be checked; that is why it addresses the operational task to investigate deliberate clearing of the Windows Security event log.

Incorrect Answers

A:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; its operational purpose is to find a principal added to a local or domain-local security group, not to achieve the specific requirement to investigate deliberate clearing of the Windows Security event log.

C:

Security audit fields differentiate interactive, network and service logons for investigation. This can help to identify a successful Windows account sign-in and its logon type, but it does not provide the particular mechanism required to investigate deliberate clearing of the Windows Security event log.

D:

Group-change events help catch unauthorized entitlement growth in Active Directory; the technique works for situations involving identify a member added to a privileged security-enabled global group, rather than this need to investigate deliberate clearing of the Windows Security event log.

Question 789

To track Kerberos ticket-granting ticket requests at domain controllers, which security control is most appropriate?

  1. Windows Security Event 4776
  2. Windows Security Event 4688
  3. Windows Security Event 4768
  4. Windows Security Event 4732

Explanation

Correct Answer

C:

TGT request events support authentication trend analysis and credential-attack investigation; its relevant protective or investigative effect is to track Kerberos ticket-granting ticket requests at domain controllers.

Incorrect Answers

A:

NTLM authentication events provide clues distinct from Kerberos ticket activity; a team would select it to identify NTLM credential validation attempts against a Windows authority, which does not provide the particular result to track Kerberos ticket-granting ticket requests at domain controllers.

B:

Process creation audit data supports execution-chain reconstruction when appropriate policy is configured; its operational purpose is to observe process launches and optional command-line arguments on Windows hosts, not to achieve the specific requirement to track Kerberos ticket-granting ticket requests at domain controllers.

D:

Membership modification evidence reveals new access paths that group reviews might otherwise miss; it addresses the different need to find a principal added to a local or domain-local security group, leaving the requested ability to track Kerberos ticket-granting ticket requests at domain controllers unresolved.

Question 790

To examine requests for Kerberos service tickets to unusual service principals and to identify NTLM credential validation attempts against a Windows authority, which TWO measures should the defender select? Choose TWO.

  1. Windows Event Forwarding subscriptions
  2. Windows Security Event 4776
  3. Windows Security Event 4688
  4. Windows Security Event 4769
  5. Windows Security Event 1102

Explanation

Correct Answers

B:

NTLM authentication events provide clues distinct from Kerberos ticket activity; its contribution to the combined design is specifically to identify NTLM credential validation attempts against a Windows authority.

D:

Service-ticket records help investigate lateral access and suspicious ticket usage; its contribution to the combined design is specifically to examine requests for Kerberos service tickets to unusual service principals.

Incorrect Answers

A:

WEF subscriptions aggregate client logs without relying entirely on a third-party host agent; that is useful when the task is to collect selected endpoint Windows events on a managed central collector, not the stated requirement to examine requests for Kerberos service tickets to unusual service principals and to identify NTLM credential validation attempts against a Windows authority.

C:

Process creation audit data supports execution-chain reconstruction when appropriate policy is configured; its operational purpose is to observe process launches and optional command-line arguments on Windows hosts, not to achieve the specific requirement to examine requests for Kerberos service tickets to unusual service principals and to identify NTLM credential validation attempts against a Windows authority.

E:

An audit-log-clear event can indicate evidence suppression, although administrative maintenance must be checked; it addresses the different need to investigate deliberate clearing of the Windows Security event log, leaving the requested ability to examine requests for Kerberos service tickets to unusual service principals and to identify NTLM credential validation attempts against a Windows authority unresolved.

Certified Network Defender (312-38) Practice Tests