Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 30
Question 290
An analytics consumer must view both old and new item images after DynamoDB updates. Which stream view is needed?
- Apply supported event filtering on the DynamoDB Streams event-source mapping.
- Enable DynamoDB Streams with NEW_AND_OLD_IMAGES.
- Enable DynamoDB Streams and configure a Lambda event-source mapping.
- Process stream records in shard order for the item key and avoid reordering its dependent side effects.
Explanation
Correct Answer
B:This stream view includes both item states for update comparison and audit logic. Modify a test item and verify its pre- and post-update attributes in the record.
Incorrect Answers
A:Event filtering routes selected stream records into function batches based on defined patterns. Enable DynamoDB Streams with NEW_AND_OLD_IMAGES. Modify a test item and verify its pre- and post-update attributes in the record.
C:DynamoDB Streams exposes ordered per-item change records for downstream consumers. Enable DynamoDB Streams with NEW_AND_OLD_IMAGES. Modify a test item and verify its pre- and post-update attributes in the record.
D:DynamoDB Streams preserves ordering of changes for a particular item; consumer parallelism needs careful handling. Enable DynamoDB Streams with NEW_AND_OLD_IMAGES. Modify a test item and verify its pre- and post-update attributes in the record.
Question 291
A consuming Lambda repeatedly fails on one bad DynamoDB stream record and blocks its shard. Which recovery settings should be evaluated?
- Apply supported event filtering on the DynamoDB Streams event-source mapping.
- Configure bounded retry attempts, maximum record age, and an on-failure destination.
- Use idempotent writes keyed by event or item version.
- Enable DynamoDB Streams and configure a Lambda event-source mapping.
Explanation
Correct Answer
B:Stream event-source settings can prevent a poison record from blocking processing indefinitely. Inject a failing record and verify bounded retries and captured failure data.
Incorrect Answers
A:Event filtering routes selected stream records into function batches based on defined patterns. Configure bounded retry attempts, maximum record age, and an on-failure destination. Inject a failing record and verify bounded retries and captured failure data.
C:Stream consumption can retry records, so downstream side effects cannot assume global exactly-once delivery. Configure bounded retry attempts, maximum record age, and an on-failure destination. Inject a failing record and verify bounded retries and captured failure data.
D:DynamoDB Streams exposes ordered per-item change records for downstream consumers. Configure bounded retry attempts, maximum record age, and an on-failure destination. Inject a failing record and verify bounded retries and captured failure data.
Question 292
A function consuming DynamoDB Streams must preserve order for one partition key. Which architectural assumption is correct?
- Enable DynamoDB Streams and configure a Lambda event-source mapping.
- Use idempotent writes keyed by event or item version.
- Apply supported event filtering on the DynamoDB Streams event-source mapping.
- Process stream records in shard order for the item key and avoid reordering its dependent side effects.
Explanation
Correct Answer
D:DynamoDB Streams preserves ordering of changes for a particular item; consumer parallelism needs careful handling. Update the same key repeatedly and inspect applied version sequence.
Incorrect Answers
A:DynamoDB Streams exposes ordered per-item change records for downstream consumers. Process stream records in shard order for the item key and avoid reordering its dependent side effects. Update the same key repeatedly and inspect applied version sequence.
B:Stream consumption can retry records, so downstream side effects cannot assume global exactly-once delivery. Process stream records in shard order for the item key and avoid reordering its dependent side effects. Update the same key repeatedly and inspect applied version sequence.
C:Event filtering routes selected stream records into function batches based on defined patterns. Process stream records in shard order for the item key and avoid reordering its dependent side effects. Update the same key repeatedly and inspect applied version sequence.
Question 293
A new consumer needs independent change processing from the primary application without slowing writes. Which pattern suits this requirement?
- Use idempotent writes keyed by event or item version.
- Attach a DynamoDB stream consumer rather than synchronously calling it from application writes.
- Process stream records in shard order for the item key and avoid reordering its dependent side effects.
- Enable DynamoDB Streams and configure a Lambda event-source mapping.
Explanation
Correct Answer
B:An asynchronous change stream decouples downstream notifications from foreground write latency. Disable the consumer and confirm table writes still succeed.
Incorrect Answers
A:Stream consumption can retry records, so downstream side effects cannot assume global exactly-once delivery. Attach a DynamoDB stream consumer rather than synchronously calling it from application writes. Disable the consumer and confirm table writes still succeed.
C:DynamoDB Streams preserves ordering of changes for a particular item; consumer parallelism needs careful handling. Attach a DynamoDB stream consumer rather than synchronously calling it from application writes. Disable the consumer and confirm table writes still succeed.
D:DynamoDB Streams exposes ordered per-item change records for downstream consumers. Attach a DynamoDB stream consumer rather than synchronously calling it from application writes. Disable the consumer and confirm table writes still succeed.
Question 294
A Lambda stream consumer sees repeated change records after a retry. What should the target data store implement?
- Enable DynamoDB Streams and configure a Lambda event-source mapping.
- Configure bounded retry attempts, maximum record age, and an on-failure destination.
- Use idempotent writes keyed by event or item version.
- Process stream records in shard order for the item key and avoid reordering its dependent side effects.
Explanation
Correct Answer
C:Stream consumption can retry records, so downstream side effects cannot assume global exactly-once delivery. Replay the same sequence number and confirm one logical update.
Incorrect Answers
A:DynamoDB Streams exposes ordered per-item change records for downstream consumers. Use idempotent writes keyed by event or item version. Replay the same sequence number and confirm one logical update.
B:Stream event-source settings can prevent a poison record from blocking processing indefinitely. Use idempotent writes keyed by event or item version. Replay the same sequence number and confirm one logical update.
D:DynamoDB Streams preserves ordering of changes for a particular item; consumer parallelism needs careful handling. Use idempotent writes keyed by event or item version. Replay the same sequence number and confirm one logical update.
Question 295
A team wants to rebuild a search index from DynamoDB changes but the stream holds only a bounded history. What additional recovery source is necessary?
- Apply supported event filtering on the DynamoDB Streams event-source mapping.
- Combine retained stream processing with a full table export or snapshot for rebuilds beyond stream retention.
- Enable DynamoDB Streams with NEW_AND_OLD_IMAGES.
- Configure bounded retry attempts, maximum record age, and an on-failure destination.
Explanation
Correct Answer
B:Streams do not provide indefinite historical replay; a full snapshot establishes baseline state. Expire test stream history and rebuild the index from snapshot plus subsequent changes.
Incorrect Answers
A:Event filtering routes selected stream records into function batches based on defined patterns. Combine retained stream processing with a full table export or snapshot for rebuilds beyond stream retention. Expire test stream history and rebuild the index from snapshot plus subsequent changes.
C:This stream view includes both item states for update comparison and audit logic. Combine retained stream processing with a full table export or snapshot for rebuilds beyond stream retention. Expire test stream history and rebuild the index from snapshot plus subsequent changes.
D:Stream event-source settings can prevent a poison record from blocking processing indefinitely. Combine retained stream processing with a full table export or snapshot for rebuilds beyond stream retention. Expire test stream history and rebuild the index from snapshot plus subsequent changes.
Question 296
A workflow should react to item modifications matching a business rule, not every write. How can filtering reduce unnecessary Lambda invocations?
- Enable DynamoDB Streams and configure a Lambda event-source mapping.
- Apply supported event filtering on the DynamoDB Streams event-source mapping.
- Enable DynamoDB Streams with NEW_AND_OLD_IMAGES.
- Configure bounded retry attempts, maximum record age, and an on-failure destination.
Explanation
Correct Answer
B:Event filtering routes selected stream records into function batches based on defined patterns. Update matching and nonmatching items and count function invocations.
Incorrect Answers
A:DynamoDB Streams exposes ordered per-item change records for downstream consumers. Apply supported event filtering on the DynamoDB Streams event-source mapping. Update matching and nonmatching items and count function invocations.
C:This stream view includes both item states for update comparison and audit logic. Apply supported event filtering on the DynamoDB Streams event-source mapping. Update matching and nonmatching items and count function invocations.
D:Stream event-source settings can prevent a poison record from blocking processing indefinitely. Event filtering routes selected stream records into function batches based on defined patterns.
Question 297
New documents land in S3 and an OCR process should run without clients waiting for recognition. Which trigger decouples processing?
- Use S3 Inventory reports as the scalable object listing source.
- Route S3 events through EventBridge rules to separate target services.
- Configure S3 object-created notifications to SQS for asynchronous OCR workers.
- Send the object event to a queue and process large jobs using appropriately long-running workers.
Explanation
Correct Answer
C:S3 notifications can enqueue file events while ingestion returns independently of processing. Upload a document and verify the notification is queued for the worker.
Incorrect Answers
A:Inventory provides periodic flat-file metadata at scale; event notifications are not a full snapshot. Configure S3 object-created notifications to SQS for asynchronous OCR workers. Upload a document and verify the notification is queued for the worker.
B:EventBridge routes matched object events to independent subscribers without hardcoded upload hooks. Configure S3 object-created notifications to SQS for asynchronous OCR workers. Upload a document and verify the notification is queued for the worker.
D:Decoupled workers such as ECS tasks can handle work that exceeds Lambda's execution limit. Configure S3 object-created notifications to SQS for asynchronous OCR workers. Upload a document and verify the notification is queued for the worker.
Question 298
An S3 notification delivery can be duplicated during retries. How should an indexing consumer avoid duplicate document entries?
- Use the bucket/key/version or sequencer context in an idempotent indexing operation.
- Read the version ID from supported event context and retrieve that version from a versioned bucket.
- Use S3 Inventory reports as the scalable object listing source.
- Filter S3 event notifications by a dedicated incoming key prefix and write outputs elsewhere.
Explanation
Correct Answer
A:S3 event notifications can be delivered at least once; consumers should deduplicate effects. Replay a notification and confirm only one logical index entry.
Incorrect Answers
B:Object version identifiers prevent a delayed consumer from accidentally processing a newer object. Use the bucket/key/version or sequencer context in an idempotent indexing operation. Replay a notification and confirm only one logical index entry.
C:Inventory provides periodic flat-file metadata at scale; event notifications are not a full snapshot. Use the bucket/key/version or sequencer context in an idempotent indexing operation. Replay a notification and confirm only one logical index entry.
D:Source prefix filtering separates ingest events from the pipeline's own artifacts. Use the bucket/key/version or sequencer context in an idempotent indexing operation. Replay a notification and confirm only one logical index entry.
Question 299
An upload event should fan out to multiple distinct downstream applications with content filtering. What event route is appropriate?
- Read the version ID from supported event context and retrieve that version from a versioned bucket.
- Route S3 events through EventBridge rules to separate target services.
- Configure S3 object-created notifications to SQS for asynchronous OCR workers.
- Use an S3 event notification to a durable SQS queue and resume consumers later.
Explanation
Correct Answer
B:EventBridge routes matched object events to independent subscribers without hardcoded upload hooks. Upload two prefixes and verify only relevant consumer rules match.
Incorrect Answers
A:Object version identifiers prevent a delayed consumer from accidentally processing a newer object. Route S3 events through EventBridge rules to separate target services. Upload two prefixes and verify only relevant consumer rules match.
C:S3 notifications can enqueue file events while ingestion returns independently of processing. Route S3 events through EventBridge rules to separate target services. Upload two prefixes and verify only relevant consumer rules match.
D:A queue retains events during worker downtime; direct synchronous application callbacks would not. Route S3 events through EventBridge rules to separate target services. Upload two prefixes and verify only relevant consumer rules match.
Question 300
An S3 notification points to an object that has already been replaced. What should the processor use to identify the exact version?
- Use the bucket/key/version or sequencer context in an idempotent indexing operation.
- Use S3 Inventory reports as the scalable object listing source.
- Send the object event to a queue and process large jobs using appropriately long-running workers.
- Read the version ID from supported event context and retrieve that version from a versioned bucket.
Explanation
Correct Answer
D:Object version identifiers prevent a delayed consumer from accidentally processing a newer object. Overwrite a test key before consumption and inspect which version is read.
Incorrect Answers
A:S3 event notifications can be delivered at least once; consumers should deduplicate effects. Read the version ID from supported event context and retrieve that version from a versioned bucket. Overwrite a test key before consumption and inspect which version is read.
B:Inventory provides periodic flat-file metadata at scale; event notifications are not a full snapshot. Read the version ID from supported event context and retrieve that version from a versioned bucket. Overwrite a test key before consumption and inspect which version is read.
C:Decoupled workers such as ECS tasks can handle work that exceeds Lambda's execution limit. Read the version ID from supported event context and retrieve that version from a versioned bucket. Overwrite a test key before consumption and inspect which version is read.