A township must place three workloads: a relational permitting database, a CMS that needs a shared POSIX file tree for web nodes, and long-term backups plus media archives. Which storage-type mapping is correct?
Select an answer to reveal the explanation.
Short Explanation
Match the tool to the job like matching keys to locks: databases want block, shared CMS trees want file, and backups/media love object. That trio—block, file, object—keeps each workload on the storage shape it expects. Stuffing a DB into pure object, parking CMS on Glacier, or one multi-attach volume for everything fights the access patterns.
Full Explanation
High-performing storage selection maps workload characteristics to storage types: block storage (for example EBS) for databases needing low-latency random I/O; file storage (EFS/FSx) for shared POSIX access across CMS web nodes; and object storage (S3) for durable backups and media at scale. Incorrect mappings create performance, sharing, or durability gaps and are common associate-level distractors.