CLF-C02 Cloud Concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Choose AMI -> Choose Instance Type -> Configure Instance Details -> Add Storage -> Configure Security Group -> Review and Launch

  Why this is correct

  The AWS EC2 launch wizard proceeds in a fixed dependency order: the AMI defines the operating system, root volume template, and architecture; the instance type then provides the CPU, memory, and network capacity compatible with that AMI. Configure Instance Details sets the VPC, subnet, IAM role, and user data, while Add Storage attaches additional volumes. Security Group configuration comes last because firewall rules are associated with the ENI in the chosen subnet and may need to reference the storage and network settings just defined. Review and Launch finalizes the parameters and generates a key pair.

• ✗

  Choose AMI -> Configure Security Group -> Choose Instance Type -> Add Storage -> Configure Instance Details -> Review and Launch

  Why it's wrong here

  This order places the security group before the instance type and the instance details, which breaks the wizard's dependency chain. At the point of configuring the security group, the wizard has not yet captured the VPC and subnet that determine where the ENI is attached; a security group can only be associated with an ENI in a specific VPC, so those details are required first. Additionally, the instance type selection influences the number of network interfaces and IP addresses, which affects how the security group rules will apply. Therefore the correct position for the security group is after storage and instance details.

• ✗

  Choose Instance Type -> Choose AMI -> Configure Instance Details -> Add Storage -> Configure Security Group -> Review and Launch

  Why it's wrong here

  Selecting the instance type before the AMI is invalid because the AMI's architecture—x86_64, arm64, or i86—and its virtualization type directly constrain which instance families and sizes are compatible. For example, a Graviton-based instance type (like a4g or c6g) cannot boot an x86_64 AMI, and choosing a type first risks selecting one that cannot run the AMI's guest OS. The wizard therefore forces AMI selection first so that the instance type list can be filtered to compatible options. Additionally, the AMI may have minimum resource requirements, such as a baseline RAM amount, which are considered only after choosing the AMI.

• ✗

  Choose AMI -> Choose Instance Type -> Configure Security Group -> Add Storage -> Configure Instance Details -> Review and Launch

  Why it's wrong here

  In this variant the security group is configured after the instance type but before storage and instance details, which is still incorrect because the network context has not been established. The Configure Instance Details step is where you select the VPC and subnet; since each security group is scoped to a VPC, the wizard must know that VPC before you can pick a group. Add Storage also informs the security group guidance, because additional volumes that are to be accessed at launch (e.g., via a shared filesystem) may require specific inbound rules. Thus the security group step belongs at position five, after storage and details.

Go deeper

Related to this question