SCS-C02 · Question #24
A company discovers a billing anomaly in its AWS account. A security consultant investigates the anomaly and discovers that an employee who left the company 30 days ago still has access to the…
The correct answer is C. In AWS CloudTrail, filter the event history to display results from the past 30 days. Create an. CloudTrail for as quickly as possible. Look up events related to the creation, modification, or deletion of resources in your AWS account. AWS Cost Anomaly Detection: For a new service subscription, 10 days of historical service usage data is needed before anomalies can be…
Question
A company discovers a billing anomaly in its AWS account. A security consultant investigates the anomaly and discovers that an employee who left the company 30 days ago still has access to the account. The company has not monitored account activity in the past. The security consultant needs to determine which resources have been deployed or reconfigured by the employee as quickly as possible. Which solution will meet these requirements?
Options
- AIn AWS Cost Explorer, filter chart data to display results from the past 30 days. Export the results
- BUse AWS Cost Anomaly Detection to create a cost monitor. Access the detection history. Set the
- CIn AWS CloudTrail, filter the event history to display results from the past 30 days. Create an
- DUse AWS Audit Manager to create an assessment for the past 30 days. Apply a usage-based
How the community answered
(48 responses)- A2% (1)
- B6% (3)
- C81% (39)
- D10% (5)
Explanation
CloudTrail for as quickly as possible. Look up events related to the creation, modification, or deletion of resources in your AWS account. AWS Cost Anomaly Detection: For a new service subscription, 10 days of historical service usage data is needed before anomalies can be detected for that service. If you create a new monitor, it can take up to 24 hours to begin detecting new anomalies.
Topics
Community Discussion
No community discussion yet for this question.