Check the AWS Config for Resource Changes and Network Impact | Exam SOA-C02 Study Guide

Correct Answer: D.

Configuration Items are created when there is a change in resources.

This includes metadata, attributes, relationships, current configuration and related events.

For the above case, the Operations team can check the Configuration Items in AWS Config to verify changes made on the resources.

At the same time, relationships can show the impact of the changes on other AWS resources.

Option A is incorrect as Configuration Aggregator is an invalid option.

Option B is incorrect as the Configuration recorder stores configuration of resources.

It would not be created when there is a change in resources.

Option C is incorrect as Configuration History is a collection of Configuration items collected from a resource over a period.

For more information on Configuration Items with AWS Config, refer to the following URL,

https://docs.aws.amazon.com/config/latest/developerguide/config-concepts.html

The AWS Config service is used to track and manage changes to AWS resources. It provides a detailed view of the configuration of the resources in an AWS account, including how they are related to each other. The service continuously monitors and records changes to AWS resources, and keeps track of configuration changes over time.

To answer the question, the component of the AWS Config that can be viewed to check the required information is the "Configuration History" option, which is option C.

The Configuration History option provides a chronological view of configuration changes that have been made to AWS resources in an AWS account. It displays the details of the changes that have been made, including who made the changes, when the changes were made, and what specific changes were made to each resource.

Using the Configuration History option, the Operations Team can view the changes made by the Junior Engineer and determine which resources were impacted by those changes. The Configuration History option also allows the Operations Team to track changes made to specific resources over time, providing a complete audit trail of configuration changes.

The other options listed in the question are also components of the AWS Config service. However, they do not provide the same level of detailed information as the Configuration History option.

Option A, Configuration Aggregator, is used to collect and manage configuration data from multiple AWS accounts and regions.

Option B, Configuration Recorder, is used to record changes to AWS resources and store that information in an Amazon S3 bucket.

Option D, Configuration Items, is a metadata object that represents a resource that AWS Config tracks. It contains information about the resource's configuration, including its relationships to other resources. However, it does not provide the same detailed information as the Configuration History option.