Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified DevOps Engineer - Professional · AWS
Select 2 answers.
This question asks for 2 answers, but our data marks only 1. Compare with the community discussion below for the full answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
A - You can enable trusted access using either the AWS Config console or the AWS Organizations console. https://docs.aws.amazon.com/organizations/latest/userguide/services-that-can-integrate-config.html
AE is the answer AWS Config offers an organization-wide data aggregation capability called the Config organization aggregator. It allows you to collect and view configuration data from all member accounts within your AWS Organization in a single location. This centralizes your view of resource configurations and compliance posture across your entire AWS environment.
A and E are correct: <AWS Config is manually configured in each AWS account> means we dont need ACF (only used for the deployment of AWS config). <centrally configure AWS Config for all accounts> means we need to allow a central account to control AWS config in all member accounts. - <record resource changes to a central account> means we need to collect data from all member accounts and push to the central account B: service-linked role only used for interacting with other AWS services C: no need ACF D: we need AWS Config organization aggregator in the delegated administrator account, not the organization's management account