1z0-1084-23 無料問題集「Oracle Cloud Infrastructure 2023 Developer Professional」

（A）Generate a self-signed certificate using Let's Encrypt. Use that certificate on OCI Load Balancer. Create the Kubernetes service using this load balancer.

（B）Create a self-signed certificate and its corresponding key. Create a Kubernetes secret using the certificate and the key. Then add these annotations to the Kubernetes service: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/oci-load-balancer-tls-secret: ssl certificate-secret

（C）Create a self-signed certificate and its corresponding key. Create a Kubernetes secret using the certificate and the key. Then add these annotations to the Kubernetes service: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/oci-load-balancer-security-list management-mode: "Frontend"

（D）Add these annotations to the kubernetes service: annotations: service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443" service.beta.kubernetes.io/oci-load-balancer-ssl-secret-key: ssl secret-key

（A）Microservices are hard to test in isolation.

（B）Microservices communicate over lightweight APIs.

（C）All microservices share a data store.

（D）Microservices can be independently deployed.

（E）Microservices can be implemented in limited number of programming languages.

（A）Microservices always use a data store while serverless functions never use a data store.

（B）Microservices are triggered by events while serverless functions are not.

（C）Microservices are used for long running operations while serverless functions are used for short running operations.

（D）Microservices are stateless while serverless functions are stateful.

（A）Leverage OCI Cloud Guard to extract and visualize the debug logs generated by your application.

（B）Trace performance issues In the Application Performance Monitoring service by enabling Function traces.

（C）Use OCI Service Connector Hub to configure a service connector to automatically send logs to the OCI Logging Analytics service.

（D）View service metric information from the OCI Monitoring service.

（E）Configure the application to send logs to the OCI Logging service.

（A）Continuous delivery requires more automatic linting, while continuous deployment testing must be run manually.

（B）Continuous delivery involves automation of developer tasks, while continuous deployment involves manual operational tasks.

（C）Continuous delivery utilizes automatic deployment to a development environment, while continuous deployment involves automatic deployment to a production environment.

（D）Continuous delivery is a process that initiates deployment manually, while continuous deployment is based on automating the deployment process.

（A）Use a ClusterIP service type in Kubernetes for each of your service endpoints using a load balancer to expose the endpoints.

（B）Deploy an Ingress Controller and use it to expose each endpoint with its own routing endpoint.

（C）Create a separate load balancer instance for each service using the lowest 100 Mbps option.

（D）Use a NodePort service type in Kubernetes for each of your service endpoints using the node's public IP address to access the applications.

（A）Invoke from the Fn Project CLI.

（B）Invoke from the Docker CLI.

（C）Invoke from the OCI CLI.

（D）Trigger by an event in the Oracle Cloud Infrastructure (OCI) Events service.

（E）Send signed HTTP requests to the function's invoke endpoint.

（A）Improved in-function state management

（B）Automatic horizontal scaling

（C）Easier to run long-running operations

（D）Reduced operational cost

（E）No need for integration testing

（A）New secret versions automatically expire in 90 days unless you configure an expiry rule.

（B）A unique OCID is automatically generated for each secret and remains unchanged even when creating a new secret version.

（C）A secret reuse rule prevents the use of secret contents across different versions of a secret.

（D）You can manually create new secrets as well as new secret versions using the OCI Console:

（A）STOCK_RESPONSE_BACKEND

（B）ORACLE_FUNCTIONS_BACKEND

（C）HTTP BACKEND

（D）ORACLE_STREAMS_BACKEND