CompTIA CySA+ (CS0-003) CS0-003 Practice Test 6
Question 50
TLS inspection at a secure access edge fails on certificate-pinned business applications. The necessary response and prerequisite corrective actions have been implemented; their effectiveness remains unproven. Management will accept closure only with a demonstrated result, not a claimed fix. Which follow-up check best verifies the security outcome?
- Collect pinned-app TLS errors and approved inspection-policy match logs
- Create narrowly scoped, documented pinning exceptions plus alternative endpoint visibility
- Verify app connectivity and security monitoring for both exempt and nonexempt traffic
- Distinguish certificate pinning failures from malicious TLS interception using client error traces
Explanation
Correct Answer
C:Verify app connectivity and security monitoring for both exempt and nonexempt traffic. This addresses the recorded condition: TLS inspection at a secure access edge fails on certificate-pinned business applications. It demonstrates that the corrective decision achieved its intended effect, identifies any remaining uncertainty and provides auditable closure evidence.
Incorrect Answers
A:The alternative to collect pinned-app TLS errors and approved inspection-policy match logs could help with collecting trustworthy source data in this case. A collection technique gathers information but alone does not prove the intended post-change outcome.
B:The alternative to create narrowly scoped, documented pinning exceptions plus alternative endpoint visibility could help with implementing a lasting control in this case. A preventive design may be sound but does not prove that it was implemented and tested.
D:The alternative to distinguish certificate pinning failures from malicious TLS interception using client error traces could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
Question 51
A Linux server baseline omits the executable path and owner of an unexpected cron task. The relevant initial records have already been collected; the analyst is evaluating their meaning. The case has not yet been attributed to a cause. Which targeted comparison most directly resolves the key evidentiary uncertainty?
- Collect crontab definitions and auditd execution logs using read-only access
- Disable the unexpected job only after capturing evidence and checking authorized maintenance
- Correlate the cron entry with executable path, file owner, package history, and change records
- Require ownership, executable allowlisting, and monitored cron-change audit records
Explanation
Correct Answer
C:Correlate the cron entry with executable path, file owner, package history, and change records. This addresses the recorded condition: A Linux server baseline omits the executable path and owner of an unexpected cron task. It interprets the evidence needed to decide whether the observation is malicious, benign, or a monitoring defect before another step changes the environment.
Incorrect Answers
A:The alternative to collect crontab definitions and auditd execution logs using read-only access could help with collecting trustworthy source data in this case. Collecting additional source records can be useful, but this scenario calls for interpreting the evidence and selecting the discriminating comparison.
B:The alternative to disable the unexpected job only after capturing evidence and checking authorized maintenance could help with choosing the immediate disposition in this case. A risk disposition before resolving the diagnostic uncertainty can misattribute the event.
D:The alternative to require ownership, executable allowlisting, and monitored cron-change audit records could help with implementing a lasting control in this case. A permanent redesign cannot establish what caused the current observation.
Question 52
A Linux server baseline omits the executable path and owner of an unexpected cron task. The team has formed a hypothesis but has not yet collected the necessary primary evidence. Investigators have agreed on the hypothesis but still need suitable primary records. Which scoped collection method will best establish facts with minimal disruption?
- Collect crontab definitions and auditd execution logs using read-only access
- Confirm the task owner, path, and execution hashes remain consistent with approved baseline
- Require ownership, executable allowlisting, and monitored cron-change audit records
- Disable the unexpected job only after capturing evidence and checking authorized maintenance
Explanation
Correct Answer
A:Collect crontab definitions and auditd execution logs using read-only access. This addresses the recorded condition: A Linux server baseline omits the executable path and owner of an unexpected cron task. It obtains the records, telemetry, or controlled test outcome at the relevant technical boundary rather than assuming the records are already complete.
Incorrect Answers
B:The alternative to confirm the task owner, path, and execution hashes remain consistent with approved baseline could help with proving the outcome in this case. A completion test assumes that collection and the necessary corrective work have already occurred.
C:The alternative to require ownership, executable allowlisting, and monitored cron-change audit records could help with implementing a lasting control in this case. An architectural control is a later intervention, not a low-impact evidence collection method.
D:The alternative to disable the unexpected job only after capturing evidence and checking authorized maintenance could help with choosing the immediate disposition in this case. A containment or prioritization decision does not provide the missing collection method.
Question 53
A Linux server baseline omits the executable path and owner of an unexpected cron task. Triage findings are documented and the incident lead must now make an operational risk decision. Responders must choose the next operational action, distinguishing confirmed exposure from an unproven suspicion. Which immediate response is most appropriate?
- Require ownership, executable allowlisting, and monitored cron-change audit records
- Correlate the cron entry with executable path, file owner, package history, and change records
- Disable the unexpected job only after capturing evidence and checking authorized maintenance
- Confirm the task owner, path, and execution hashes remain consistent with approved baseline
Explanation
Correct Answer
C:Disable the unexpected job only after capturing evidence and checking authorized maintenance. This addresses the recorded condition: A Linux server baseline omits the executable path and owner of an unexpected cron task. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
A:The alternative to require ownership, executable allowlisting, and monitored cron-change audit records could help with implementing a lasting control in this case. A durable fix follows an immediate risk decision and may require separate change authority.
B:The alternative to correlate the cron entry with executable path, file owner, package history, and change records could help with diagnosing the evidence in this case. Further diagnosis alone leaves the requested near-term risk disposition undecided.
D:The alternative to confirm the task owner, path, and execution hashes remain consistent with approved baseline could help with proving the outcome in this case. Testing closure before the immediate response would be premature.
Question 54
A Linux server baseline omits the executable path and owner of an unexpected cron task. The immediate response decision has already been made and authorized. With the acute response complete, engineering can change policy or architecture. Which enduring control is most directly linked to this root cause?
- Require ownership, executable allowlisting, and monitored cron-change audit records
- Correlate the cron entry with executable path, file owner, package history, and change records
- Collect crontab definitions and auditd execution logs using read-only access
- Confirm the task owner, path, and execution hashes remain consistent with approved baseline
Explanation
Correct Answer
A:Require ownership, executable allowlisting, and monitored cron-change audit records. This addresses the recorded condition: A Linux server baseline omits the executable path and owner of an unexpected cron task. It changes the underlying access path, control, collection capability, or process so the same failure does not recur simply after the ticket closes.
Incorrect Answers
B:The alternative to correlate the cron entry with executable path, file owner, package history, and change records could help with diagnosing the evidence in this case. Evidence analysis helps establish the cause but does not implement a prevention measure.
C:The alternative to collect crontab definitions and auditd execution logs using read-only access could help with collecting trustworthy source data in this case. A data-gathering method improves visibility but does not itself eliminate the recurring mechanism.
D:The alternative to confirm the task owner, path, and execution hashes remain consistent with approved baseline could help with proving the outcome in this case. A validation step is needed after a sustained control exists, not in place of designing it.
Question 55
A Linux server baseline omits the executable path and owner of an unexpected cron task. The necessary response and prerequisite corrective actions have been implemented; their effectiveness remains unproven. The response or authorized change is complete. Which specific outcome test best supports closure instead of relying on a ticket-status update?
- Disable the unexpected job only after capturing evidence and checking authorized maintenance
- Correlate the cron entry with executable path, file owner, package history, and change records
- Confirm the task owner, path, and execution hashes remain consistent with approved baseline
- Collect crontab definitions and auditd execution logs using read-only access
Explanation
Correct Answer
C:Confirm the task owner, path, and execution hashes remain consistent with approved baseline. This addresses the recorded condition: A Linux server baseline omits the executable path and owner of an unexpected cron task. It demonstrates that the corrective decision achieved its intended effect, identifies any remaining uncertainty and provides auditable closure evidence.
Incorrect Answers
A:The alternative to disable the unexpected job only after capturing evidence and checking authorized maintenance could help with choosing the immediate disposition in this case. An immediate disposition is a decision, not measured proof of final effectiveness.
B:The alternative to correlate the cron entry with executable path, file owner, package history, and change records could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
D:The alternative to collect crontab definitions and auditd execution logs using read-only access could help with collecting trustworthy source data in this case. A collection technique gathers information but alone does not prove the intended post-change outcome.
Question 56
A hybrid identity deployment records MFA approval but not the originating client or device state. The relevant initial records have already been collected; the analyst is evaluating their meaning. Initial records are available but their meaning is disputed. What analysis most directly tests the suspected cause before any claim of compromise or noncompliance?
- Relate MFA approvals to device compliance, client app, source IP and token issuance
- Perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields
- Enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry
- Query identity provider conditional-access details and the endpoint posture service
Explanation
Correct Answer
A:Relate MFA approvals to device compliance, client app, source IP and token issuance. This addresses the recorded condition: A hybrid identity deployment records MFA approval but not the originating client or device state. It interprets the evidence needed to decide whether the observation is malicious, benign, or a monitoring defect before another step changes the environment.
Incorrect Answers
B:The alternative to perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields could help with proving the outcome in this case. Closure testing is appropriate after a change; it does not resolve the original unknown cause.
C:The alternative to enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry could help with implementing a lasting control in this case. A permanent redesign cannot establish what caused the current observation.
D:The alternative to query identity provider conditional-access details and the endpoint posture service could help with collecting trustworthy source data in this case. Collecting additional source records can be useful, but this scenario calls for interpreting the evidence and selecting the discriminating comparison.
Question 57
A hybrid identity deployment records MFA approval but not the originating client or device state. The team has formed a hypothesis but has not yet collected the necessary primary evidence. The analyst needs a defensible technical method to obtain the necessary source information, before deciding containment or changing permanent controls. Which method is best?
- Query identity provider conditional-access details and the endpoint posture service
- Revoke suspicious sessions where approved MFA cannot be tied to trusted device context
- Relate MFA approvals to device compliance, client app, source IP and token issuance
- Perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields
Explanation
Correct Answer
A:Query identity provider conditional-access details and the endpoint posture service. This addresses the recorded condition: A hybrid identity deployment records MFA approval but not the originating client or device state. It obtains the records, telemetry, or controlled test outcome at the relevant technical boundary rather than assuming the records are already complete.
Incorrect Answers
B:The alternative to revoke suspicious sessions where approved MFA cannot be tied to trusted device context could help with choosing the immediate disposition in this case. A containment or prioritization decision does not provide the missing collection method.
C:The alternative to relate MFA approvals to device compliance, client app, source IP and token issuance could help with diagnosing the evidence in this case. An investigative comparison describes what to assess but not how the required primary records should be acquired.
D:The alternative to perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields could help with proving the outcome in this case. A completion test assumes that collection and the necessary corrective work have already occurred.
Question 58
A hybrid identity deployment records MFA approval but not the originating client or device state. Triage findings are documented and the incident lead must now make an operational risk decision. Security and service owners need a near-term risk decision under current constraints. Which action should take precedence now, not after system redesign?
- Revoke suspicious sessions where approved MFA cannot be tied to trusted device context
- Relate MFA approvals to device compliance, client app, source IP and token issuance
- Query identity provider conditional-access details and the endpoint posture service
- Enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry
Explanation
Correct Answer
A:Revoke suspicious sessions where approved MFA cannot be tied to trusted device context. This addresses the recorded condition: A hybrid identity deployment records MFA approval but not the originating client or device state. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
B:The alternative to relate MFA approvals to device compliance, client app, source IP and token issuance could help with diagnosing the evidence in this case. Further diagnosis alone leaves the requested near-term risk disposition undecided.
C:The alternative to query identity provider conditional-access details and the endpoint posture service could help with collecting trustworthy source data in this case. Collecting another dataset can inform the decision but does not select the proportionate operational response.
D:The alternative to enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry could help with implementing a lasting control in this case. A durable fix follows an immediate risk decision and may require separate change authority.
Question 59
A hybrid identity deployment records MFA approval but not the originating client or device state. The immediate response decision has already been made and authorized. The immediate risk has been triaged and engineering must prevent recurrence. Which sustainable control corrects the underlying failure mode rather than merely collecting more evidence?
- Revoke suspicious sessions where approved MFA cannot be tied to trusted device context
- Enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry
- Perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields
- Query identity provider conditional-access details and the endpoint posture service
Explanation
Correct Answer
B:Enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry. This addresses the recorded condition: A hybrid identity deployment records MFA approval but not the originating client or device state. It changes the underlying access path, control, collection capability, or process so the same failure does not recur simply after the ticket closes.
Incorrect Answers
A:The alternative to revoke suspicious sessions where approved MFA cannot be tied to trusted device context could help with choosing the immediate disposition in this case. A temporary or immediate disposition may lower risk now without providing a durable corrective control.
C:The alternative to perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields could help with proving the outcome in this case. A validation step is needed after a sustained control exists, not in place of designing it.
D:The alternative to query identity provider conditional-access details and the endpoint posture service could help with collecting trustworthy source data in this case. A data-gathering method improves visibility but does not itself eliminate the recurring mechanism.
Question 60
A hybrid identity deployment records MFA approval but not the originating client or device state. The necessary response and prerequisite corrective actions have been implemented; their effectiveness remains unproven. A reviewer requests evidence of effectiveness and residual limitations after remediation. Which validation is most persuasive?
- Relate MFA approvals to device compliance, client app, source IP and token issuance
- Perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields
- Revoke suspicious sessions where approved MFA cannot be tied to trusted device context
- Enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry
Explanation
Correct Answer
B:Perform legitimate and untrusted-device sign-ins to verify policy outcomes and audit fields. This addresses the recorded condition: A hybrid identity deployment records MFA approval but not the originating client or device state. It demonstrates that the corrective decision achieved its intended effect, identifies any remaining uncertainty and provides auditable closure evidence.
Incorrect Answers
A:The alternative to relate MFA approvals to device compliance, client app, source IP and token issuance could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
C:The alternative to revoke suspicious sessions where approved MFA cannot be tied to trusted device context could help with choosing the immediate disposition in this case. An immediate disposition is a decision, not measured proof of final effectiveness.
D:The alternative to enforce phishing-resistant MFA and device-bound conditional access with complete audit telemetry could help with implementing a lasting control in this case. A preventive design may be sound but does not prove that it was implemented and tested.