Question 1: EBS Volumes and Availability Zones

Question:

You have just terminated an EC2 instance in us-east-1a, and its attached EBS volume is now available. Your teammate tries to attach it to an EC2 instance in us-east-1b, but he can't. What is a possible cause for this?

Options:

⚪ He's missing IAM permissions

⚪ EBS volumes are locked to an AWS Region

🔘 EBS volumes are locked to an Availability Zone ✅ (Correct Answer)

💡 Explanation:

• EBS volumes are tied to a specific Availability Zone (AZ) and cannot be directly attached to an instance in another AZ.
• You can migrate an EBS volume between AZs by creating an EBS snapshot and restoring it in the target AZ.

Question 2: EC2 Root Volume Deletion Behavior

Question:

You have launched an EC2 instance with two EBS volumes: a Root volume and another EBS volume to store data. A month later, you plan to terminate the EC2 instance. What is the default behavior regarding these volumes?

Options:

⚪ Both the root volume type and the EBS volume type will be deleted

🔘 The Root volume type will be deleted and the EBS volume type will not be deleted ✅ (Correct Answer)

⚪ The root volume type will not be deleted and the EBS volume type will be deleted

⚪ Both the root volume type and the EBS volume type will not be deleted

💡 Explanation: