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

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.

Question 801

To match an administrator's login to commands and logout timing, which approach should a security logging engineer choose?

  1. Mac unified log review
  2. Sudo event log
  3. SSH session correlation
  4. Mac endpoint security telemetry

Explanation

Correct Answer

C:

Authentication, process audit and session records combine into a stronger activity timeline; its relevant protective or investigative effect is to match an administrator's login to commands and logout timing.

Incorrect Answers

A:

Unified logging stores structured system and process messages queried through supported tooling; it could help someone trying to investigate an application crash or service event on a recent macOS host, but the problem is instead to match an administrator's login to commands and logout timing.

B:

Sudo records command and account context, depending on configured syslog or journal policy; that is useful when the task is to identify which operator escalated privileges to execute a maintenance command, not the stated requirement to match an administrator's login to commands and logout timing.

D:

Endpoint Security integrations can report process and file events under granted system permissions; its operational purpose is to find a suspicious execution chain not visible in ordinary application logs, not to achieve the specific requirement to match an administrator's login to commands and logout timing.

Question 802

To investigate an application crash or service event on a recent macOS host and to find a suspicious execution chain not visible in ordinary application logs, which TWO measures should the defender select? Choose TWO.

  1. Mac endpoint security telemetry
  2. SSH session correlation
  3. Cron log analysis
  4. Sudo event log
  5. Mac unified log review

Explanation

Correct Answers

A:

Endpoint Security integrations can report process and file events under granted system permissions; its contribution to the combined design is specifically to find a suspicious execution chain not visible in ordinary application logs.

E:

Unified logging stores structured system and process messages queried through supported tooling; its contribution to the combined design is specifically to investigate an application crash or service event on a recent macOS host.

Incorrect Answers

B:

Authentication, process audit and session records combine into a stronger activity timeline; it could help someone trying to match an administrator's login to commands and logout timing, but the problem is instead to investigate an application crash or service event on a recent macOS host and to find a suspicious execution chain not visible in ordinary application logs.

C:

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 an application crash or service event on a recent macOS host and to find a suspicious execution chain not visible in ordinary application logs.

D:

Sudo records command and account context, depending on configured syslog or journal policy; a team would select it to identify which operator escalated privileges to execute a maintenance command, which does not provide the particular result to investigate an application crash or service event on a recent macOS host and to find a suspicious execution chain not visible in ordinary application logs.

Question 803

To find a suspicious execution chain not visible in ordinary application logs, which method is designed for the task?

  1. Rsyslog queue monitoring
  2. Logrotate audit
  3. Mac endpoint security telemetry
  4. SSH session correlation

Explanation

Correct Answer

C:

Endpoint Security integrations can report process and file events under granted system permissions; this choice fits the scenario because the team must find a suspicious execution chain not visible in ordinary application logs.

Incorrect Answers

A:

Queue size and error metrics reveal backpressure before important events are discarded; the outcome it supports is to detect log loss when a remote collection destination becomes unavailable, whereas this scenario asks defenders to find a suspicious execution chain not visible in ordinary application logs.

B:

Rotation schedules and retention settings explain legitimate and accidental record loss; although relevant to check whether logs disappeared because rotation was misconfigured, it does not by itself achieve the required task to find a suspicious execution chain not visible in ordinary application logs.

D:

Authentication, process audit and session records combine into a stronger activity timeline; that is useful when the task is to match an administrator's login to commands and logout timing, not the stated requirement to find a suspicious execution chain not visible in ordinary application logs.

Question 804

To locate which access rule blocked a legitimate HTTPS service connection, what technique should the team use?

  1. Firewall allow/deny analysis
  2. VPN session logs
  3. Router login audit
  4. Router configuration-change logs

Explanation

Correct Answer

A:

Firewall decision records show matching policy, addressing and action, subject to log configuration; this mechanism directly supports the requirement to locate which access rule blocked a legitimate HTTPS service connection.

Incorrect Answers

B:

Tunnel records link authenticated users to network addressing during the access interval; the outcome it supports is to trace remote-user connection times and assigned tunnel addresses, whereas this scenario asks defenders to locate which access rule blocked a legitimate HTTPS service connection.

C:

Device AAA records associate login sources and user identities with control-plane access; although relevant to find administrative access from an unfamiliar management workstation, it does not by itself achieve the required task to locate which access rule blocked a legitimate HTTPS service connection.

D:

Configuration accounting and syslog tie command changes to operational incidents; it could help someone trying to identify the actor who altered a routing filter before an outage, but the problem is instead to locate which access rule blocked a legitimate HTTPS service connection.

Question 805

To find administrative access from an unfamiliar management workstation, which protective or investigative measure applies?

  1. VPN session logs
  2. Router login audit
  3. Router configuration-change logs
  4. Apache access log review
  5. Firewall allow/deny analysis

Explanation

Correct Answer

B:

Device AAA records associate login sources and user identities with control-plane access; it supplies the specific control needed to find administrative access from an unfamiliar management workstation.

Incorrect Answers

A:

Tunnel records link authenticated users to network addressing during the access interval; the technique works for situations involving trace remote-user connection times and assigned tunnel addresses, rather than this need to find administrative access from an unfamiliar management workstation.

C:

Configuration accounting and syslog tie command changes to operational incidents; the outcome it supports is to identify the actor who altered a routing filter before an outage, whereas this scenario asks defenders to find administrative access from an unfamiliar management workstation.

D:

Request methods, URLs, status codes and source addresses reveal probing patterns; although relevant to investigate repeated requests to an administrative path returning errors, it does not by itself achieve the required task to find administrative access from an unfamiliar management workstation.

E:

Firewall decision records show matching policy, addressing and action, subject to log configuration; it could help someone trying to locate which access rule blocked a legitimate HTTPS service connection, but the problem is instead to find administrative access from an unfamiliar management workstation.

Question 806

To identify the actor who altered a routing filter before an outage, what is the most direct option?

  1. Router configuration-change logs
  2. Apache access log review
  3. VPN session logs
  4. Router login audit

Explanation

Correct Answer

A:

Configuration accounting and syslog tie command changes to operational incidents; that is why it addresses the operational task to identify the actor who altered a routing filter before an outage.

Incorrect Answers

B:

Request methods, URLs, status codes and source addresses reveal probing patterns; the technique works for situations involving investigate repeated requests to an administrative path returning errors, rather than this need to identify the actor who altered a routing filter before an outage.

C:

Tunnel records link authenticated users to network addressing during the access interval; its mechanism supports trace remote-user connection times and assigned tunnel addresses, while the requested control must be able to identify the actor who altered a routing filter before an outage.

D:

Device AAA records associate login sources and user identities with control-plane access; the outcome it supports is to find administrative access from an unfamiliar management workstation, whereas this scenario asks defenders to identify the actor who altered a routing filter before an outage.

Question 807

To trace remote-user connection times and assigned tunnel addresses, what should defenders select?

  1. Nginx error log review
  2. Router login audit
  3. DNS resolver logs
  4. VPN session logs

Explanation

Correct Answer

D:

Tunnel records link authenticated users to network addressing during the access interval; its relevant protective or investigative effect is to trace remote-user connection times and assigned tunnel addresses.

Incorrect Answers

A:

Server errors provide processing details not visible from access status codes alone; applying it would serve identify upstream failures that coincide with suspicious inbound requests without directly satisfying the goal to trace remote-user connection times and assigned tunnel addresses.

B:

Device AAA records associate login sources and user identities with control-plane access; it addresses the different need to find administrative access from an unfamiliar management workstation, leaving the requested ability to trace remote-user connection times and assigned tunnel addresses unresolved.

C:

Query records expose requested names and client identities when resolver policy retains them; the technique works for situations involving detect many unusual subdomain lookups from one workstation, rather than this need to trace remote-user connection times and assigned tunnel addresses.

Question 808

To find requests from infected clients to known command domains, which mechanism best fits?

  1. VPN session logs
  2. Proxy access logs
  3. Apache access log review
  4. Router configuration-change logs

Explanation

Correct Answer

B:

HTTP proxy metadata includes requested destinations and user context within the proxy's visibility; the requested outcome is precisely to find requests from infected clients to known command domains.

Incorrect Answers

A:

Tunnel records link authenticated users to network addressing during the access interval; its operational purpose is to trace remote-user connection times and assigned tunnel addresses, not to achieve the specific requirement to find requests from infected clients to known command domains.

C:

Request methods, URLs, status codes and source addresses reveal probing patterns; it addresses the different need to investigate repeated requests to an administrative path returning errors, leaving the requested ability to find requests from infected clients to known command domains unresolved.

D:

Configuration accounting and syslog tie command changes to operational incidents; the technique works for situations involving identify the actor who altered a routing filter before an outage, rather than this need to find requests from infected clients to known command domains.

Question 809

To detect many unusual subdomain lookups from one workstation, which measure best meets the requirement?

  1. Router configuration-change logs
  2. Firewall allow/deny analysis
  3. Proxy access logs
  4. DNS resolver logs

Explanation

Correct Answer

D:

Query records expose requested names and client identities when resolver policy retains them; this choice fits the scenario because the team must detect many unusual subdomain lookups from one workstation.

Incorrect Answers

A:

Configuration accounting and syslog tie command changes to operational incidents; a team would select it to identify the actor who altered a routing filter before an outage, which does not provide the particular result to detect many unusual subdomain lookups from one workstation.

B:

Firewall decision records show matching policy, addressing and action, subject to log configuration; its operational purpose is to locate which access rule blocked a legitimate HTTPS service connection, not to achieve the specific requirement to detect many unusual subdomain lookups from one workstation.

C:

HTTP proxy metadata includes requested destinations and user context within the proxy's visibility; applying it would serve find requests from infected clients to known command domains without directly satisfying the goal to detect many unusual subdomain lookups from one workstation.

Question 810

To investigate repeated requests to an administrative path returning errors, what control should be selected?

  1. Load balancer logs
  2. Web application audit logs
  3. IDS alert log enrichment
  4. Router configuration-change logs
  5. Apache access log review

Explanation

Correct Answer

E:

Request methods, URLs, status codes and source addresses reveal probing patterns; this mechanism directly supports the requirement to investigate repeated requests to an administrative path returning errors.

Incorrect Answers

A:

Gateway records connect front-end requests with upstream selection and termination behavior; that is useful when the task is to determine which backend server processed a particular client connection, not the stated requirement to investigate repeated requests to an administrative path returning errors.

B:

Application-level identity and action records supplement web-server request logs; a team would select it to trace which authenticated account changed sensitive application permissions, which does not provide the particular result to investigate repeated requests to an administrative path returning errors.

C:

Enrichment helps analysts prioritize detections beyond a bare signature identifier; its operational purpose is to add asset criticality and identity context to signature matches, not to achieve the specific requirement to investigate repeated requests to an administrative path returning errors.

D:

Configuration accounting and syslog tie command changes to operational incidents; applying it would serve identify the actor who altered a routing filter before an outage without directly satisfying the goal to investigate repeated requests to an administrative path returning errors.

Certified Network Defender (312-38) Practice Tests