A county must harden durability of land-record objects in Amazon S3 against accidental deletes and Regional loss. Which combination best fits?

Enabling Amazon S3 versioning with MFA Delete and cross-Region replication hardens durability of county land-record objects against accidental deletes and Regional loss. Versioning works because overwrite and delete operations retain prior object versions instead of irreversibly discarding the only copy of a deed image or title PDF. MFA Delete raises the bar for permanently removing versioned objects, reducing the chance that a compromised or mistaken identity quietly purges history. Cross-Region replication copies objects to another Region so a Regional event or bucket-level disaster in the primary location does not erase the county’s system of record. Together they address both accidental deletion and geographic durability for civic records.

Disabling versioning, turning off replication, and granting every clerk s3:DeleteObject without MFA fails by concept because it maximizes blast radius for human error and insider or stolen-credential deletes. Storing land records only on a single EBS volume attached to one EC2 instance in one AZ fails because that volume is AZ-scoped, snapshot-dependent for durability, and a poor system of record compared with S3’s designed durability features. Using Amazon ElastiCache alone as the system of record for land titles fails because caches are ephemeral performance layers, not durable authoritative stores for legal land documents.

Exam caveat: versioning increases storage cost and still needs lifecycle rules; MFA Delete has account/root operational implications that must be planned. Operational check: enable versioning and CRR on the land-records bucket, restrict delete permissions, test restore of a prior version after a soft-delete drill, and confirm replica objects appear in the destination Region bucket.