A company needs to enforce tagging requirements for Amazon DynamoDB tables in its AWS accounts. A SysOps administrator must implement a solution to identify and remediate all DynamoDB tables that do…

Question

Options

• ACreate a custom AWS Lambda function to evaluate and remediate all DynamoDB tables.
• BCreate a custom AWS Lambda function to evaluate and remediate ail DynamoDB tables.
• CUse the required-tags AWS Config managed rule to evaluate all DynamoDB tables for the
• DCreate an Amazon EventBridge managed rule to evaluate all DynamoDB tables for the

• A
  17% (9)
• B
  4% (2)
• C
  72% (39)
• D
  7% (4)

Explanation

Option C is correct because AWS Config's required-tags managed rule is a pre-built, fully managed solution that natively evaluates DynamoDB tables (and other AWS resources) for tag compliance - no custom code required - and can be paired with AWS Config Remediation Actions to automatically fix non-compliant resources, minimizing operational overhead. Options A and B are essentially identical (the word "ail" in B appears to be a typo for "all") and both describe writing a custom Lambda function, which introduces code you must author, deploy, test, and maintain - far more operational burden than using a managed rule. Option D is incorrect because Amazon EventBridge does not have "managed rules" for evaluating resource compliance; EventBridge is an event bus/routing service, and any compliance evaluation logic would still require a custom Lambda target, recreating the same overhead as A and B.

Memory tip: Think of AWS Config as your compliance auditor - when the question mentions "evaluate resources for compliance" + "least overhead," AWS Config managed rules should be your first instinct, since they require zero custom code and integrate natively with auto-remediation.

No community discussion yet for this question.