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

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.

Question 791

To identify NTLM credential validation attempts against a Windows authority, which practice addresses that objective?

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

Explanation

Correct Answer

C:

NTLM authentication events provide clues distinct from Kerberos ticket activity; this choice fits the scenario because the team must identify NTLM credential validation attempts against a Windows authority.

Incorrect Answers

A:

Service-ticket records help investigate lateral access and suspicious ticket usage; it could help someone trying to examine requests for Kerberos service tickets to unusual service principals, but the problem is instead to identify NTLM credential validation attempts against a Windows authority.

B:

An audit-log-clear event can indicate evidence suppression, although administrative maintenance must be checked; that is useful when the task is to investigate deliberate clearing of the Windows Security event log, not the stated requirement to identify NTLM credential validation attempts against a Windows authority.

D:

WEF subscriptions aggregate client logs without relying entirely on a third-party host agent; its operational purpose is to collect selected endpoint Windows events on a managed central collector, not to achieve the specific requirement to identify NTLM credential validation attempts against a Windows authority.

Question 792

Windows Event Forwarding is configured, but events from one expected workstation stopped arriving. On the collector, which command most directly shows whether that source is connected to the subscription at runtime?

  1. wecutil gr <subscriptionID>
  2. Review Windows Security Event 4776
  3. Review Windows Security Event 4688
  4. wecutil gs <subscriptionID>

Explanation

Correct Answer

A:

The wecutil gr command obtains subscription runtime status and source state on the collector. It helps confirm whether the expected forwarder is connected to that subscription.

Incorrect Answers

B:

Event 4776 records NTLM credential-validation activity in an appropriately audited Windows environment. It is not the collector runtime-status query for event forwarding subscriptions.

C:

Event 4688 can document new process creation when auditing is configured. It does not report whether a particular WEF event source remains connected to its collector.

D:

The wecutil gs command shows subscription configuration information rather than the runtime connectivity view of individual sources provided by wecutil gr.

Question 793

To investigate failed SSH sign-ins on distributions using that authentication log, which tool, policy, or technique is appropriate?

  1. Journald unit filter
  2. Linux secure log review
  3. Linux auth.log review
  4. Cron log analysis

Explanation

Correct Answer

C:

sshd authentication messages record accounts, sources and results when the chosen logging stack writes them there; it supplies the specific control needed to investigate failed SSH sign-ins on distributions using that authentication log.

Incorrect Answers

A:

Journal queries filter by unit identity and boot context for focused troubleshooting; the outcome it supports is to inspect errors emitted by one systemd-managed application service, whereas this scenario asks defenders to investigate failed SSH sign-ins on distributions using that authentication log.

B:

Platform logging conventions vary, so operators must check the actual destination and service configuration; although relevant to find repeated sudo or login events on a distribution that uses /var/log/secure, it does not by itself achieve the required task to investigate failed SSH sign-ins on distributions using that authentication log.

D:

Scheduler records expose task execution times and account context for persistence review; that is useful when the task is to find an unexpected periodic command running under a privileged identity, not the stated requirement to investigate failed SSH sign-ins on distributions using that authentication log.

Question 794

To find repeated sudo or login events on a distribution that uses /var/log/secure, what safeguard would be most applicable?

  1. Auditd syscall log
  2. Linux auth.log review
  3. Linux secure log review
  4. Sudo event log

Explanation

Correct Answer

C:

Platform logging conventions vary, so operators must check the actual destination and service configuration; that is why it addresses the operational task to find repeated sudo or login events on a distribution that uses /var/log/secure.

Incorrect Answers

A:

Kernel audit events retain subject and operation metadata under configured rules; its mechanism supports trace a protected file change back to a process and user identity, while the requested control must be able to find repeated sudo or login events on a distribution that uses /var/log/secure.

B:

sshd authentication messages record accounts, sources and results when the chosen logging stack writes them there; the outcome it supports is to investigate failed SSH sign-ins on distributions using that authentication log, whereas this scenario asks defenders to find repeated sudo or login events on a distribution that uses /var/log/secure.

D:

Sudo records command and account context, depending on configured syslog or journal policy; it could help someone trying to identify which operator escalated privileges to execute a maintenance command, but the problem is instead to find repeated sudo or login events on a distribution that uses /var/log/secure.

Question 795

To inspect errors emitted by one systemd-managed application service, what is the relevant defensive action?

  1. Linux secure log review
  2. Journald unit filter
  3. Logrotate audit
  4. Sudo event log
  5. Cron log analysis

Explanation

Correct Answer

B:

Journal queries filter by unit identity and boot context for focused troubleshooting; its relevant protective or investigative effect is to inspect errors emitted by one systemd-managed application service.

Incorrect Answers

A:

Platform logging conventions vary, so operators must check the actual destination and service configuration; the technique works for situations involving find repeated sudo or login events on a distribution that uses /var/log/secure, rather than this need to inspect errors emitted by one systemd-managed application service.

C:

Rotation schedules and retention settings explain legitimate and accidental record loss; the outcome it supports is to check whether logs disappeared because rotation was misconfigured, whereas this scenario asks defenders to inspect errors emitted by one systemd-managed application service.

D:

Sudo records command and account context, depending on configured syslog or journal policy; although relevant to identify which operator escalated privileges to execute a maintenance command, it does not by itself achieve the required task to inspect errors emitted by one systemd-managed application service.

E:

Scheduler records expose task execution times and account context for persistence review; it could help someone trying to find an unexpected periodic command running under a privileged identity, but the problem is instead to inspect errors emitted by one systemd-managed application service.

Question 796

To trace a protected file change back to a process and user identity, which option most directly provides the capability?

  1. Linux secure log review
  2. Linux auth.log review
  3. Journald unit filter
  4. Auditd syscall log

Explanation

Correct Answer

D:

Kernel audit events retain subject and operation metadata under configured rules; the requested outcome is precisely to trace a protected file change back to a process and user identity.

Incorrect Answers

A:

Platform logging conventions vary, so operators must check the actual destination and service configuration; it addresses the different need to find repeated sudo or login events on a distribution that uses /var/log/secure, leaving the requested ability to trace a protected file change back to a process and user identity unresolved.

B:

sshd authentication messages record accounts, sources and results when the chosen logging stack writes them there; the technique works for situations involving investigate failed SSH sign-ins on distributions using that authentication log, rather than this need to trace a protected file change back to a process and user identity.

C:

Journal queries filter by unit identity and boot context for focused troubleshooting. This can help to inspect errors emitted by one systemd-managed application service, but it does not provide the particular mechanism required to trace a protected file change back to a process and user identity.

Question 797

To identify which operator escalated privileges to execute a maintenance command, which control achieves the target outcome?

  1. Linux auth.log review
  2. Cron log analysis
  3. Auditd syscall log
  4. Sudo event log

Explanation

Correct Answer

D:

Sudo records command and account context, depending on configured syslog or journal policy; this choice fits the scenario because the team must identify which operator escalated privileges to execute a maintenance command.

Incorrect Answers

A:

sshd authentication messages record accounts, sources and results when the chosen logging stack writes them there; applying it would serve investigate failed SSH sign-ins on distributions using that authentication log without directly satisfying the goal to identify which operator escalated privileges to execute a maintenance command.

B:

Scheduler records expose task execution times and account context for persistence review; it addresses the different need to find an unexpected periodic command running under a privileged identity, leaving the requested ability to identify which operator escalated privileges to execute a maintenance command unresolved.

C:

Kernel audit events retain subject and operation metadata under configured rules; the technique works for situations involving trace a protected file change back to a process and user identity, rather than this need to identify which operator escalated privileges to execute a maintenance command.

Question 798

To find an unexpected periodic command running under a privileged identity, which solution should be adopted?

  1. Linux secure log review
  2. Cron log analysis
  3. Auditd syscall log
  4. Mac endpoint security telemetry
  5. Linux auth.log review
  6. Sudo event log

Explanation

Correct Answer

B:

Scheduler records expose task execution times and account context for persistence review; this mechanism directly supports the requirement to find an unexpected periodic command running under a privileged identity.

Incorrect Answers

A:

Platform logging conventions vary, so operators must check the actual destination and service configuration; its operational purpose is to find repeated sudo or login events on a distribution that uses /var/log/secure, not to achieve the specific requirement to find an unexpected periodic command running under a privileged identity.

C:

Kernel audit events retain subject and operation metadata under configured rules; it addresses the different need to trace a protected file change back to a process and user identity, leaving the requested ability to find an unexpected periodic command running under a privileged identity unresolved.

D:

Endpoint Security integrations can report process and file events under granted system permissions; the technique works for situations involving find a suspicious execution chain not visible in ordinary application logs, rather than this need to find an unexpected periodic command running under a privileged identity.

E:

sshd authentication messages record accounts, sources and results when the chosen logging stack writes them there; its mechanism supports investigate failed SSH sign-ins on distributions using that authentication log, while the requested control must be able to find an unexpected periodic command running under a privileged identity.

F:

Sudo records command and account context, depending on configured syslog or journal policy; the outcome it supports is to identify which operator escalated privileges to execute a maintenance command, whereas this scenario asks defenders to find an unexpected periodic command running under a privileged identity.

Question 799

To detect log loss when a remote collection destination becomes unavailable, which of the available controls is suitable?

  1. SSH session correlation
  2. Rsyslog queue monitoring
  3. Linux secure log review
  4. Sudo event log

Explanation

Correct Answer

B:

Queue size and error metrics reveal backpressure before important events are discarded; it supplies the specific control needed to detect log loss when a remote collection destination becomes unavailable.

Incorrect Answers

A:

Authentication, process audit and session records combine into a stronger activity timeline; a team would select it to match an administrator's login to commands and logout timing, which does not provide the particular result to detect log loss when a remote collection destination becomes unavailable.

C:

Platform logging conventions vary, so operators must check the actual destination and service configuration; applying it would serve find repeated sudo or login events on a distribution that uses /var/log/secure without directly satisfying the goal to detect log loss when a remote collection destination becomes unavailable.

D:

Sudo records command and account context, depending on configured syslog or journal policy; it addresses the different need to identify which operator escalated privileges to execute a maintenance command, leaving the requested ability to detect log loss when a remote collection destination becomes unavailable unresolved.

Question 800

To check whether logs disappeared because rotation was misconfigured, which option is the direct technical match?

  1. Auditd syscall log
  2. Logrotate audit
  3. SSH session correlation
  4. Cron log analysis
  5. Rsyslog queue monitoring

Explanation

Correct Answer

B:

Rotation schedules and retention settings explain legitimate and accidental record loss; that is why it addresses the operational task to check whether logs disappeared because rotation was misconfigured.

Incorrect Answers

A:

Kernel audit events retain subject and operation metadata under configured rules; that is useful when the task is to trace a protected file change back to a process and user identity, not the stated requirement to check whether logs disappeared because rotation was misconfigured.

C:

Authentication, process audit and session records combine into a stronger activity timeline; its operational purpose is to match an administrator's login to commands and logout timing, not to achieve the specific requirement to check whether logs disappeared because rotation was misconfigured.

D:

Scheduler records expose task execution times and account context for persistence review; applying it would serve find an unexpected periodic command running under a privileged identity without directly satisfying the goal to check whether logs disappeared because rotation was misconfigured.

E:

Queue size and error metrics reveal backpressure before important events are discarded; it addresses the different need to detect log loss when a remote collection destination becomes unavailable, leaving the requested ability to check whether logs disappeared because rotation was misconfigured unresolved.

Certified Network Defender (312-38) Practice Tests