Before tax-day traffic, a city anticipates a large spike in concurrent Lambda executions for filing helpers. Architects worry reliability will fail when the account hits its concurrency quota. What should they do first?
Select an answer to reveal the explanation.
Short Explanation
Quotas are speed limits, not suggestions. Raise the Lambda concurrency ceiling before tax day and prove it with a load test so the filing helpers don’t get throttled mid-rush.
Full Explanation
Cross-Region replication for critical citizen documents must include both data movement and integrity verification, not only a checkbox that replication is enabled. Configuring S3 Cross-Region Replication with appropriate replication metrics, versioning, and periodic restore or checksum validation proves documents exist and are readable in the destination Region. Enabling CRR but never validating destination objects leaves silent replication failures undetected. Replicating only to the same Region does not address Region-level loss. Deleting destination copies nightly to save storage defeats continuity. Exam caveat: CRR is asynchronous—RPO is not zero—and delete markers, encryption keys, and ownership settings can block replication if misconfigured. Operational check: upload a marker object, confirm replication metrics and destination presence, restore or read it from the DR Region, and alert on replication latency or failure metrics. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure.