I85PREP
⌘ K
Oracle Autonomous Database Professional study materials
Oracle Autonomous Database Professional study resources

Oracle Autonomous Database Professional: Provisioning and Connecting to Autonomous Databases

Oracle Autonomous Database Professional · Work through your exam, one topic at a time.

All guide sections

Provisioning and Connecting to Autonomous Databases

Domain 2: Provisioning and Connecting to Autonomous Databases

This domain tests provisioning choices and the connection path from client to database. Expect scenarios on public versus private endpoints, wallets, service levels, and least-privilege users.

Core rules and concepts

  • Provisioning requires a compartment, IAM permissions, a database name, ADMIN password, workload type, compute model, and storage. For a private endpoint, also plan the VCN, subnet, route table, security list, and optional network security group.
  • Network access choices are public endpoint with access control, public endpoint open to allowed IPs/VCNs, or private endpoint. Private endpoint keeps traffic inside the VCN; public endpoint with an ACL restricts source addresses.
  • Download the client credentials wallet for mutual TLS. Connection strings expose service levels such as _tpurgent, _tp, _high, _medium, and _low for transaction processing; data warehouse typically uses _high, _medium, and _low. Use _medium for ordinary application pools, _tpurgent for highest-priority OLTP, and _high for parallel/reporting work.
  • Connect with SQL Developer, SQLcl, Database Actions, JDBC, or OCI Cloud Shell. Database Actions provides SQL, Data Load, and related tools in the browser.
  • ADMIN is for administration. Create application users with only the privileges they need; do not put ADMIN credentials in an app.

Worked example

An application in a private subnet must connect without traversing the internet. Provision Autonomous Database with a private endpoint in the application VCN/subnet, attach an NSG that allows the app tier on the database listener port, download the wallet to the app host, and use the _medium service in the connection pool. Reasoning: the private endpoint removes public exposure; the NSG and subnet controls restrict reachability; _medium suits a pooled OLTP app better than a parallel-query service.

Traps that cost marks

  • Forgetting route/security rules for a private endpoint.
  • Using a wallet from another database or after credentials change.
  • Choosing _high for a high-concurrency OLTP pool.
  • Using ADMIN in application configuration.