The approach that should be used to trigger emails when a new file is created in an OCI Object Storage bucket is to create a rule in the OCI Events service that sends the bucket event to an OCI Notifications service topic configured with an email subscriber. The OCI Events service is a service that allows you to react to changes in your OCI resources by creating rules that match events of interest and trigger actions based on those events. The OCI Notifications service is a service that allows you to broadcast messages to distributed components through topics and subscriptions. By using these services together, you can achieve the following workflow:

Create an OCI Notifications service topic and add an email subscriber with the customer's email address.

Create an OCI Events service rule that matches the Object Storage bucket event type ''com.oraclecloud.objectstorage.createobject'' and specifies the Notifications topic as the action.

Whenever a new file is created in the Object Storage bucket, an event will be generated and matched by the rule, which will send a message to the Notifications topic.

The Notifications topic will deliver the message to the email subscriber, which will trigger an email to the customer. Verified Reference: [Events - Oracle Cloud Infrastructure Developer Tools], [Notifications - Oracle Cloud Infrastructure Developer Tools]

The goal of DevSecOps is to integrate security into every stage of the software development process, from planning to delivery. DevSecOps aims to find and fix security issues early in the software development process, before they become costly and risky to remediate. DevSecOps also codifies security as part of the larger goal structure of DevOps, which is to deliver software faster and more reliably while ensuring quality and compliance. Verified Reference: [DevSecOps - Oracle Cloud Infrastructure Security], [DevSecOps Best Practices - Oracle Cloud Infrastructure Security]

The configuration error that could lead to the 'unable to clone the repository' error is: Dynamic Groups access and OCI IAM policies to the code repository are not set: This error suggests that the necessary permissions and access controls have not been properly configured for the OCI Code Repository. Dynamic Groups and IAM policies control user access and permissions to various OCI re-sources, including code repositories. Without the correct configuration, the build pipeline is unable to clone the repository and retrieve the source code. The other options mentioned are not directly related to the error mentioned: More stages were added than required to the build pipeline: Adding more stages to the build pipeline than necessary would not cause an error related to cloning the repository. It might impact the overall flow and logic of the pipeline, but it is not directly related to the repository cloning process. Source files connected directly to the build pipeline: Connecting source files directly to the build pipeline is a typical setup and would not cause a 'unable to clone the repository' error. Artifacts and build spec being removed before running the build: Removing artifacts and build specifications before running the build could impact the build process and result in other errors, but it would not specifically cause an error related to cloning the repository. Reference: https://docs.oracle.com/en-us/iaas/Content/devops/using/troubleshooting.htm

The correct statement is: You need to provision a new stack because Terraform uses immutable in-frastructure. In Oracle Cloud Infrastructure (OCI) Resource Manager, Terraform uses the concept of immutable infrastructure, which means that any changes to the infrastructure are managed through the Terraform code. In this scenario, if you want to add a CIDR block, subnet, and compute instance to your VCN, you would need to make the necessary changes to your Terraform code, create a new stack in Resource Manager, and deploy the updated code. This ensures that the infra-structure is created consistently and according to the desired state defined in the Terraform code. Simply provisioning the new resources in the OCI console and later adding them to the Terraform configuration and state would not be the recommended approach in this case.

The statement that is true regarding OKE supported images and shapes for worker nodes is that to provision worker nodes from a custom image, you must use the CLI or API and specify the custom image's OCID when creating the node pool. A custom image is an image that you create by importing an image file from your local environment or by customizing an existing OCI image. A custom image allows you to have more control over the configuration and software of your worker nodes. However, to use a custom image for your worker nodes, you cannot use the Console. You must use the CLI or API and provide the OCID (Oracle Cloud Identifier) of the custom image when creating the node pool. Verified Reference: [Creating Node Pools - Oracle Cloud Infrastructure Container Engine for Kubernetes], [Custom Images - Oracle Cloud Infrastructure Compute]