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

（A）Configure OCI Compute agent on OCI compute instances to collect required resource metrics. Use OCI Events and Functions services to track the end-to-end deployment pipeline (com.oraclecloud.devopsdeploy.createdeployment) and creation of new buckets (com.oraclecloud.objectatorage.createbucker Use OCI Notifications and Events services to notify these changes.

（B）Configure OCI Compute agent on on-premises VMs to collect required resource met-rics. Lise OCI Events service to track all deployments (com.oraclecloud.devopsdeploy.createdeployment) with OC!
Notifications service to track and report all changes occurring the target environment.

（C）Configure OCI Compute agent on on-premises VMs and OCI compute instances to collect required resource metrics. Use OCI Events service to track the end-to-end deployment process (com.oraclecloud.devopsdeploy.createdeployment) and creation of new bucket (com.oraclecloud.objectstorage.createbucket Use OCI Notifications and Events services to notify these changes.

（D）Configure both 3rd party monitoring tool and OCI Compute Agent on OCI compute instances to collect required resource metrics. Use OCI Events service (com.oraclecloud.devopsdeploy.createdeployment) with Notifications service to track and notify all changes occurring in the target OCI environment.

（A）Use monolithic approach, as it allows you to easily redeploy your applications to per-form frequent updates.

（B）Use microservices architecture as it eliminates any long term commitment to a technology stack.

（C）Use monolithic approach to as it makes it easier to incrementally adapt to newer technology.

（D）Choose monolithic approach over microservices as it has better fault isolation capability.

（E）Build the application as a single unit and use container technology to deploy it.

（F）Implement each module as an independent service/process which can be replaced, up-dated, or deleted without disrupting the rest of the application:

（A）Deploy an Oracle Function that checks the bucket every 60 seconds, then sends an email when a new file is found.

（B）Define and schedule a Cron job that monies the bucket, then sends an email when a new file is found.

（C）Create an alert in the OCI Monitoring service that triggers an email when the monitored bucket is updated.

（D）Create a rule in the OCI Events service that sends the bucket event to an OCI Notifications service topic configured with an email subscriber.

（A）You can add an Approval stage that pauses the deployment for a specified duration for manual decision from the approver

（B）You can add a Wait stage that adds a specified duration of delay in the pipeline.

（C）Using deployment pipeline, you can deploy artifacts to Kubernetes cluster, Instance Group, and OCI Compute Instances.

（D）You can add a Traffic Shift stage that routes the traffic between two sets of backend IPs using preconfigured load balancer and listener.

（A）defined parameters such as $(VARIABLE_NAME) that you later assigned in the Pa-rameters tab when you ran the build pipeline

（B）exported a vaultVariable by creating another variable to export, then transferred the values over during a build stage

（C）used vaultVariable to hold the content of the vault secrets in OCID format

（D）assumed a non-exported variable would be persistent across multiple stages of a build pipeline.

（A）kubectl create secret docker-registry secret-name> --docker-server- <region-key>.oke.io
--docker-username=<oci-username> --docker- password='<oci-auth-token>'
--docker-email-<email-address>

（B）kubectl create secret docker-registry <secret-name> --docker-server- <region-key>.oke.io
--docker-username=<tenancy-namespace>/<oci-username>
--docker-password='<oci-auth-token>'--docker-email-cemail- address>

（C）kubectl create secret docker-registry <secret-name> --docker-server- <region-key>.ocir.io
--docker-username=coci-username> --docker- password='<oci-auth-token>
--docker-email-email-address>

（D）kubectl create secret docker-registry <secret-name> --docker-server- <region-key>.ocir.io
--docker-username=<tenancy-namespace>/<oci- username>
--docker-password='<oci-auth-token>'--docker-email-cemail- address>

（A）When creating a new cluster, essential cluster add-ons cannot be disabled.

（B）When creating a new cluster, essential cluster add-ons are set to manually update.

（C）When enabling a cluster add-on, you cannot configure the add-on by specifying one or more key/value pairs to pass as arguments to the cluster add-on.

（D）When you disable a cluster add-on using the console, the add-on is completely removed from the cluster