Oracle Cloud Infrastructure Developer - Connecting to Autonomous Transaction Processing (ATP) Database from Kubernetes Container

Connecting to ATP from Kubernetes Container

Question

You have a containerized app that requires an Autonomous Transaction Processing (ATP) Database.

Which option is not valid for connecting to ATP from a container in Kubernetes? (Choose the best answer.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D.

https://blogs.oracle.com/developers/creating-an-atp-instance-with-the-oci-service-broker

The correct answer is option A, "Enable Oracle REST Data Services for the required schemas and connect via HTTPS."

Option A is not a valid method to connect to an Autonomous Transaction Processing (ATP) Database from a container in Kubernetes. Oracle REST Data Services (ORDS) is a tool that provides a RESTful web interface to Oracle databases, and while it can be used to connect to an ATP database, it is not a recommended method for containerized apps in Kubernetes.

Option B is a valid method for connecting to ATP from a container in Kubernetes. The ATP database instance Wallet files contain the necessary credentials for connecting to the database, and a Kubernetes secret can be created with the contents of the Wallet files. This secret can then be mounted as a volume in the container, allowing the app to access the database.

Option C is also a valid method for connecting to ATP from a container in Kubernetes. Kubernetes secrets can be used to store and pass sensitive information, such as the ATP instance OCID and OCI API credentials, to the container. The app can then use the CreateConnection API endpoint from the service runtime to establish a connection to the database.

Option D is also a valid method for connecting to ATP from a container in Kubernetes. The Oracle Cloud Infrastructure Service Broker allows Kubernetes resources to be created and managed using the OCI API. By deploying ServiceInstance and ServiceBinding resources for ATP, the app can use the specified binding name as a volume in the application deployment manifest, allowing it to access the database.

In summary, options B, C, and D are valid methods for connecting to an Autonomous Transaction Processing (ATP) Database from a container in Kubernetes. Option A is not a recommended method for containerized apps in Kubernetes.