A company deployed a landing zone with an AWS Organizations structure and an SCP. Developers may create resources only with CloudFormation and the AWS CDK. A DevOps engineer finds that SQS queues deployed in different CloudFormation stacks have inconsistent configurations and the application cost-allocation tag is sometimes missing. The engineer needs to enforce tagging, encourage code reuse, and prevent inconsistent SQS configurations. What should the engineer do?

The correct answer addresses all requirements: enforcing tagging, encouraging code reuse, and preventing inconsistent SQS configurations. Using AWS CDK tagging ensures the cost allocation tag is consistently applied. Requiring developers to define SQS queues with the AWS CDK and deploy them as CDK stacks promotes code reuse through constructs and enforces consistent configurations since CDK code is programmatic and reusable. CloudFormation StackSets, mentioned in the correct option, are suitable for deploying consistent resources across multiple accounts or regions. Incorrect options: Organizations tag policies enforce tagging but don't inherently encourage code reuse or prevent inconsistent SQS configurations. CloudFormation StackSets can deploy consistent resources, but without a standardized definition (like CDK constructs), inconsistency can still arise. SCPs enforce policies at the organizational level but cannot directly enforce code reuse or prevent configuration inconsistencies within CloudFormation templates. CloudFormation modules promote reuse but don't automatically enforce tagging like CDK tagging can. CDK feature flags are for controlling CDK behavior during synthesis, not for enforcing tagging or deployment mechanisms. While using CDK for SQS definition is good, feature flags are not the primary mechanism for the stated goals.