Free and Premium Oracle 1z0-1109-23 Dumps Questions Answers

Explanation

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.

Explanation

A reasonable expectation for Configuration Management (CM) as it pertains to applications in the Oracle Cloud Infrastructure (OCI) DevOps process is consistency in performance, function, design, and implementation. Configuration Management ensures that the application's configuration, set-tings, and dependencies are managed consistently across different environments and deployments. It helps maintain the desired state of the application and ensures that it behaves consistently in terms of performance, functionality, design, and implementation. By using CM practices, develop-ers can ensure that the application's configurations and dependencies are accurately managed and deployed, minimizing variations and inconsistencies that could lead to unexpected behavior or per-formance issues. This helps maintain a consistent experience for users and facilitates smooth and reliable operation of the application.

Explanation

OCI DevOps deployment pipelines can work across OCI regions. From a single deployment pipe-line, deployments can be executed into multiple regions, in parallel or sequentially. To efficiently deploy an application in the Japan Central (ap-osaka-1) region using an existing deployment pipeline set up in the US East (us-ashburn-1) region, the recommended approach is: Deploy directly in ap-osaka-1 from the us-ashburn-1 deployment pipeline. OCI DevOps allows you to deploy applications across regions, and you can leverage this capability to deploy your application in a different region than where the deployment pipeline is set up. You can configure the deployment stage in your deployment pipeline to target the ap-osaka-1 region, specifying the appropriate resources and settings for deployment in that region. This way, you can achieve efficient deployment to the desired region without the need to create a separate deployment pipeline. The other options mentioned are not the most efficient approaches: Creating another deployment pipeline in ap-osaka-1: While it is possible to create another deployment pipeline in the ap-osaka-1 region, it would introduce additional complexity and management overhead. It is more efficient to leverage the existing deployment pipeline and configure it to deploy in the desired region. Deploying the application in us-ashburn-1 and duplicating it in ap-osaka-1: This approach would involve deploying the application separately in both regions, which can lead to duplication of efforts and increased maintenance complexity. It is more efficient to use a single deployment pipeline and configure it to deploy in the target region directly.

Explanation

The two approaches that can be used to build the e-commerce website and achieve deployment in-dependence, easier technology upgrades, and resiliency to architecture changes are: Implement each module as an independent service/process: This approach is aligned with the microservices architecture, where each module or functionality is developed and deployed as a separate service. This al-lows for independent updates, replacements, or deletions of specific modules without disrupting the rest of the application. It provides flexibility, scalability, and easier technology upgrades by enabling the use of different technologies and frameworks for different services. Use microservices architec-ture: Microservices architecture involves breaking down the application into smaller, loosely coupled services that communicate with each other through APIs. This architecture promotes independent deployment of services, making it easier to update or modify specific services without affecting the entire application. It allows for better scalability, fault isolation, and resiliency to architecture changes. The monolithic approach, where the entire application is built as a single unit, is not suitable for achieving the mentioned goals. It can lead to challenges in deployment independence, technology upgrades, and adaptability to newer technologies.

Explanation

To use a Kubernetes cluster in your deployment architecture on Oracle Cloud Infrastructure (OCI) with OCI DevOps service, the two recommended tools or services are: Terraform: Terraform is a widely used Infrastructure-as-Code (IaC) tool that allows you to define and manage your infra-structure resources in a declarative way. You can use Terraform to define and provision your Ku-bernetes cluster on OCI, including the necessary networking, compute resources, and container services. Ansible Collection: Ansible is an open-source automation tool that helps with configuration management, application deployment, and orchestration. The Ansible Collection for OCI provides modules and playbooks specifically designed to manage and interact with OCI resources, including Kubernetes clusters. You can use Ansible Collection to automate the deployment and management of your Kubernetes cluster on OCI. The other options mentioned are not directly related to managing Kubernetes clusters on OCI: Compute Jenkins Plug-in: Jenkins is a popular open-source automation server used for Continuous Integration/Continuous Deployment (CI/CD) processes. The Compute Jenkins Plug-in is specific to managing OCI compute resources using Jenkins but does not directly address Kubernetes cluster deployment. Chef Knife Plug-in: Chef is a configuration management tool that helps with managing infrastructure as code. The Chef Knife Plug-in is used to interact with the Chef tool, but it does not directly address Kubernetes cluster deployment on OCI. OCI Resource Manager: OCI Resource Manager is a service that helps you automate the process of deploying infrastructure resources on OCI. While it can be used to manage various OCI resources, including compute instances, it does not specifically focus on Kubernetes cluster deployment.

Explanation

The Kubernetes Cluster Autoscaler increases or decreases the size of a node pool automatically based on resource requests, rather than on resource utilization of nodes in the node pool. Reference:

The best practices that ABC Inc. should implement to incorporate DevSecOps into their DevOps process are:

• Follow established security guidelines, such as the OWASP DevSecOps guideline, during the development and testing process. The OWASP DevSecOps guideline is a set of recommendations and tools that help developers and testers integrate security into every stage of the software development lifecycle (SDLC). The guideline covers topics such as threat modeling, secure coding, code analysis, security testing, vulnerability management, etc.
• Perform regular scans for vulnerabilities and prioritize fixing them based on their severity. Vulnerability scanning is a process of identifying and assessing the security risks in your code, dependencies, images, containers, or infrastructure. You can use tools such as SonarQube, Sonatype Nexus IQ Server, or Twistlock to perform vulnerability scanning and generate reports with detailed information and remediation suggestions. You should also prioritize fixing the vulnerabilities based on their severity level and potential impact.
• Implement role-based access control and define roles and responsibilities for everyone involved in the development process. Role-based access control (RBAC) is a method of restricting access to resources based on the roles of the users or groups. You can use RBAC to enforce the principle of least privilege, which means granting only the minimum level of access required for each user or group to perform their tasks. You should also define clear roles and responsibilities for everyone involved in the development process, such as developers, testers, operations staff, security staff, etc., and assign them appropriate permissions and policies. Verified References: [DevSecOps - Oracle Cloud Infrastructure Security], [DevSecOps Best Practices - Oracle Cloud Infrastructure Security]

To securely store and version your application and automatically build, test, and deploy your application to OCI, you can choose the following OCI services:

• DevOps: This service enables you to automate the software development lifecycle (SDLC) and deliver software faster and more reliably. You can use DevOps to create projects, repositories, build pipelines, deployment pipelines, triggers, and artifacts.
• Oracle Cloud Infrastructure Registry: This service is a private Docker registry that allows you to store and manage your Docker images in OCI. You can use Registry to push and pull images from your local machine or from your build pipelines.
• Container Engine for Kubernetes: This service is a fully-managed platform that allows you to run your containerized applications in OCI. You can use Container Engine for Kubernetes to create and manage Kubernetes clusters, pods, services, and deployments. Verified References: [DevOps - Oracle Cloud Infrastructure Developer Tools], [Oracle Cloud Infrastructure Registry - Oracle Cloud Infrastructure Developer Tools], [Container Engine for Kubernetes - Oracle Cloud Infrastructure Developer Tools]

Explanation

The reason why the storage administrator cannot associate an encryption key from OCI Vault to an Object Storage bucket in a new compartment could be: There is no Identity and Access Management (IAM) policy allowing the Object Store service to use the Vault key. This is because an IAM policy is required to authorize the Object Storage service to use the encryption key from OCI Vault. The IAM policy should allow the service to use the key and also give permission to access the Vault resource. Without the appropriate IAM policy in place, the storage administrator will not be able to associate the encryption key with the Object Storage bucket. Here is the link to the official documentation on associating an Oracle-managed encryption key from OCI Vault with an Object Storage bucket: Reference:

The steps that you would take to delete the specified image are:

• To determine which container is using the image, use the “docker ps -a” command. This command will list all the containers in your system, including their ID, image name, status, etc. You can look for the container that has the image name d123f4e55e12 in its output.
• To delete the container, use the ‘docker rm 0f1262bd1285’ command. This command will remove the container with the ID 0f1262bd1285 from your system. You can also use the -f flag to force remove the container if it is running or paused.
• To delete the docker image, use the ‘docker rmi d123f4e55e12’ command. This command will remove the image with the ID d123f4e55e12 from your system. You can also use the -f flag to force remove the image if it is being used by another container. Verified References: [docker ps - Docker Documentation], [docker rm - Docker Documentation], [docker rmi - Docker Documentation]

To rollback to version 1 of a secret that has been rotated once, you need to do the following:

• From the version 1 menu, select “Promote to Current”. This will change the status of version 1 from Previous to Current, and change the status of version 2 from Current to Previous. This means that version 1 will be used as the current key version for encrypting and decrypting secrets.
• Optionally, you can also delete version 2 if you no longer need it. From the version 2 menu, select “Delete”. This will change the status of version 2 from Previous to Deleted. You can also restore or destroy deleted versions if needed. Verified References: [Rotating Secrets - Oracle Cloud Infrastructure Vault], [Managing Secret Versions - Oracle Cloud Infrastructure Vault]

The statement that is false about deployment pipeline in OCI DevOps is that using deployment pipeline, you can deploy artifacts to Kubernetes cluster, Instance Group, and OCI Compute Instances. This statement is false because using deployment pipeline, you can deploy artifacts to Kubernetes cluster and Instance Group, but not to OCI Compute Instances. A deployment pipeline is a component of OCI DevOps service that allows you to automate the deployment of your artifacts to various target environments. A target environment is a destination where you want to deploy your artifact, such as a Kubernetes cluster or an Instance Group. An Instance Group is a group of compute instances that share the same configuration and are managed as a single unit. However, OCI DevOps service does not support deploying artifacts directly to individual OCI Compute Instances. Verified References: [Deployment Pipelines - Oracle Cloud Infrastructure DevOps], [Target Environments - Oracle Cloud Infrastructure DevOps], [Instance Groups - Oracle Cloud Infrastructure DevOps]

The primary benefits of DevOps tools are to improve the efficiency of IT operations by automating routine tasks and eliminating manual processes, and to automate the software development lifecycle to increase production speed and consistency. DevOps tools enable collaboration between developers and operations teams, streamline workflows, reduce errors, enhance security, and enable continuous integration and delivery of software. Verified References: [DevOps - Oracle Cloud Infrastructure Developer Tools], [DevOps Tools - Oracle Cloud Infrastructure Developer Tools]

Explanation

The correct answer is: The cost for each stack will be higher for a Pay As You Go subscription than for monthly flex billing. When it comes to the cost of using Terraform stacks created with Oracle Cloud Infrastructure (OCI) Resource Manager, it's important to note that Resource Manager stacks are free to use. However, you will be charged for the resources that are provisioned by these stacks. The cost of these resources will depend on factors such as the types of resources created, their con-figurations, usage duration, and the pricing model associated with your subscription. The pricing model you choose, such as Pay As You Go or monthly flex billing, will affect the cost of the re-sources provisioned by your Terraform stacks. Pay As You Go typically incurs usage-based charges, where you pay for the actual consumption of resources. Monthly flex billing, on the other hand, provides predictable costs based on fixed monthly commitments. The number of lines of text in your Terraform configuration files or the time it takes to build resources does not directly determine the cost. It's the actual usage and configuration of provisioned resources that impact the cost.

Explanation

The prerequisite for creating a secret in Oracle Cloud Infrastructure Vault service is to have a Vault managed key to encrypt the secret. Explanation: Oracle Cloud Infrastructure Vault service provides a secure and centralized location for storing secrets such as passwords, API keys, and other sensitive information. When creating a secret in Vault, one of the prerequisites is to have a Vault man-aged key. The Vault managed key is used to encrypt the secret data, ensuring its confidentiality and security. By utilizing a Vault managed key, the secret can be securely stored and managed within the Oracle Cloud Infrastructure Vault service.

Explanation

The correct option is: A playbook could be leveraged and executed against the group of web servers, as defined in the Inventory. Then, Ansible would connect to each server and apply the same set of configurations. In Ansible, a playbook is a YAML file that describes a series of plays and tasks to be executed against a group of hosts. The inventory file defines the group of web servers that need to be patched. By leveraging a playbook, the DevOps team can define the desired configuration or patching tasks once and apply them consistently across all the web servers in the group. An-sible will connect to each server in the inventory and execute the tasks defined in the playbook, ensuring that the desired configurations or patches are applied uniformly. This approach simplifies the management of multiple servers as the same playbook can be executed against the entire group, eliminating the need to manually configure each server individually. It also allows for automation and repeatability, ensuring that the desired changes are applied consistently and efficiently.

Explanation

The correct answer is: You must have a Vault managed key to encrypt the secret. A prerequisite for creating a secret in the Oracle Cloud Infrastructure (OCI) Vault service is having a Vault managed key. The Vault service allows you to securely store and manage sensitive information such as pass-words, API keys, and other secrets. To ensure the confidentiality of the stored secrets, they are encrypted using encryption keys. In OCI Vault, the encryption keys used for encrypting secrets are managed by the Vault service itself, and you need to have a Vault managed key available to encrypt the secret before creating it.

Explanation

The correct answer is: From the version menu, select "Promote to current." To rollback to a previous version in OCI Secret Management within a Vault, the administrator should select the desired version from the version menu and choose the option "Promote to current." In this scenario, the administrator wants to rollback to version 1, so they would select version 1 from the menu and promote it to the current version. This action will make version 1 the active and current version of the secret, replacing version 2. The "Promote to current" option allows administrators to switch between different versions of a secret and make a specific version the active one.

Explanation

The correct approach to upgrade an Oracle Container Engine for Kubernetes (OKE) cluster to a newer version of Kubernetes is to first upgrade the control plane and then upgrade the node pools. Here are the steps to follow: Upgrade the control plane: Initiate the upgrade process for the control plane using the OCI Console, CLI, or API. This upgrade will update the Kubernetes control plane components running in the master nodes of the cluster. Upgrade the node pools: After the control plane upgrade is completed, you can proceed to upgrade the node pools. A node pool is a set of worker nodes within the cluster. You can upgrade the node pools one at a time or simultaneously, depending on your requirements and cluster configuration. By following this approach, you ensure that the control plane is upgraded first, which ensures compatibility and stability with the new version of Kubernetes. Afterward, you can upgrade the node pools to ensure all worker nodes are running the latest version of Kubernetes. It is important to note that before performing any upgrades, it is recommended to review the release notes and upgrade documentation provided by Oracle for any specific instructions or considerations related to the version you are upgrading to. Reference:

Explanation

When creating stages for an Oracle Kubernetes Engine (OKE) deployment pipeline, you are able to include the following actions within the pipeline stages themselves: Add a stage to apply the Kubernetes manifest to the Kubernetes cluster: This stage allows you to apply the desired Kubernetes manifest files that define the deployment configuration of your application to the OKE cluster. It ensures that the desired state of your application is reflected in the cluster. Add a stage to apply the container image to the Kubernetes cluster: This stage involves deploying the container image of your application to the OKE cluster. It ensures that the latest version of your application's container image is deployed and running in the cluster. Add a stage to deploy incrementally to multiple OKE target environments: This stage allows you to deploy your application incrementally to multiple OKE target environments, such as staging and production. It enables you to control the deployment process and ensure that the application is rolled out smoothly across different environments. Add a stage to deliver artifacts to an Oracle Cloud Infrastructure (OCI) Artifact Registry: This stage involves delivering the artifacts generated during the build process, such as container images or other artifacts, to the OCI Artifact Registry. The Artifact Registry provides a centralized location for storing and managing artifacts, making them easily accessible for deployment to OKE or other environments. Including these actions within the pipeline stages themselves helps streamline the deployment process and ensures that all necessary steps are included within the automated pipeline, minimizing the need for manual intervention or external processes.

Explanation

The recommended solution to achieve the requirements mentioned would be: Configure OCI Com-pute agent on OCI compute instances to collect the required resource metrics. Use OCI Events and Functions services to track the end-to-end deployment pipeline (com.oraclecloud.devopsdeploy.createdeployment) and the creation of new OCI Object Storage buckets (com.oraclecloud.objectstorage.createbucket). Finally, utilize OCI Notifications and Events services to notify these changes. Explanation: Continuous monitoring with resource metrics: Install and configure the OCI Compute agent on the OCI compute instances to collect the required re-source metrics such as CPU utilization, memory utilization, and disk IOPS. This ensures continuous monitoring of the VMs as they are migrated to OCI. Monitoring the deployment pipeline: Utilize the OCI Events service to track the end-to-end deployment pipeline. Specifically, use the event type "com.oraclecloud.devopsdeploy.createdeployment" to monitor the deployment process. This allows you to track the progress and status of the migration workflow. Notification for new OCI Object Storage buckets: Leverage the OCI Notifications service in conjunction with the OCI Events ser-vice. Set up a notification rule to trigger an email notification whenever a new OCI Object Storage bucket is created. Use the event type "com.oraclecloud.objectstorage.createbucket" to identify the creation of new buckets. By combining the OCI Compute agent, OCI Events service, Functions service, and Notifications service, you can ensure continuous monitoring of resource metrics, track the deployment pipeline, and receive email notifications for any new OCI Object Storage bucket creations during the migration workflow.

Explanation

The proper rule to follow when creating container repositories inside the Oracle Cloud Infrastructure (OCI) Registry is: You must use a separate container repository for each image, but multiple versions of that image can be in a single repository. This means that each distinct image should have its own repository, but different versions of the same image can be stored within that repository. This allows for better organization and management of container images. The other options mentioned are not correct: Checking the "Immutable Artifacts" box does not exist as a requirement when creating a container repository. Immutable artifacts refer to the immutability of the container images themselves, not a setting in the repository. There are no restrictions on using capital letters or hyphens in the naming of container repositories. Both capital letters and hyphens are allowed in the repository name. The OCI DevOps Managed Build stage is not directly related to defining artifacts in the artifact and container repositories. The Managed Build stage is responsible for building and packaging application artifacts, but it does not define the repositories themselves.

Explanation

The correct answer is: Continuous delivery is a process that initiates deployment manually, while continuous deployment is based on automating the deployment process. In the DevOps lifecycle, continuous delivery and continuous deployment are both approaches to software release and deployment, but they differ in the level of automation and manual intervention involved. Continuous delivery refers to the practice of continuously preparing software releases in a way that they could be deployed to production at any time. It focuses on automating the build, test, and deployment processes, ensuring that software is always in a deployable state. However, the decision to actually deploy the software to production is made manually, typically by a human operator or team. On the other hand, continuous deployment takes the automation one step further. With continuous deployment, the software is automatically deployed to production as soon as it passes all the necessary tests and checks. There is no manual intervention in the deployment process, and it is fully automat-ed. This approach allows for faster and more frequent deployments, reducing the time between developing new features and making them available to users. So, the main difference is that continuous delivery requires a manual trigger for deployment to production, while continuous deployment automates the deployment process without the need for manual intervention.

Explanation

To automate infrastructure and configure Oracle Cloud Infrastructure (OCI) resources, the recom-mended tool to use is Ansible. Ansible is a popular automation tool that focuses on provisioning, configuring, and managing IT infrastructure. It uses a declarative language called YAML to de-scribe the desired state of the infrastructure, allowing you to define and automate the configuration of OCI resources such as Compute, Load Balancing, and Database services. Ansible provides a col-lection specifically designed for OCI, called the "Ansible Collection," which includes modules and playbooks for interacting with OCI APIs. By utilizing Ansible in OCI, you can easily automate the provisioning and configuration of your infrastructure, ensuring consistency and reproducibility. An-sible's simplicity and agentless architecture make it a flexible and efficient choice for managing OCI resources and automating infrastructure tasks in the context of OCI DevOps.

The correct way is to use the variables section in your build_spec.yaml file to define variables and assign values to them. You can also use the vaultVariable section to define variables that hold the content of the vault secrets in OCID format. You can then use these variables in other sections of your build_spec.yaml file by using the syntax $(VARIABLE_NAME). You can also use the exportedVariables section to define variables that can be used in subsequent stages of the same pipeline. Verified References: [Variables - Oracle Cloud Infrastructure DevOps], [Defining Variables - Oracle Cloud Infrastructure DevOps]

Explanation

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:

The recommended approach in OCI for creating identical blue-green environments for deploying a critical application is to use two separate OKE clusters to ensure complete separation between environments. A blue-green environment is a deployment technique that involves creating two identical environments (blue and green) and switching traffic between them after testing. This technique allows you to reduce downtime, minimize risk, and improve user experience. To create blue-green environments in OCI, you can use two separate OKE clusters, one for the blue environment and one for the green environment. Each cluster will have its own set of resources, such as node pools, pods, services, deployments, etc., that are isolated from each other. You can also use OCI Load Balancing service to route traffic between the clusters based on your criteria. Verified References: [Deployment Strategies - Oracle Cloud Infrastructure DevOps], [Creating Clusters - Oracle Cloud Infrastructure Container Engine for Kubernetes]

The steps that you can perform to enable specific logs applicable to services along with configuring an alarm to monitor any new failures are:

• Install the OCI compute agent software on client systems, enable Custom log and create an agent configuration selecting log path. The OCI compute agent is a software component that runs on your compute instances and collects logs from various sources, such as files, syslog, Windows Event Log, etc. You can use the OCI compute agent to enable Custom log, which is a type of log that allows you to define your own log source and format. You can also create an agent configuration that specifies the log path, log group, and log name for your Custom log.
• Create custom filters with required data fields (for example: source, time, statusCode, message) to filter log messages, configure Service Connector with Monitoring for creating an Alarm. A custom filter is a query that allows you to filter and analyze your log messages based on various data fields, such as source, time, level, message, etc. You can use custom filters to search for specific patterns or conditions in your logs, such as failures or errors. You can also configure a Service Connector with Monitoring, which is a component that allows you to transfer data from one OCI service to another. You can use a Service Connector with Monitoring to send your filtered log messages to the OCI Monitoring service, which is a service that allows you to create metrics and alarms based on your logs. You can then create an Alarm, which is a rule that triggers an action when a metric meets a specified threshold. Verified References: [Compute Agent - Oracle Cloud Infrastructure Logging], [Custom Logs - Oracle Cloud Infrastructure Logging], [Custom Filters - Oracle Cloud Infrastructure Logging], [Service Connectors - Oracle Cloud Infrastructure Logging], [Monitoring - Oracle Cloud Infrastructure Logging], [Alarms - Oracle Cloud Infrastructure Logging]

Explanation

The statement that is TRUE with regard to OCI DevOps is: OCI DevOps automates the Software Development Life Cycle (SDLC) and serves as a Continuous Integration/Continuous Deployment (CI/CD) platform for developers. OCI DevOps provides capabilities to automate and streamline the entire software development process, including building, testing, deploying, and managing applications and infrastructure. It enables developers to implement CI/CD practices and deliver software more efficiently and reliably.

Explanation

"The OCI capability that can help achieve the requirement of archiving logging data into OCI Object Storage is the ""Service Connector Hub."" The Service Connector Hub in OCI enables you to configure connections and workflows between different OCI services. In this case, you can create a connection between the OCI Logging service and OCI Object Storage using the Service Connector Hub. By setting up a connection between these services, you can define a workflow to automatically transfer the logs collected by the Logging service to Object Storage for archiving. This ensures that the logging data is securely stored and easily accessible for future analysis or compliance purposes. The Logging Query capability allows you to search and analyze logs, but it does not directly address the requirement of archiving the logging data into Object Storage. ObjectCollectionRule is not a valid OCI capability and does not pertain to the archiving of logging data into Object Storage. IAM policies are used to manage access and permissions within OCI, but they do not directly pro-vide the capability to archive logging data into Object Storage." Reference: