If there is no special control on the traffic direction of the subnet, and the default IPC intranet intercommunication, the default routing table can be used, and there is no need to configure a…

Question

Options

• ATrue
• BFalse

• A
  80% (47)
• B
  20% (12)

Explanation

Option A is correct because in cloud networking environments, default routing tables are automatically configured to handle standard intranet traffic within the same virtual network. When no special traffic direction controls are applied to a subnet and the default IPC (intranet private communication) settings are in use, the platform's built-in routing is sufficient to route traffic between subnets without any manual intervention. Custom routing policies are only required when you need to override default behavior, such as forcing traffic through a firewall, NAT gateway, or specific network appliance. Option B is incorrect because it implies that custom routing is always necessary, which overcomplicates standard intranet configurations where the defaults already satisfy communication requirements.

Memory tip: Think of it as "default in, default out" - if everything is default (no special controls, default IPC), then the default routing table does the job, and no custom policy is needed.

No community discussion yet for this question.