A Database Specialist is performing a proof of concept with Amazon Aurora using a small instance to confirm a simple database behavior. When loading a large dataset and creating the index, the…

Question

Options

• AThe scaling of Aurora storage cannot catch up with the data loading. The Database Specialist
• BThe scaling of Aurora storage cannot catch up with the data loading. The Database Specialist
• CThe local storage used to store temporary tables is full. The Database Specialist needs to scale
• DThe local storage used to store temporary tables is full. The Database Specialist needs to enable

• A
  2% (1)
• B
  5% (3)
• C
  84% (47)
• D
  9% (5)

Explanation

Explanation

Option C is correct because the error message references a temporary file, not Aurora's primary storage - Aurora uses local instance storage for temporary tables and sort operations during index creation, and when a small instance is used, this local temp space can quickly become exhausted with large datasets. The fix is to scale up to a larger instance type, which provides more local storage for these temporary operations.

Options A and B are incorrect because Aurora's shared storage layer automatically scales up to 128 TiB and is not the bottleneck here - the error explicitly points to a temporary file issue, not a problem with Aurora's distributed storage architecture.

Option D is incorrect because enabling a feature is not the appropriate resolution; the root cause is insufficient local instance storage, which can only be addressed by scaling up to a larger instance with more local temp storage capacity.

Memory Tip

Think "temp = local, Aurora = shared" - Aurora's magic auto-scaling applies to its shared distributed storage, but temporary files live locally on the instance itself. If you see "temporary file" in an Aurora error, think instance size, not storage scaling.

No community discussion yet for this question.