CompTIA CySA+ (CS0-003) CS0-003 Practice Test 2
Question 10
Container workloads are destroyed after autoscaling before security events reach the collector. 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?
- Use a DaemonSet log forwarder with durable buffering and orchestration audit events
- Kill a test pod and confirm its final events arrive once with workload identity attached
- Preserve available runtime events and prioritize workloads that disappeared before ingestion
- Match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination
Explanation
Correct Answer
B:Kill a test pod and confirm its final events arrive once with workload identity attached. This addresses the recorded condition: Container workloads are destroyed after autoscaling before security events reach the collector. 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 use a DaemonSet log forwarder with durable buffering and orchestration audit events 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.
C:The alternative to preserve available runtime events and prioritize workloads that disappeared before ingestion 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 match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
Question 11
A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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?
- Compare the outbound destination with function invocation metadata and approved service integrations
- Enable managed function execution logs plus provider network-flow records without host persistence
- Invoke the function under controlled conditions and verify destination attribution and log retention
- Apply least-privilege egress policies and durable execution telemetry for each function revision
Explanation
Correct Answer
A:Compare the outbound destination with function invocation metadata and approved service integrations. This addresses the recorded condition: A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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 enable managed function execution logs plus provider network-flow records without host persistence 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.
C:The alternative to invoke the function under controlled conditions and verify destination attribution and log retention could help with proving the outcome in this case. Closure testing is appropriate after a change; it does not resolve the original unknown cause.
D:The alternative to apply least-privilege egress policies and durable execution telemetry for each function revision could help with implementing a lasting control in this case. A permanent redesign cannot establish what caused the current observation.
Question 12
A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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?
- Invoke the function under controlled conditions and verify destination attribution and log retention
- Compare the outbound destination with function invocation metadata and approved service integrations
- Enable managed function execution logs plus provider network-flow records without host persistence
- Temporarily restrict the unexpected egress destination after checking business dependency
Explanation
Correct Answer
C:Enable managed function execution logs plus provider network-flow records without host persistence. This addresses the recorded condition: A serverless function calls an unknown endpoint but its runtime has no persistent host logs. It obtains the records, telemetry, or controlled test outcome at the relevant technical boundary rather than assuming the records are already complete.
Incorrect Answers
A:The alternative to invoke the function under controlled conditions and verify destination attribution and log retention could help with proving the outcome in this case. A completion test assumes that collection and the necessary corrective work have already occurred.
B:The alternative to compare the outbound destination with function invocation metadata and approved service integrations 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 temporarily restrict the unexpected egress destination after checking business dependency could help with choosing the immediate disposition in this case. A containment or prioritization decision does not provide the missing collection method.
Question 13
A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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?
- Compare the outbound destination with function invocation metadata and approved service integrations
- Enable managed function execution logs plus provider network-flow records without host persistence
- Temporarily restrict the unexpected egress destination after checking business dependency
- Apply least-privilege egress policies and durable execution telemetry for each function revision
Explanation
Correct Answer
C:Temporarily restrict the unexpected egress destination after checking business dependency. This addresses the recorded condition: A serverless function calls an unknown endpoint but its runtime has no persistent host logs. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
A:The alternative to compare the outbound destination with function invocation metadata and approved service integrations could help with diagnosing the evidence in this case. Further diagnosis alone leaves the requested near-term risk disposition undecided.
B:The alternative to enable managed function execution logs plus provider network-flow records without host persistence 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 apply least-privilege egress policies and durable execution telemetry for each function revision 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 14
A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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?
- Enable managed function execution logs plus provider network-flow records without host persistence
- Apply least-privilege egress policies and durable execution telemetry for each function revision
- Temporarily restrict the unexpected egress destination after checking business dependency
- Invoke the function under controlled conditions and verify destination attribution and log retention
Explanation
Correct Answer
B:Apply least-privilege egress policies and durable execution telemetry for each function revision. This addresses the recorded condition: A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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 enable managed function execution logs plus provider network-flow records without host persistence could help with collecting trustworthy source data in this case. A data-gathering method improves visibility but does not itself eliminate the recurring mechanism.
C:The alternative to temporarily restrict the unexpected egress destination after checking business dependency 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.
D:The alternative to invoke the function under controlled conditions and verify destination attribution and log retention 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 15
A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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?
- Temporarily restrict the unexpected egress destination after checking business dependency
- Apply least-privilege egress policies and durable execution telemetry for each function revision
- Compare the outbound destination with function invocation metadata and approved service integrations
- Invoke the function under controlled conditions and verify destination attribution and log retention
Explanation
Correct Answer
D:Invoke the function under controlled conditions and verify destination attribution and log retention. This addresses the recorded condition: A serverless function calls an unknown endpoint but its runtime has no persistent host logs. 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 temporarily restrict the unexpected egress destination after checking business dependency 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 apply least-privilege egress policies and durable execution telemetry for each function revision 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.
C:The alternative to compare the outbound destination with function invocation metadata and approved service integrations could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
Question 16
Cloud and on-premises identity providers emit incompatible subject identifiers during federation. The relevant initial records have already been collected; the analyst is evaluating their meaning. At triage, analysts have conflicting explanations and must decide what evidence distinguishes them, rather than take corrective action yet. What is the best analysis?
- Correlate IdP subject, tenant, federation transaction ID, and token issuer fields
- Quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions
- Replay known federation sign-ins and confirm each event maps to one correct identity
- Resolve federated user identifiers through immutable mapping claims before combining identity events
Explanation
Correct Answer
D:Resolve federated user identifiers through immutable mapping claims before combining identity events. This addresses the recorded condition: Cloud and on-premises identity providers emit incompatible subject identifiers during federation. 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 correlate IdP subject, tenant, federation transaction ID, and token issuer fields 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 quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions could help with choosing the immediate disposition in this case. A risk disposition before resolving the diagnostic uncertainty can misattribute the event.
C:The alternative to replay known federation sign-ins and confirm each event maps to one correct identity could help with proving the outcome in this case. Closure testing is appropriate after a change; it does not resolve the original unknown cause.
Question 17
Cloud and on-premises identity providers emit incompatible subject identifiers during federation. The team has formed a hypothesis but has not yet collected the necessary primary evidence. The lead has authorized limited data collection, not a production redesign. What technique most directly gathers the records required for this case?
- Quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions
- Normalize identities to a stable cross-provider principal key with issuer-scoped namespaces
- Resolve federated user identifiers through immutable mapping claims before combining identity events
- Correlate IdP subject, tenant, federation transaction ID, and token issuer fields
Explanation
Correct Answer
D:Correlate IdP subject, tenant, federation transaction ID, and token issuer fields. This addresses the recorded condition: Cloud and on-premises identity providers emit incompatible subject identifiers during federation. It obtains the records, telemetry, or controlled test outcome at the relevant technical boundary rather than assuming the records are already complete.
Incorrect Answers
A:The alternative to quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions could help with choosing the immediate disposition in this case. A containment or prioritization decision does not provide the missing collection method.
B:The alternative to normalize identities to a stable cross-provider principal key with issuer-scoped namespaces could help with implementing a lasting control in this case. An architectural control is a later intervention, not a low-impact evidence collection method.
C:The alternative to resolve federated user identifiers through immutable mapping claims before combining identity events 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.
Question 18
Cloud and on-premises identity providers emit incompatible subject identifiers during federation. Triage findings are documented and the incident lead must now make an operational risk decision. The investigation has reached the immediate response decision. Which disposition is most proportionate to the evidence and business impact, before designing a long-term fix?
- Quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions
- Correlate IdP subject, tenant, federation transaction ID, and token issuer fields
- Normalize identities to a stable cross-provider principal key with issuer-scoped namespaces
- Replay known federation sign-ins and confirm each event maps to one correct identity
Explanation
Correct Answer
A:Quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions. This addresses the recorded condition: Cloud and on-premises identity providers emit incompatible subject identifiers during federation. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
B:The alternative to correlate IdP subject, tenant, federation transaction ID, and token issuer fields 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.
C:The alternative to normalize identities to a stable cross-provider principal key with issuer-scoped namespaces could help with implementing a lasting control in this case. A durable fix follows an immediate risk decision and may require separate change authority.
D:The alternative to replay known federation sign-ins and confirm each event maps to one correct identity could help with proving the outcome in this case. Testing closure before the immediate response would be premature.
Question 19
Cloud and on-premises identity providers emit incompatible subject identifiers during federation. The immediate response decision has already been made and authorized. The incident or finding is stabilized. The team is selecting a durable preventive design that respects legitimate business operation. Which change best fits?
- Resolve federated user identifiers through immutable mapping claims before combining identity events
- Quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions
- Normalize identities to a stable cross-provider principal key with issuer-scoped namespaces
- Replay known federation sign-ins and confirm each event maps to one correct identity
Explanation
Correct Answer
C:Normalize identities to a stable cross-provider principal key with issuer-scoped namespaces. This addresses the recorded condition: Cloud and on-premises identity providers emit incompatible subject identifiers during federation. 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 resolve federated user identifiers through immutable mapping claims before combining identity events could help with diagnosing the evidence in this case. Evidence analysis helps establish the cause but does not implement a prevention measure.
B:The alternative to quarantine identity alerts with untrusted principal linkage instead of falsely attributing actions 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.
D:The alternative to replay known federation sign-ins and confirm each event maps to one correct identity 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 20
Cloud and on-premises identity providers emit incompatible subject identifiers during federation. 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?
- Replay known federation sign-ins and confirm each event maps to one correct identity
- Resolve federated user identifiers through immutable mapping claims before combining identity events
- Correlate IdP subject, tenant, federation transaction ID, and token issuer fields
- Normalize identities to a stable cross-provider principal key with issuer-scoped namespaces
Explanation
Correct Answer
A:Replay known federation sign-ins and confirm each event maps to one correct identity. This addresses the recorded condition: Cloud and on-premises identity providers emit incompatible subject identifiers during federation. It demonstrates that the corrective decision achieved its intended effect, identifies any remaining uncertainty and provides auditable closure evidence.
Incorrect Answers
B:The alternative to resolve federated user identifiers through immutable mapping claims before combining identity events 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 correlate IdP subject, tenant, federation transaction ID, and token issuer fields 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.
D:The alternative to normalize identities to a stable cross-provider principal key with issuer-scoped namespaces 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.