Which of the following statements are true about route tables in a VPC?

Route tables are a fundamental component of a Virtual Private Cloud (VPC) in AWS, and understanding their characteristics is crucial for effective network management.

Every subnet within a VPC must be associated with a route table to define the routes for outbound traffic from the subnet. If a subnet is not explicitly associated with a route table, it will use the main route table that is automatically created with the VPC. This association ensures that instances within the subnet can route traffic to the appropriate destinations, whether internal to the VPC or external to the internet.

Upon the creation of a VPC, it comes with a default route table. This default route table contains a local route that allows communication between all instances within the VPC. The presence of this default route table helps streamline initial setup and ensures that there is at least a minimal routing mechanism available immediately after VPC creation.

Furthermore, route tables can indeed be shared among multiple subnets. This allows for simplified management of routes since multiple subnets can leverage the same routing rules. By associating multiple subnets with a single route table, you can ensure that they share the same outbound traffic routing, which is especially useful for scenarios like shared internet access or routing to a common set of resources.

Given all