AWS EC2 Basics: Launching Your First Instance Quiz Quiz

Enhance your foundational understanding of launching virtual machines on AWS EC2. This quiz covers key steps, best practices, and terminology essential for anyone starting with cloud-based compute instances.

  1. Selecting an AMI

    Which option is primarily chosen when launching a new EC2 instance to define the operating system and initial setup?

    1. Active Measured Instance
    2. Application Management Interface
    3. Access Management Identity
    4. Amazon Machine Image (AMI)

    Explanation: The Amazon Machine Image (AMI) provides the operating system and software configuration to your EC2 instance. The other options are incorrect: 'Application Management Interface' and 'Access Management Identity' are not related to instance setups, while 'Active Measured Instance' is a misleading term with no connection to the process.

  2. Instance Types

    When choosing an instance type for your EC2 instance, what are you mainly determining?

    1. The hardware resources allocated, such as CPU and memory
    2. The pricing model for data transfer
    3. The backup schedule frequency
    4. The email notification settings

    Explanation: Instance type selection determines how much CPU, memory, storage, and network capacity your EC2 instance receives. Email notifications, pricing models for data transfer, and backup schedules are not set by instance types; those are managed elsewhere.

  3. Configuring Key Pairs

    Why is it important to create or select a key pair when launching an EC2 instance?

    1. To add extra disk storage
    2. To boost your instance’s processing speed
    3. To enable secure SSH or RDP access to the instance
    4. To change the operating system mid-launch

    Explanation: A key pair is crucial because it provides the cryptographic credentials needed to log into your instance securely via SSH or RDP. It does not affect processing speed or storage, nor does it allow operating system changes during launch.

  4. Security Groups Purpose

    What function does a security group serve when launching an EC2 instance?

    1. It changes the root password remotely
    2. It adjusts CPU and RAM quotas
    3. It manages user account permissions
    4. It controls inbound and outbound network traffic

    Explanation: Security groups act as a virtual firewall, regulating which network communications are allowed into and out of your instance. Managing user permissions, hardware quotas, or root passwords are not functions of security groups.

  5. Default VPC Selection

    If you do not specify a VPC when launching your first EC2 instance, where is it placed by default?

    1. Within a private isolated subnet only
    2. In the default Virtual Private Cloud (VPC)
    3. In a randomly selected data center
    4. On a physical on-premises server

    Explanation: If you don't select a VPC, the instance is automatically launched into the default Virtual Private Cloud. The other options do not apply: instances are not launched on physical servers by default, they're not randomly data-centered, and they're not always placed in an isolated subnet unless specified.

  6. EBS Volume Attachment

    What is the purpose of selecting an Elastic Block Store (EBS) volume when launching an EC2 instance?

    1. To increase internet bandwidth limits
    2. To change the instance's public IP automatically
    3. To assign a custom CPU architecture
    4. To provide persistent storage for instance data

    Explanation: EBS volumes serve as persistent storage so that your data is retained even if the instance stops or reboots. They do not affect internet bandwidth, IP addresses, or CPU architecture; those are managed differently.

  7. Tagging EC2 Instances

    Why might you assign tags to your EC2 instance during launch, such as Name: WebServer1?

    1. To prevent the instance from being deleted
    2. To organize resources with metadata for identification and management
    3. To install antivirus software automatically
    4. To set automatic shutdown times

    Explanation: Tags help you categorize and manage your instances by adding metadata such as names or purposes. Tags do not directly control antivirus installation, automation scripts, or deletion protection, though they can assist with resource organization for future actions.

  8. Terminating vs. Stopping Instance

    What is the difference between stopping and terminating an EC2 instance you launched?

    1. Stopping increases the CPU power
    2. Stopping keeps the instance for later use; terminating deletes it permanently
    3. Terminating automatically emails you a backup
    4. Both actions delete data stored on instance storage

    Explanation: Stopping an instance simply shuts it down and you can restart it later, while terminating permanently deletes the instance and associated resources. Stopping does not increase CPU capacity, nor does terminating send you a backup automatically. Data deletion applies only to certain types of storage.

  9. Checking Instance Status

    Where can you regularly monitor the status of your newly launched EC2 instance?

    1. With a physical server monitor
    2. Via direct mobile SMS updates only
    3. In your local file explorer
    4. On the EC2 Instances dashboard page

    Explanation: The EC2 Instances dashboard page provides real-time status, health checks, and metrics. Local file explorers and physical monitors cannot access this information, while SMS updates are optional and not the primary method.

  10. Launch Wizard Assistance

    How does the EC2 Launch Wizard assist users during the process of launching their first instance?

    1. By auto-deleting previous instances
    2. By generating hard-coded security credentials only
    3. By locking you out of further configuration changes
    4. By providing a step-by-step guide that covers all essential configuration options

    Explanation: The Launch Wizard simplifies the instance creation process by guiding users through each setup phase and explaining options along the way. It does not delete previous instances, restrict credentials, or block future configuration changes; instead, it helps new users avoid misconfiguration.