Question 810
To investigate repeated requests to an administrative path returning errors, what control should be selected?
- Load balancer logs
- Web application audit logs
- IDS alert log enrichment
- Router configuration-change logs
- 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.
Question 811
To identify upstream failures that coincide with suspicious inbound requests, which security control is most appropriate?
- Load balancer logs
- Apache access log review
- Nginx error log review
- IDS alert log enrichment
Explanation
Correct Answer
C:Server errors provide processing details not visible from access status codes alone; it supplies the specific control needed to identify upstream failures that coincide with suspicious inbound requests.
Incorrect Answers
A:Gateway records connect front-end requests with upstream selection and termination behavior; it could help someone trying to determine which backend server processed a particular client connection, but the problem is instead to identify upstream failures that coincide with suspicious inbound requests.
B:Request methods, URLs, status codes and source addresses reveal probing patterns; that is useful when the task is to investigate repeated requests to an administrative path returning errors, not the stated requirement to identify upstream failures that coincide with suspicious inbound requests.
D: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 identify upstream failures that coincide with suspicious inbound requests.
Question 812
To determine which backend server processed a particular client connection, what would a security logging engineer implement or use?
- IDS alert log enrichment
- Load balancer logs
- DNS resolver logs
- Nginx error log review
Explanation
Correct Answer
B:Gateway records connect front-end requests with upstream selection and termination behavior; that is why it addresses the operational task to determine which backend server processed a particular client connection.
Incorrect Answers
A:Enrichment helps analysts prioritize detections beyond a bare signature identifier; although relevant to add asset criticality and identity context to signature matches, it does not by itself achieve the required task to determine which backend server processed a particular client connection.
C:Query records expose requested names and client identities when resolver policy retains them; that is useful when the task is to detect many unusual subdomain lookups from one workstation, not the stated requirement to determine which backend server processed a particular client connection.
D:Server errors provide processing details not visible from access status codes alone; a team would select it to identify upstream failures that coincide with suspicious inbound requests, which does not provide the particular result to determine which backend server processed a particular client connection.
Question 813
To add asset criticality and identity context to signature matches, which practice addresses that objective?
- Proxy access logs
- Nginx error log review
- Web application audit logs
- IDS alert log enrichment
Explanation
Correct Answer
D:Enrichment helps analysts prioritize detections beyond a bare signature identifier; its relevant protective or investigative effect is to add asset criticality and identity context to signature matches.
Incorrect Answers
A:HTTP proxy metadata includes requested destinations and user context within the proxy's visibility; the outcome it supports is to find requests from infected clients to known command domains, whereas this scenario asks defenders to add asset criticality and identity context to signature matches.
B:Server errors provide processing details not visible from access status codes alone; although relevant to identify upstream failures that coincide with suspicious inbound requests, it does not by itself achieve the required task to add asset criticality and identity context to signature matches.
C:Application-level identity and action records supplement web-server request logs; it could help someone trying to trace which authenticated account changed sensitive application permissions, but the problem is instead to add asset criticality and identity context to signature matches.
Question 814
To determine which backend server processed a particular client connection, to add asset criticality and identity context to signature matches, and to trace which authenticated account changed sensitive application permissions, which THREE measures should the team select? Choose THREE.
- Load balancer logs
- IDS alert log enrichment
- Nginx error log review
- DNS resolver logs
- Apache access log review
- Web application audit logs
Explanation
Correct Answers
A:Gateway records connect front-end requests with upstream selection and termination behavior; its contribution to the combined design is specifically to determine which backend server processed a particular client connection.
B:Enrichment helps analysts prioritize detections beyond a bare signature identifier; its contribution to the combined design is specifically to add asset criticality and identity context to signature matches.
F:Application-level identity and action records supplement web-server request logs; its contribution to the combined design is specifically to trace which authenticated account changed sensitive application permissions.
Incorrect Answers
C:Server errors provide processing details not visible from access status codes alone; although relevant to identify upstream failures that coincide with suspicious inbound requests, it does not by itself achieve the required task to determine which backend server processed a particular client connection, to add asset criticality and identity context to signature matches, and to trace which authenticated account changed sensitive application permissions.
D:Query records expose requested names and client identities when resolver policy retains them; it could help someone trying to detect many unusual subdomain lookups from one workstation, but the problem is instead to determine which backend server processed a particular client connection, to add asset criticality and identity context to signature matches, and to trace which authenticated account changed sensitive application permissions.
E:Request methods, URLs, status codes and source addresses reveal probing patterns; that is useful when the task is to investigate repeated requests to an administrative path returning errors, not the stated requirement to determine which backend server processed a particular client connection, to add asset criticality and identity context to signature matches, and to trace which authenticated account changed sensitive application permissions.
Question 815
To detect a surge of security events caused by misconfigured network equipment, which tool, policy, or technique is appropriate?
- SIEM detection rule testing
- SIEM ingestion rate
- Log source coverage matrix
- UEBA impossible-travel alert
- SIEM field mapping
Explanation
Correct Answer
B:Events-per-second metrics reveal collection capacity issues separately from threat severity; this choice fits the scenario because the team must detect a surge of security events caused by misconfigured network equipment.
Incorrect Answers
A:Controlled replay validates parsing, thresholds and alert routing before production reliance; the technique works for situations involving confirm a new brute-force correlation produces alerts with expected sample events, rather than this need to detect a surge of security events caused by misconfigured network equipment.
C:Mapped inventories reveal missing monitoring even when the SIEM dashboard appears healthy; the outcome it supports is to find critical domain controllers absent from centralized event collection, whereas this scenario asks defenders to detect a surge of security events caused by misconfigured network equipment.
D:Behavior analytics compares activity against plausible movement while allowing VPN and routing exceptions; although relevant to identify unlikely sign-in geography changes for one workforce identity, it does not by itself achieve the required task to detect a surge of security events caused by misconfigured network equipment.
E:Correct extraction supports reliable cross-source queries and investigation pivots; it could help someone trying to ensure every VPN log includes normalized source IP and username fields, but the problem is instead to detect a surge of security events caused by misconfigured network equipment.
Question 816
To confirm a new brute-force correlation produces alerts with expected sample events, what safeguard would be most applicable?
- SOAR alert enrichment
- SIEM field mapping
- SIEM detection rule testing
- Detection content versioning
Explanation
Correct Answer
C:Controlled replay validates parsing, thresholds and alert routing before production reliance; this mechanism directly supports the requirement to confirm a new brute-force correlation produces alerts with expected sample events.
Incorrect Answers
A:Automated lookup reduces analyst preparation time without independently proving an alert is malicious; it addresses the different need to automatically attach domain reputation and device owner to a SIEM finding, leaving the requested ability to confirm a new brute-force correlation produces alerts with expected sample events unresolved.
B:Correct extraction supports reliable cross-source queries and investigation pivots; the technique works for situations involving ensure every VPN log includes normalized source IP and username fields, rather than this need to confirm a new brute-force correlation produces alerts with expected sample events.
D:Version-controlled rules make modifications auditable and reversible; the outcome it supports is to restore an earlier alert rule after a tuning change suppresses critical matches, whereas this scenario asks defenders to confirm a new brute-force correlation produces alerts with expected sample events.
Question 817
To ensure every VPN log includes normalized source IP and username fields, what is the relevant defensive action?
- SIEM ingestion rate
- SIEM field mapping
- SOAR alert enrichment
- Log source coverage matrix
- SIEM detection rule testing
- UEBA impossible-travel alert
Explanation
Correct Answer
B:Correct extraction supports reliable cross-source queries and investigation pivots; it supplies the specific control needed to ensure every VPN log includes normalized source IP and username fields.
Incorrect Answers
A:Events-per-second metrics reveal collection capacity issues separately from threat severity; applying it would serve detect a surge of security events caused by misconfigured network equipment without directly satisfying the goal to ensure every VPN log includes normalized source IP and username fields.
C:Automated lookup reduces analyst preparation time without independently proving an alert is malicious; the technique works for situations involving automatically attach domain reputation and device owner to a SIEM finding, rather than this need to ensure every VPN log includes normalized source IP and username fields.
D:Mapped inventories reveal missing monitoring even when the SIEM dashboard appears healthy; its mechanism supports find critical domain controllers absent from centralized event collection, while the requested control must be able to ensure every VPN log includes normalized source IP and username fields.
E:Controlled replay validates parsing, thresholds and alert routing before production reliance; the outcome it supports is to confirm a new brute-force correlation produces alerts with expected sample events, whereas this scenario asks defenders to ensure every VPN log includes normalized source IP and username fields.
F:Behavior analytics compares activity against plausible movement while allowing VPN and routing exceptions; although relevant to identify unlikely sign-in geography changes for one workforce identity, it does not by itself achieve the required task to ensure every VPN log includes normalized source IP and username fields.
Question 818
To identify unlikely sign-in geography changes for one workforce identity, which option most directly provides the capability?
- Log source coverage matrix
- Case evidence links
- SIEM detection rule testing
- UEBA impossible-travel alert
Explanation
Correct Answer
D:Behavior analytics compares activity against plausible movement while allowing VPN and routing exceptions; that is why it addresses the operational task to identify unlikely sign-in geography changes for one workforce identity.
Incorrect Answers
A:Mapped inventories reveal missing monitoring even when the SIEM dashboard appears healthy; its operational purpose is to find critical domain controllers absent from centralized event collection, not to achieve the specific requirement to identify unlikely sign-in geography changes for one workforce identity.
B:Traceable references let reviewers reproduce findings despite later aggregation and rotation; applying it would serve preserve the exact log query and record IDs supporting an incident conclusion without directly satisfying the goal to identify unlikely sign-in geography changes for one workforce identity.
C:Controlled replay validates parsing, thresholds and alert routing before production reliance; it addresses the different need to confirm a new brute-force correlation produces alerts with expected sample events, leaving the requested ability to identify unlikely sign-in geography changes for one workforce identity unresolved.
Question 819
To find critical domain controllers absent from centralized event collection, which control achieves the target outcome?
- SIEM field mapping
- SOAR alert enrichment
- Log source coverage matrix
- Detection content versioning
Explanation
Correct Answer
C:Mapped inventories reveal missing monitoring even when the SIEM dashboard appears healthy; its relevant protective or investigative effect is to find critical domain controllers absent from centralized event collection.
Incorrect Answers
A:Correct extraction supports reliable cross-source queries and investigation pivots; a team would select it to ensure every VPN log includes normalized source IP and username fields, which does not provide the particular result to find critical domain controllers absent from centralized event collection.
B:Automated lookup reduces analyst preparation time without independently proving an alert is malicious; its operational purpose is to automatically attach domain reputation and device owner to a SIEM finding, not to achieve the specific requirement to find critical domain controllers absent from centralized event collection.
D:Version-controlled rules make modifications auditable and reversible; it addresses the different need to restore an earlier alert rule after a tuning change suppresses critical matches, leaving the requested ability to find critical domain controllers absent from centralized event collection unresolved.
Question 820
To restore an earlier alert rule after a tuning change suppresses critical matches, which solution should be adopted?
- High-cardinality field control
- Case evidence links
- UEBA impossible-travel alert
- SOAR alert enrichment
- Detection content versioning
Explanation
Correct Answer
E:Version-controlled rules make modifications auditable and reversible; the requested outcome is precisely to restore an earlier alert rule after a tuning change suppresses critical matches.
Incorrect Answers
A:Field management and normalization control search performance without indiscriminate dropping of evidence; that is useful when the task is to prevent unbounded unique values from overwhelming a security analytics index, not the stated requirement to restore an earlier alert rule after a tuning change suppresses critical matches.
B:Traceable references let reviewers reproduce findings despite later aggregation and rotation; a team would select it to preserve the exact log query and record IDs supporting an incident conclusion, which does not provide the particular result to restore an earlier alert rule after a tuning change suppresses critical matches.
C:Behavior analytics compares activity against plausible movement while allowing VPN and routing exceptions; its operational purpose is to identify unlikely sign-in geography changes for one workforce identity, not to achieve the specific requirement to restore an earlier alert rule after a tuning change suppresses critical matches.
D:Automated lookup reduces analyst preparation time without independently proving an alert is malicious; applying it would serve automatically attach domain reputation and device owner to a SIEM finding without directly satisfying the goal to restore an earlier alert rule after a tuning change suppresses critical matches.