Bird
Raised Fist0
AWScloud~5 mins

Creating a custom VPC in AWS - Quick Revision & Summary

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Recall & Review
beginner
What is a VPC in AWS?
A VPC (Virtual Private Cloud) is like your own private network in the cloud where you can launch AWS resources securely and control network settings.
Click to reveal answer
beginner
Why create a custom VPC instead of using the default one?
Creating a custom VPC lets you control IP ranges, subnets, route tables, and security settings tailored to your needs, unlike the default VPC which has preset configurations.
Click to reveal answer
beginner
What is a subnet in a VPC?
A subnet is a smaller network inside your VPC that divides the IP address range into segments, helping organize and isolate resources.
Click to reveal answer
beginner
What is the purpose of an Internet Gateway in a VPC?
An Internet Gateway allows resources in your VPC to connect to the internet and receive traffic from it.
Click to reveal answer
intermediate
How do route tables work in a custom VPC?
Route tables control where network traffic is directed within your VPC and to outside networks, like the internet or other VPCs.
Click to reveal answer
What is the first step when creating a custom VPC in AWS?
ACreate an Internet Gateway
BDefine the IP address range using CIDR notation
CLaunch an EC2 instance
DSet up security groups
Which AWS component allows your VPC to access the internet?
AInternet Gateway
BNAT Gateway
CRoute Table
DSecurity Group
What does a subnet do inside a VPC?
ADivides the VPC IP range into smaller networks
BManages user permissions
CStores data
DControls internet access
Which of these is NOT a reason to create a custom VPC?
AControl IP address range
BCustomize network security
CAutomatically launch EC2 instances
DDefine subnets and route tables
What controls the flow of traffic between subnets and outside networks in a VPC?
AElastic IPs
BNetwork ACLs
CSecurity Groups
DRoute Tables
Explain the key components you need to set up when creating a custom VPC in AWS.
Think about the network parts that let your cloud resources communicate safely.
You got /5 concepts.
    Describe how a custom VPC helps improve security and control compared to the default VPC.
    Consider how having your own network setup can protect and organize your cloud resources.
    You got /4 concepts.

      Practice

      (1/5)
      1. What is the main purpose of creating a custom VPC in AWS?
      easy
      A. To automatically create public IP addresses for all instances
      B. To connect your AWS account to social media platforms
      C. To enable AWS to manage your network without your input
      D. To have a private network with a specific IP range for your resources

      Solution

      1. Step 1: Understand what a VPC is

        A VPC is a private network in AWS where you control IP ranges and network settings.

      2. Step 2: Identify the purpose of a custom VPC

        Creating a custom VPC lets you choose your IP range and control network setup for your resources.

      3. Final Answer:

        To have a private network with a specific IP range for your resources -> Option D

      4. Quick Check:

        Custom VPC = Private network with chosen IP range [OK]
      Hint: Custom VPC means your own private network in AWS [OK]
      Common Mistakes:
      • Thinking VPC automatically assigns public IPs
      • Believing AWS manages the network without user control
      • Confusing VPC with external internet connections
      2. Which of the following is the correct way to specify the CIDR block when creating a custom VPC?
      easy
      A. 192.168.1.256/24
      B. 255.255.255.0
      C. 10.0.0.0/16
      D. 10.0.0.0/33

      Solution

      1. Step 1: Understand CIDR notation

        CIDR block defines IP range with format like x.x.x.x/y where y is between 0 and 32.

      2. Step 2: Check each option for validity

        10.0.0.0/16 is valid CIDR (10.0.0.0/16). 255.255.255.0 is a subnet mask, not CIDR. 192.168.1.256/24 has invalid IP (256). 10.0.0.0/33 has invalid prefix length (33).

      3. Final Answer:

        10.0.0.0/16 -> Option C

      4. Quick Check:

        CIDR block format = x.x.x.x/y with y ≤ 32 [OK]
      Hint: CIDR uses / and prefix ≤ 32, IP parts ≤ 255 [OK]
      Common Mistakes:
      • Using subnet mask instead of CIDR
      • Using invalid IP numbers like 256
      • Using prefix length greater than 32
      3. Given this AWS CLI command to create a VPC:
      aws ec2 create-vpc --cidr-block 10.1.0.0/16 --tag-specifications 'ResourceType=vpc,Tags=[{Key=Name,Value=MyVPC}]'

      What will be the result?
      medium
      A. A VPC with CIDR 10.1.0.0/16 and a Name tag 'MyVPC' will be created
      B. The command will fail due to incorrect tag syntax
      C. A VPC with default CIDR will be created ignoring the specified CIDR
      D. A subnet will be created instead of a VPC

      Solution

      1. Step 1: Analyze the CLI command structure

        The command uses 'create-vpc' with a valid CIDR block and correct tag specification syntax.

      2. Step 2: Understand the effect of the command

        This creates a VPC with the given CIDR and applies the Name tag 'MyVPC' to it.

      3. Final Answer:

        A VPC with CIDR 10.1.0.0/16 and a Name tag 'MyVPC' will be created -> Option A

      4. Quick Check:

        Valid CLI command creates VPC with CIDR and tags [OK]
      Hint: Tags use 'ResourceType' and 'Tags' in CLI [OK]
      Common Mistakes:
      • Incorrect tag syntax causing command failure
      • Confusing subnet creation with VPC creation
      • Ignoring the CIDR block parameter
      4. You created a custom VPC but forgot to enable DNS hostnames. What is the best way to fix this?
      medium
      A. Modify the VPC attribute to enable DNS hostnames using AWS console or CLI
      B. Delete the VPC and create a new one with DNS hostnames enabled
      C. Create a new subnet with DNS hostnames enabled
      D. DNS hostnames cannot be enabled after VPC creation

      Solution

      1. Step 1: Understand DNS hostnames setting in VPC

        DNS hostnames is a VPC attribute that can be enabled or disabled after creation.

      2. Step 2: Identify how to enable DNS hostnames

        You can modify the VPC attribute via AWS console or CLI without deleting the VPC.

      3. Final Answer:

        Modify the VPC attribute to enable DNS hostnames using AWS console or CLI -> Option A

      4. Quick Check:

        DNS hostnames can be enabled post-creation [OK]
      Hint: VPC attributes can be changed anytime without deletion [OK]
      Common Mistakes:
      • Thinking you must delete and recreate the VPC
      • Trying to enable DNS hostnames on a subnet instead of VPC
      • Believing DNS hostnames are enabled by default always
      5. You want to create a custom VPC with two public subnets in different availability zones and enable DNS support and hostnames. Which sequence of steps is correct?
      hard
      A. Attach internet gateway first, then create VPC and subnets, DNS settings are automatic
      B. Create VPC with CIDR, enable DNS support and hostnames, create two public subnets in different AZs, attach internet gateway
      C. Create VPC with CIDR, create subnets, attach internet gateway, then enable DNS support and hostnames
      D. Create two subnets first, then create VPC, enable DNS hostnames, attach internet gateway

      Solution

      1. Step 1: Create the VPC with chosen CIDR block

        The VPC must exist before creating subnets or attaching gateways.

      2. Step 2: Enable DNS support and hostnames on the VPC

        This ensures resources inside can resolve names properly.

      3. Step 3: Create two public subnets in different availability zones

        Subnets must be inside the VPC and in separate AZs for high availability.

      4. Step 4: Attach an internet gateway to allow internet access

        This makes the subnets public.

      5. Final Answer:

        Create VPC with CIDR, enable DNS support and hostnames, create two public subnets in different AZs, attach internet gateway -> Option B

      6. Quick Check:

        VPC -> DNS -> Subnets -> Internet Gateway [OK]
      Hint: VPC first, then DNS settings, subnets, internet gateway [OK]
      Common Mistakes:
      • Creating subnets before the VPC exists
      • Attaching internet gateway before VPC creation
      • Assuming DNS settings are automatic