Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 447 discussion

Ans "D" - more granular. Q: What is the difference between a linked account monitor in a payer account, and a services monitor in a linked account? A linked account monitor in a payer account will monitor the spend of all services, in total, for that linked account. A services monitor in a linked account will monitor the individual spend for each service for that linked account. For example, if there is a spike in S3 spending, but a dip in EC2 spending of the same amount (net neutral change), the linked account monitor in the payer account will not detect this because it is monitoring the total account spend across all services. However, the services monitor in the linked account would detect the S3 spike since it is monitoring each service spend individually.

On reconsideration: D, as it deals with the individual services in an account, not just the total cost.

By creating a cost monitor with the monitor type set to "AWS services," Cost Anomaly Detection will monitor the individual spend for each service within the linked account. This would allow the company to detect anomalies or spikes in spending for specific services, even if there is a corresponding decrease in another service that offsets the overall account spend. Given the requirement to identify resources that cause an increase in cost, monitoring at the service level would provide more granular visibility and enable the company to pinpoint the specific services or resources responsible for cost increases. Creating a subscription to send daily AWS cost summaries to the operations team and specifying a threshold for cost variance would ensure that the team is notified when the cost increase for any individual service exceeds the defined threshold.

Option D: Using AWS Cost Anomaly Detection to create a cost monitor with a monitor type of AWS services: This option focuses on individual AWS services, making it easier to identify which specific resource is causing the increase in costs. This approach provides detailed insights into each service's contribution to your company's overall expenses, making it easier to pinpoint the issue and take corrective action. Considering all options, Option D seems to be the most suitable solution for identifying resources that cause an increase in costs and automatically notifying the company's operations team. This approach offers real-time monitoring, detailed insights into individual services' contributions, and automatic notifications when costs exceed specified thresholds.

For those who think the correct answer is C: A Linked Account monitor detects anomalies at the account level. While it can identify which account has unusual spending, it does NOT pinpoint the SPECIFIC SERVICES or RESOURCES causing the increase, as the statement requires.

"identify resources that cause an increase in cost " D for sure

Monitoring at the AWS service level can be useful, but it may not provide the same comprehensive view of costs across accounts as the linked account monitor type. Therefore, option C provides a more adaptive and comprehensive solution for detecting cost anomalies and notifying the operations team.

D for me

D. An AWS service monitor will be applicable to all customers since it tracks and detects anomalies across any service they deploy https://aws.amazon.com/aws-cost-management/aws-cost-anomaly-detection/faqs/#:~:text=An%20AWS%20service%20monitor%20will%20be%20applicable%20to%20all%20customers%20since%20it%20tracks%20and%20detects%20anomalies%20across%20any%20service%20they%20deploy

c: identify abnormal accounts d: identify abnormal service, which is desired.

vote D here A linked account monitor can track up to 10 different linked accounts. A linked account monitor tracks spending aggregated across all of the designated linked accounts. For example, if a linked account monitor tracks Account A and Account B, and then Account A’s usage spikes while Account B’s usage dips by the same amount, there will be no anomaly detected because it is a net neutral change. ref https://aws.amazon.com/aws-cost-management/aws-cost-anomaly-detection/faqs/

C more granular

Option C and Not Option D : Linked account - This monitor evaluates the total spend of an individual, or group of, member accounts. If your Organizations need to segment spend by team, product, services, or environment, this monitor is useful. The maximum number of member accounts that you can select for each monitor is 10. https://docs.aws.amazon.com/cost-management/latest/userguide/getting-started-ad.html#monitor-type-def

I will go with C because the scenario says, "to create all new infrastructure in its AWS member accounts."

D seems more granular to detect thich resource in which account generated the bill. C seem only care about the balance across accounts as below "linked account monitor can track up to 10 different linked accounts. A linked account monitor tracks spending aggregated across all of the designated linked accounts. For example, if a linked account monitor tracks Account A and Account B, and then Account A’s usage spikes while Account B’s usage dips by the same amount, there will be no anomaly detected because it is a net neutral change" https://aws.amazon.com/aws-cost-management/aws-cost-anomaly-detection/faqs/

Answer is between C and D. Choosing monitor type AWS Services is more appropriate than Linked Account because the monitor AWS Services monitors all resources including resources from all member accounts of the organization. Also with Linked Accounts you can only add max 10 accounts to a single monitor. Therefore answer D is correct.

C is the correct answer. D is not granular enough.