AWS VPC Subnets

Question 1

What is the main purpose of creating subnets within an AWS VPC?

A) To organize instances into groups for billing purposes
B) To separate resources for security and routing purposes
C) To define the VPC’s IP address range
D) To allocate separate AWS accounts within the VPC

Answer 1

Answer: B) To separate resources for security and routing purposes

Explanation: Subnets in an AWS VPC are used to logically separate resources, enabling fine-grained control over security and routing.

Question 2

Can instances in different subnets within the same VPC communicate with each other by default?

A) Yes, they can always communicate without any additional configuration.
B) No, communication between subnets requires setting up VPC peering.
C) It depends on the route table and security group settings.
D) Only instances in public subnets can communicate within the VPC.

Answer 2

Answer: C) It depends on the route table and security group settings.

Explanation: By default, instances in different subnets within the same VPC can communicate if the route tables and security groups allow it. Configuration may be needed to enable or restrict communication.