True or False: It is a best practice to use custom route tables for each subnet for granular routing.

Using custom route tables for each subnet is considered a best practice in AWS for achieving granular routing, making the statement true. By employing custom route tables, you can control the routing of traffic to and from resources more effectively within your Virtual Private Cloud (VPC). This flexibility allows you to specify routes that are tailored to the specific needs of each subnet, which can be critical for optimizing performance, security, and connectivity.

For example, a public subnet may require a route to an internet gateway to allow external traffic, whereas a private subnet might direct traffic through a NAT gateway for outbound internet access without exposing its resources directly. Additionally, custom route tables can facilitate integration with different services, such as peering connections, VPNs, or Direct Connect, depending on the architecture's requirements.

The option stating that this practice is only for specific subnets does not capture the full scope of the best practice, which applies broadly across different subnet configurations. The notion that it depends on the architecture also doesn't wholly embrace the acknowledged benefits of segregating route management through custom route tables, as the best practice is relevant in various architectural scenarios for improved network control. Overall, utilizing custom route tables is vital for creating a well-optimized and secure network environment in AWS.