Which two networking configurations are required for Oracle Database@Azure deployment? (Choose two)

Question breakdown

Tests

Plan network prerequisites for Oracle Database@Azure

Difficulty

Medium

Key idea: Exadata VM clusters attach to a delegated Azure subnet that must be sized correctly and reachable from application VNets, usually through VNet peering.

How to reach the answer

1. Oracle Database@Azure lands in an Azure VNet subnet delegated to Oracle, so the subnet must have enough addresses for the VM cluster nodes, VIPs and SCAN IPs.
2. Applications in other VNets reach the database through VNet peering, typically in a hub-and-spoke design.
3. FastConnect is an OCI-to-on-premises circuit and is not part of this deployment.
4. DNS forwarding can help with hybrid name resolution but is optional, so B and D are the answers.

Each option

• AIncorrect. DNS forwarding is an optional add-on for custom or hybrid resolution, not a deployment requirement.
• BCorrect. VNet peering connects application VNets to the VNet holding the Exadata delegated subnet.
• CIncorrect. FastConnect is OCI's dedicated private link and is not needed because the database runs inside Azure.
• DCorrect. The delegated subnet must have enough IP addresses for Exadata VM nodes, virtual IPs and SCAN listeners, plus future scaling.

Common trap: FastConnect looks required because OCI is involved, but the database runs inside Azure data centers, so Azure-native networking replaces it.

In practice: Network engineers reserve a properly sized CIDR for the Oracle delegated subnet early, because undersizing blocks VM cluster creation or later scale-out.

Remember: For Oracle Database@Azure, size the delegated subnet generously and peer application VNets to it; FastConnect does not apply.

Official documentation: Oracle Database@Azure

Drafted with AI assistance and checked against the answer key.