Which can be used to ensure that your Autonomous Database is accessible only from a given set of IPs?

Restricting access to an Autonomous Database to specific IPs involves network security controls. The

correct answer is:

Access Control List (C): In Autonomous Database, an Access Control List (ACL) defines which IP

addresses or CIDR blocks (e.g., 192.168.1.0/24) can connect to the database. You configure this via

the OCI console under the ADB’s “Access Control List” settings, adding rules like “Allow TCP from

10.0.0.0/16 on port 1522.” This applies to public endpoints (shared infrastructure) or private

endpoints with additional network rules, ensuring only authorized IPs can initiate connections. For

example, a company might restrict access to its office VPN range, blocking all other traffic. ACLs work

at the database level, complementing VCN security.

The incorrect options are:

Security List (A): Security Lists operate at the VCN subnet level, controlling traffic to all resources in

the subnet (e.g., ingress TCP 1522 to an ADB subnet). While useful, they’re broader than ADB-

specific ACLs, which target the database instance directly, making ACLs the precise answer here.

IP Vault (B): There’s no “IP Vault” in OCI. This might confuse OCI Vault (for secrets), but it doesn’t

manage IP access.

IPSec List (D): IPSec secures traffic via VPNs, not IP allowlisting for database access. It’s unrelated to

ADB connectivity restrictions.

ACLs provide a database-specific, user-friendly way to enforce IP-based access control.

Reference: Oracle Cloud Infrastructure Documentation - Configuring Access Control