You have a DynamoDB table with 1000 items. You perform a parallel scan with Segment=0 and TotalSegments=4. What portion of the table does this scan segment read?
Think about how the total segments divide the table for parallel scanning.
When you set TotalSegments=4, the table is divided into 4 parts. Each segment scans roughly 1/4 of the table. So segment 0 scans about 25% of the items.
Which of the following is the correct way to specify parameters for a parallel scan in DynamoDB using the AWS SDK?
Remember that Segment must be less than TotalSegments.
The Segment parameter must be a number from 0 to TotalSegments - 1. Option C correctly sets Segment=1 and TotalSegments=4.
You want to speed up scanning a large DynamoDB table using parallel scan. Which approach will most effectively improve scan speed?
Think about how dividing work among multiple workers helps.
Increasing TotalSegments allows more parallel workers to scan different parts of the table simultaneously, improving speed.
You run a parallel scan with parameters: { TableName: 'MyTable', Segment: 5, TotalSegments: 4 }. What error will this cause?
Check the allowed range for the Segment parameter.
The Segment value must be between 0 and TotalSegments - 1. Here, 5 is not less than 4, so a validation error occurs.
You perform a parallel scan on a large DynamoDB table with TotalSegments=10. How does this affect the consumption of read capacity units compared to a single scan?
Think about how parallel scan divides the work but still reads the entire table.
Parallel scan divides the table into segments scanned concurrently. The total read capacity units consumed is about the same as a full scan, but the load is distributed across multiple workers.