Elastic Block Store Volumes u0026 Snapshots Essentials Quiz Quiz

Challenge your understanding of Elastic Block Store (EBS) volumes and snapshots with this easy quiz. Explore key concepts, use cases, backup strategies, and essential features of EBS storage to reinforce your foundational knowledge in cloud computing.

1. EBS Volume Attachment

   Which statement is true about attaching Elastic Block Store (EBS) volumes to virtual servers in the same availability zone?

   1. EBS volumes are attached over the public internet.
   2. An EBS volume can only be attached to one running server in its availability zone at a time.
   3. A single EBS volume can be attached to multiple servers at once within the same zone.
   4. EBS volumes can be shared across all zones by default.

   Explanation: EBS volumes are designed to attach to only one running server within the same availability zone at a time, allowing block-level storage for that specific server. They cannot be attached to multiple servers simultaneously, which would risk data corruption. EBS volumes are not inherently shared across all zones, and they use secure internal networks rather than the public internet for attachment. Option A and C are incorrect due to sharing limitations, and option D misrepresents how EBS is accessed.

2. Durability of Snapshots

   When you create a snapshot of an EBS volume, where is the snapshot stored for durability and long-term backup?

   1. In the same availability zone as the EBS volume
   2. On the same server as the EBS volume
   3. In object storage for high durability across multiple locations
   4. Only on the local machine where the snapshot was created

   Explanation: Snapshots are stored in object storage designed for durability and replicated across multiple physical locations. This protects data from failure in a single zone. They are not saved on the original server or local machine, as that would risk data loss. Option B incorrectly limits storage durability to only one zone. Storing only locally, noted in option D, would not ensure backup or disaster recovery.

3. Deleting Volumes vs. Snapshots

   What happens when you delete an EBS volume that has existing snapshots?

   1. Any attached server is upgraded automatically.
   2. Existing snapshots remain intact even after the volume is deleted.
   3. The server using the volume shuts down instantly.
   4. All snapshots of the volume are also deleted automatically.

   Explanation: Deleting an EBS volume does not affect its pre-existing snapshots. The snapshots are stored independently and can be used to restore the volume later if needed. Option A is incorrect because snapshots are not deleted with the volume. Option C is not standard behavior as deleting storage does not force a shutdown, and option D refers to unrelated functionality.

4. Snapshot Use Case

   Which scenario most appropriately uses EBS snapshots?

   1. Increasing the real-time throughput of EBS volumes
   2. Storing long-term logs on frequently accessed servers
   3. Backing up the state of an EBS volume to restore it if needed
   4. Reducing server CPU utilization during busy periods

   Explanation: Snapshots are primarily used for backing up EBS volumes so you can restore them later if needed. They are not intended for storing logs (option A), nor do they directly affect throughput (option B). Option D misrepresents the purpose, as snapshots do not relate to CPU utilization.

5. EBS Volume Types

   Which EBS volume type is optimized for high sequential read and write operations, such as big data analytics?

   1. General Purpose SSD
   2. Bursting SSD
   3. Throughput Optimized HDD
   4. Cold HDD

   Explanation: Throughput Optimized HDD volumes are specifically designed for workloads requiring high sequential read and write throughput, such as analytics or log processing. General Purpose SSD is suitable for everyday workloads but not optimized for high throughput. Cold HDD serves infrequent access, and Bursting SSD is not a standard type. The other options are less suitable for big sequential operations.

6. Creating a Volume from a Snapshot

   If you need to create a new EBS volume with data from an existing snapshot, what is the correct procedure?

   1. Delete the volume before using the snapshot
   2. Upload the snapshot to the server’s local disk first
   3. Attach the snapshot directly to a running server as a block device
   4. Restore the EBS snapshot to create a new volume in any available zone

   Explanation: You use a snapshot to create a new EBS volume in a compatible availability zone, restoring the data from that snapshot. Snapshots cannot be attached directly as block devices (option B), nor do you have to upload them to local disks (option C). Deleting the original volume, as stated in D, is not necessary or recommended to use the snapshot.

7. Modifying EBS Volume Size

   Which statement correctly describes how to increase the storage size of an EBS volume?

   1. You must delete and re-create the volume to resize it.
   2. Resize only by merging two volumes together.
   3. EBS volumes cannot have their size changed after creation.
   4. Increase the volume size, then expand the file system on the server.

   Explanation: You can increase the size of an EBS volume through configuration, then expand the related file system within your server to utilize the new space. It is unnecessary to delete and re-create the volume (option C), nor is merging volumes (option D) a supported resizing strategy. Option A is outdated as modern volumes are resizable.

8. Snapshot Characteristics

   Which statement accurately describes the characteristics of an EBS snapshot?

   1. Snapshots cannot be restored to a new volume.
   2. Snapshots are only available for SSD volumes, not HDD types.
   3. Snapshots are incremental, saving only changed data since the last snapshot.
   4. Each snapshot is a complete independent copy of all data, consuming space equal to the full volume every time.

   Explanation: EBS snapshots are incremental which means each subsequent snapshot only stores the data that changed from a previous snapshot. As a result, they are space-efficient. Option A is incorrect as snapshots do not always copy the whole volume every time, and option C incorrectly restricts them to SSD volumes only. Option D is false, as restoring to a new volume is a primary purpose of snapshots.

9. Volume Encryption

   If you create a new encrypted EBS volume, how is data security maintained during read and write operations?

   1. Only the initial snapshot is encrypted; subsequent operations are unprotected.
   2. Encryption is handled at the server application level by default.
   3. Encryption happens only when the volume is detached.
   4. Data is encrypted transparently during every read and write operation.

   Explanation: Encrypted EBS volumes provide transparent encryption, meaning all data is automatically encrypted or decrypted on every read and write, without user action. Option A refers to application-level encryption, which is not default EBS behavior. Option C is incorrect because encryption applies to all operations, and D is misleading as encryption is ongoing, not limited to detachment events.

10. Availability Zone Limitations

    Why must EBS volumes and the servers they attach to reside in the same availability zone?

    1. EBS volumes must be attached through the public internet
    2. Since volumes automatically send data to servers in every region
    3. Due to network latency and to maintain low-latency, high-performance storage connections
    4. Because EBS volumes are instance-specific and cannot be shared at all

    Explanation: EBS volumes are bound to a particular availability zone because attaching them to servers in the same zone ensures low-latency and high-performance connectivity. They can be re-attached or cloned to other zones if needed, so option A is too strict. Option C is incorrect as EBS volumes do not broadcast data everywhere, and D is wrong as EBS does not use the public internet for such connections.