AWS - DynamoDBYou defined a GSI on a DynamoDB table but your application reports 'ValidationException: Index not found'. What is the most likely cause?AThe GSI has a different sort key than the base table.BThe GSI uses the same partition key as the base table.CThe GSI was not created or is still being created.DThe table has no provisioned throughput.Check Answer
Step-by-Step SolutionSolution:Step 1: Understand the error meaning'Index not found' means the requested GSI does not exist or is not ready.Step 2: Check GSI creation statusGSI creation is asynchronous; if still creating or failed, queries fail with this error.Final Answer:The GSI was not created or is still being created. -> Option CQuick Check:GSI must exist and be active before querying [OK]Quick Trick: Wait for GSI creation to complete before querying [OK]Common Mistakes:Assuming error due to key schema mismatchIgnoring GSI creation statusConfusing throughput issues with index errors
Master "DynamoDB" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - Resources and methods - Quiz 8hard AWS Lambda - Why serverless matters - Quiz 9hard Auto Scaling - Minimum, maximum, and desired capacity - Quiz 14medium Auto Scaling - Auto Scaling with ELB integration - Quiz 15hard Auto Scaling - Auto Scaling groups - Quiz 6medium CloudWatch - Alarm actions (SNS, Auto Scaling) - Quiz 2easy CloudWatch - Why monitoring matters - Quiz 4medium DynamoDB - Why DynamoDB for NoSQL - Quiz 15hard RDS and Relational Databases - Read replicas for performance - Quiz 14medium RDS and Relational Databases - Parameter groups and option groups - Quiz 13medium