What is the MOST likely cause of these issues?

A developer is trying get data from an Amazon DynamoDB table called demoman-table. The developer configured the AWS CLI to use a specific IAM use’s credentials and ran the following command.

The command returned errors and no rows were returned.

What is the MOST likely cause of these issues?
A . The command is incorrect; it should be rewritten to use put-item with a string argument
B . The developer needs to log a ticket with AWS Support to enable access to the demoman-table
C . Amazon DynamoOB cannot be accessed from the AWS CLI and needs to called via the REST API
D . The IAM user needs an associated policy with read access to demoman-table

View Answer

Answer: D

Explanation:

This solution will most likely solve the issues because it will grant the IAM user the necessary permission to access the DynamoDB table using the AWS CLI command. The error message indicates that the IAM user does not have sufficient access rights to perform the scan operation on the table. Option A is not optimal because it will change the command to use put-item instead of scan, which will not achieve the desired result of getting data from the table. Option B is not optimal because it will involve contacting AWS Support, which may not be necessary or efficient for this issue. Option C is not optimal because it will state that DynamoDB cannot be accessed from the AWS CLI, which is incorrect as DynamoDB supports AWS CLI commands.

Reference: AWS CLI for DynamoDB, [IAM Policies for DynamoDB]