[Solved] You wrote this IAM policy condition:{"Condition": {"StringEquals": {"dynamodb:LeadingKeys": "user123"}}}Why might this cause an error when enforcing fine-grained access control? | DynamoDB

DynamoDB - Security and Access Control

You wrote this IAM policy condition:

{"Condition": {"StringEquals": {"dynamodb:LeadingKeys": "user123"}}}

Why might this cause an error when enforcing fine-grained access control?

AThe policy must use StringNotEquals instead

BStringEquals is not a valid condition operator

Cdynamodb:LeadingKeys expects a list, not a single string

DLeadingKeys cannot be used in conditions

Step-by-Step Solution

Solution:

Step 1: Check expected data type for dynamodb:LeadingKeys
dynamodb:LeadingKeys requires a list of strings, even if only one key is specified.
Step 2: Identify the error in the policy
The policy uses a single string instead of a list, causing a syntax or runtime error.
Final Answer:
dynamodb:LeadingKeys expects a list, not a single string -> Option C
Quick Check:
LeadingKeys must be a list in IAM conditions [OK]

Quick Trick: Always use a list for dynamodb:LeadingKeys values [OK]

Common Mistakes:

MISTAKES

Master "Security and Access Control" in DynamoDB

9 interactive learning modes - each teaches the same concept differently

More DynamoDB Quizzes

You wrote this IAM policy condition: