DOP-C02 — Frequently Asked Questions

E affects retention, not query logic. It keeps recent data in memory but doesn't reduce the I/O cost of reading/write structure like A and D do.

No. Timestream can push down filters to specific measures within a multi-measure record, scanning only the relevant data rather than the whole record.

Enhanced Fan-Out provides dedicated throughput per consumer, removing contention and reducing latency caused by shared bandwidth and polling intervals.

No, Reserved Concurrency limits maximum concurrent executions. It protects against throttling but does not increase processing speed or reduce backlog latency.

Unidirectional CRR only replicates Primary to Secondary. If the app fails over to Secondary and writes data, that data is not sent back to Primary, causing loss upon return.

Yes, Managed Replication (MRP) supports two-way rules. It automates the creation of replication rules between buckets to keep them in sync bidirectionally.

No, CodeDeploy processes all defined file mappings in the appspec.yml. If a file matches multiple rules, it will be deployed to all specified destinations.

Mapping the root directory '/' to a destination copies all files and folders from the source root to that destination, including any specific files already targeted by other rules.

Option A uses the legacy CloudWatch Agent and Fluent Bit. AWS now recommends AWS Distro for OpenTelemetry (ADOT) for EKS as it provides a unified, standardized way to collect metrics and logs.

You use a CloudWatch Metric Log Filter Alarm. This type of alarm monitors log groups for specific patterns (like error messages) in the Autoscaler's deployment logs.

No, VPC endpoints do not support ECR Public repositories. You must use a pull-through cache rule to cache public images in a private repository.

Option A requires managing a separate CodeBuild project for each image, creating high operational overhead. The pull-through cache rule automates this efficiently.