DOP-C02 Exam Dumps : AWS Certified DevOps Engineer - Professional

Service-managed StackSets are the correct low-overhead deployment model when AWS Organizations trusted access is enabled. CloudFormation creates and manages the required StackSet execution roles, so self-managed permissions are unnecessary. However, AWS explicitly states that service-managed StackSets do not deploy stacks to the organization management account, even if the management account is part of the organization or belongs to an OU. Therefore, targeting the root OU deploys to the member accounts, but the management account still needs a separate normal CloudFormation stack. Option B is the only answer that covers both the member accounts and the management account with the least operational overhead. Option A misses the management account, while C and D require unnecessary self-managed role administration.

================

This failure is typically due to incorrectly configured health checks in Elastic Load Balancing for the Classic Load Balancer, Application Load Balancer, or Network Load Balancer used to manage traffic for the deployment group. To resolve the issue, review and correct any errors in the health check configuration for the load balancer.

The requirement specifies enforcing encryption before CloudFormation creates or updates resources. This is key because preventive enforcement must occur during the provisioning workflow, not after resources already exist. AWS provides CloudFormation Hooks specifically for this purpose. A Hook allows an organization to intercept a CloudFormation stack operation and validate resource configurations before provisioning occurs. This feature is recommended by AWS for pre-deployment governance such as enforcing encryption policies, tag compliance, or security restrictions.

By enabling trusted access between CloudFormation StackSets and AWS Organizations, the Hook can be deployed centrally from the delegated administrator account across all accounts in the specified OU. Any attempt to create or update EBS volumes or SQS queues through CloudFormation is validated first by the Hook. If encryption is not configured, the operation fails immediately.

Option C (SCP) blocks API calls globally, but SCPs cannot perform conditional logic based on resource properties passed by CloudFormation prior to creation. Option B (AWS Config) detects violations after resources already exist, which does not satisfy “before stack operation.” Option D (Lambda remediation) also occurs after the resource is created.

Thus, CloudFormation Hooks distributed via StackSets provide the only solution that enforces compliance before the provisioning lifecycle