Resiliency is about recovering from failures without downtime or data loss. It involves designing systems that can continue to operate or quickly return to a fully functional state even when failures occur. It is not about avoiding failures entirely, but rather about handling and recovering from them efficiently.
To enable Oracle Cloud Infrastructure (OCI) Container Engine for Kubernetes (OKE) cluster access from the kubectl CLI, you need to install and configure the OCI CLI and have a configured OCI API signing key pair. The OCI CLI is necessary to interact with the services and to set up the kubeconfig file required for kubectl to communicate with the Kubernetes cluster. The API signing key pair is used for authenticating API requests made from the CLI tools or other applications to OCI services.
Using Kubernetes secrets to configure environment variables on the container with ATP instance OCID and OCI API credentials, and then using the CreateConnection API endpoint from the service runtime is not a valid method. This is because there is no such OCI API named 'CreateConnection API' specifically for establishing a connection to an ATP database from a Kubernetes environment. The other options are valid methods: Enabling Oracle REST Data Services, creating a Kubernetes secret with instance Wallet files, and using the Oracle Cloud Infrastructure Service Broker are all legitimate approaches for connecting to ATP from a container in Kubernetes.
OCI Resource Manager is the appropriate service to create and manage your infrastructure in Oracle Cloud Infrastructure. It is a managed service that allows you to automate the process of provisioning your Oracle Cloud Infrastructure resources. Using infrastructure-as-code through tools like Terraform, you can define and manage your OCI resource configurations consistently across different environments such as development, testing, staging, and production.
When developing an application that uses Oracle Cloud Infrastructure (OCI) APIs to POST messages to a stream, the request must include an authorization signing string, which necessitates the use of the Authorization header. This is required for authenticating the request and ensuring its integrity. The other statements outline correct requirements for making a POST request to the OCI Streaming service, such as including specific headers and ensuring proper time synchronization to avoid an HTTP 401 error. Therefore, the incorrect statement is that the request does not require an Authorization header.