5 collocation exercises on cloud storage operations.
0 / 5 completed
1 / 5
To create object storage, you ___ a bucket.
You provision a bucket — creating and configuring an object-storage container such as an S3 bucket. Provision collocates broadly with cloud resources (provision a server, provision a database). Raise up, spawn off and erect out are not used. Provisioning typically includes setting the region, access policies and naming, and is often done declaratively through infrastructure-as-code tools like Terraform.
2 / 5
To attach block storage to an instance, you ___ a volume.
You mount a volume — attaching a block-storage device to a server so the operating system can read and write to it at a path. Mount is the fixed term (you also unmount it). Clip up, fix on and latch out are wrong. Mounting makes the volume's filesystem available; in the cloud you first attach the volume to the instance, then mount it inside the OS.
3 / 5
To capture a point-in-time copy, you ___ the volume.
You snapshot a volume — taking a point-in-time copy you can restore from later. Snapshot works as both noun and verb (take a snapshot, snapshot the disk). Photo off, capture up and freeze out are not idiomatic. Snapshots underpin backup and disaster-recovery strategies, letting you roll storage back to a known good state or clone it to spin up new instances quickly.
4 / 5
To move cold data to cheaper storage, you ___ it.
You archive data — moving infrequently accessed data to a low-cost tier such as Glacier or Coldline. The verb archive collocates with data, logs and files. Shelf up, store off and stash out are not standard. Archiving trades retrieval speed for much lower storage cost, which is ideal for compliance data or old logs you must keep but rarely read.
5 / 5
To automate data tiering, you ___ a lifecycle policy.
You set a lifecycle policy — rules that automatically transition or delete objects based on age. The collocation is set a policy (you also apply or configure one). Lay up, place off and fix out are wrong. Lifecycle policies move objects from hot to cold tiers and eventually expire them, controlling storage cost without manual intervention as data ages over weeks or months.