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 an auto subnet mode in Google Cloud VPC?
Auto subnet mode automatically creates one subnet in each region with a predefined IP range. This makes setup quick and simple without manual subnet configuration.
Click to reveal answer
beginner
What does custom subnet mode allow you to do in Google Cloud VPC?
Custom subnet mode lets you create and manage your own subnets manually. You choose the regions and IP ranges, giving you full control over network layout.
Click to reveal answer
intermediate
How does auto subnet mode affect network control and flexibility?
Auto subnet mode offers less control because subnets and IP ranges are predefined. It is easier but less flexible for complex network needs.
Click to reveal answer
intermediate
Why might you choose custom subnet mode over auto mode?
You choose custom mode to tailor your network to specific needs, such as custom IP ranges, regional subnet placement, or advanced security setups.
Click to reveal answer
advanced
Can you switch a VPC from auto subnet mode to custom subnet mode after creation?
No, you cannot switch modes after creation. You must create a new VPC with the desired subnet mode and migrate resources if needed.
Click to reveal answer
What happens when you create a VPC in auto subnet mode?
AYou must manually create all subnets.
BSubnets are automatically created in all regions with default IP ranges.
CNo subnets are created until you add them.
DOnly one subnet is created in a single region.
✗ Incorrect
Auto subnet mode automatically creates subnets in all regions with predefined IP ranges.
Which subnet mode gives you full control over subnet IP ranges and regions?
ACustom subnet mode
BHybrid subnet mode
CAuto subnet mode
DDefault subnet mode
✗ Incorrect
Custom subnet mode lets you manually create subnets with your chosen IP ranges and regions.
Can you change a VPC from auto subnet mode to custom subnet mode after it is created?
AYes, but only within 24 hours
BYes, but only with command line tools
CYes, anytime via the console
DNo, you must create a new VPC
✗ Incorrect
You cannot change subnet mode after creation; a new VPC must be created.
Which subnet mode is best for quick setup without detailed network planning?
ACustom subnet mode
BManual subnet mode
CAuto subnet mode
DHybrid subnet mode
✗ Incorrect
Auto subnet mode is designed for quick setup with automatic subnet creation.
What is a key disadvantage of auto subnet mode?
ALess flexibility in subnet placement and IP ranges
BNo subnets are created automatically
CCannot connect to other networks
DRequires manual IP range configuration
✗ Incorrect
Auto subnet mode limits flexibility because subnets and IP ranges are predefined.
Explain the difference between auto subnet mode and custom subnet mode in Google Cloud VPC.
Think about how much control you have over subnet creation and IP ranges.
You got /5 concepts.
Describe a scenario where choosing custom subnet mode is better than auto subnet mode.
Consider when you want to design your network carefully.
You got /4 concepts.
Practice
(1/5)
1. What happens when you create a VPC network in auto subnet mode in GCP?
easy
A. Subnets are automatically created in all regions with predefined IP ranges.
B. No subnets are created; you must create them manually.
C. Only one subnet is created in the default region.
D. Subnets are created but without any IP ranges assigned.
Solution
Step 1: Understand auto subnet mode behavior
In auto mode, GCP automatically creates subnets in every region with default IP ranges.
Step 2: Compare with other modes
Unlike custom mode, auto mode does not require manual subnet creation or IP range assignment.
Final Answer:
Subnets are automatically created in all regions with predefined IP ranges. -> Option A
Quick Check:
Auto mode = automatic subnet creation [OK]
Hint: Auto mode means automatic subnets in all regions [OK]
Common Mistakes:
Thinking auto mode requires manual subnet creation
Assuming only one subnet is created
Believing subnets have no IP ranges assigned
2. Which of the following is the correct way to create a custom subnet in GCP using gcloud CLI?
easy
A. gcloud compute networks subnets create my-network --subnet-mode=custom
B. gcloud compute networks create my-network --subnet-mode=auto
C. gcloud compute networks create my-subnet --range=10.0.0.0/24
D. gcloud compute networks subnets create my-subnet --network=my-network --range=10.0.0.0/24
Solution
Step 1: Identify command to create a subnet
The command to create a subnet is gcloud compute networks subnets create with network and IP range specified.
Step 2: Check option correctness
gcloud compute networks subnets create my-subnet --network=my-network --range=10.0.0.0/24 correctly uses the subnet creation command with network and IP range parameters.
Subnet creation uses 'networks subnets create' with range [OK]
Hint: Use 'networks subnets create' with --range for custom subnets [OK]
Common Mistakes:
Using 'networks create' to create subnets
Missing the --range parameter for IP range
Confusing network and subnet names
3. Given a VPC network in custom subnet mode with two subnets: subnet-a: 10.1.0.0/16 subnet-b: 10.2.0.0/16 What happens if you try to create a third subnet with IP range 10.1.128.0/17?
medium
A. The subnet is created successfully without issues.
B. The subnet is created but traffic is blocked between subnets.
C. Creation fails due to overlapping IP ranges with subnet-a.
D. The subnet is created but assigned a different IP range automatically.
Solution
Step 1: Check IP range overlap
Subnet-a uses 10.1.0.0/16 which covers 10.1.0.0 to 10.1.255.255. The new subnet 10.1.128.0/17 overlaps this range.
Step 2: Understand subnet creation rules
GCP does not allow overlapping IP ranges in subnets within the same VPC network.
Final Answer:
Creation fails due to overlapping IP ranges with subnet-a. -> Option C
Quick Check:
Overlapping IP ranges cause subnet creation failure [OK]
Hint: Check IP ranges for overlap before subnet creation [OK]
Common Mistakes:
Assuming subnets can overlap IP ranges
Thinking GCP auto-adjusts overlapping ranges
Believing traffic is blocked but subnet created
4. You created a VPC network in custom subnet mode but forgot to create any subnets. What is the result when you try to deploy a VM instance in this network?
medium
A. The VM instance deploys successfully with an automatic subnet created.
B. The VM deployment fails because no subnet exists in the network.
C. The VM deploys but without an internal IP address.
D. The VM deploys but is not reachable from other resources.
In custom mode, subnets must be created manually before deploying resources.
Step 2: Check VM deployment dependency
VMs require a subnet to get an IP address; without subnets, deployment fails.
Final Answer:
The VM deployment fails because no subnet exists in the network. -> Option B
Quick Check:
Custom mode needs subnets before VM deployment [OK]
Hint: No subnet means VM deployment fails in custom mode [OK]
Common Mistakes:
Assuming auto subnet creation in custom mode
Thinking VM can deploy without internal IP
Believing VM deploys but is unreachable
5. You want to create a VPC network that spans multiple regions with subnets having specific IP ranges you control. Which subnet mode should you choose and why?
hard
A. Custom mode, because it lets you manually create subnets with specific IP ranges in each region.
B. Custom mode, because it automatically creates subnets in all regions with default IP ranges.
C. Auto mode, because it allows you to edit IP ranges after subnet creation.
D. Auto mode, because it creates subnets automatically with your chosen IP ranges.
Solution
Step 1: Identify requirement for specific IP ranges
You want control over IP ranges, so automatic default ranges won't work.
Step 2: Choose subnet mode matching control needs
Custom mode allows manual subnet creation with chosen IP ranges per region.
Step 3: Eliminate incorrect options
Auto mode does not allow choosing IP ranges; it creates default subnets automatically.
Final Answer:
Custom mode, because it lets you manually create subnets with specific IP ranges in each region. -> Option A
Quick Check:
Custom mode = manual subnet creation with chosen IP ranges [OK]
Hint: Custom mode for manual subnets with specific IP ranges [OK]
Common Mistakes:
Confusing auto mode as allowing custom IP ranges
Thinking auto mode subnets can be edited after creation