From 3fc5b6ad66b8fe9695ca8b58c43b0145d30cecb8e409e669d6d700f6a9e7aaf7 Mon Sep 17 00:00:00 2001 From: Rijndael Date: Mon, 2 Nov 2026 22:34:05 +0000 Subject: [PATCH] formatting --- Papers/Practice Exam 3.md | 3 ++- Study/DynamoDB/ReadWriteUnits.md | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/Papers/Practice Exam 3.md b/Papers/Practice Exam 3.md index 9da4fd6..39afec4 100644 --- a/Papers/Practice Exam 3.md +++ b/Papers/Practice Exam 3.md @@ -63,4 +63,5 @@ When items from a primary table are written to the GSI they consume write capaci In this scenario, it is likely that the Developer assumed that the GSI would need fewer WCUs as it is more read-intensive and neglected to factor in the WCUs required for writing data into the GSI. Therefore, the most likely explanation is that the write capacity units on the GSI are under provisioned ---- \ No newline at end of file +--- + diff --git a/Study/DynamoDB/ReadWriteUnits.md b/Study/DynamoDB/ReadWriteUnits.md index e885b40..c6275e3 100644 --- a/Study/DynamoDB/ReadWriteUnits.md +++ b/Study/DynamoDB/ReadWriteUnits.md @@ -16,3 +16,4 @@ m =& \text{ modifier: } \\ &2\text{ for transactional operations} \end{aligned} $$ +See [[Read and Write Units - Set 3]] for some examples.