2023年最新のFast2test Oracle 1z0-1109-23問題集と試験テストエンジン
Oracle 1z0-1109-23問題集にはリアル試験問題解答
質問 # 57
A company has an Oracle Cloud Infrastructure (OCI) DevOps deployment pipeline set up in US East (us-ashburn 1) region, but they want to deploy an application in Japan Central (ap-osaka-1). How can they deploy their application in the ap-osaka-1 region with the deployment pipeline set up in the us ashburn-1 region in the most efficient manner?
- A. It is not possible to use the same deployment pipeline across regions.
- B. Create another deployment pipeline in ap-osaka-1 to connect to the deployment pipeline in us ashburn-1
- C. Deploy directly in ap-osaka-1 from the us-ashburn-1 deployment pipeline.
- D. Deploy application in us-ashburn-1 and duplicate the same in ap-osaka-1.
正解：C
解説：
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.
質問 # 58
Which of the following are VALID log category with regard to logging service in Oracle Cloud Infrastructure?
(Choose two.)
- A. Audit logs
- B. Custom logs
- C. Query logs
- D. User logs
正解：A、B
解説：
Explanation
The two valid log categories with regard to the logging service in Oracle Cloud Infrastructure (OCI) are: Audit logs: Audit logs capture actions and events related to resource operations in OCI. These logs provide visibility into who performed an action, what action was performed, and when it occurred, helping with compliance and security monitoring. Custom logs: Custom logs allow users to define and send their application-specific log data to OCI logging service. Users can create custom log groups and log streams to organize and manage their log data. This enables centralized log management and analysis for custom applications and services running in OCI. Query logs and User logs are not valid log categories in OCI's logging service.
質問 # 59
As a cloud engineer, you are responsible for managing a Kubernetes cluster on the Oracle Cloud Infrastructure (OCI) platform for your organization. You are looking for ways to ensure reliable operations of Kubernetes at scale while minimizing the operational overhead of managing the worker node infrastructure. Which cluster option is the best fit for your requirement?
- A. Using OCI OKE managed nodes with cluster autoscalers to eliminate worker node infrastructure management.
- B. Using OCI OKE virtual nodes to eliminate worker node infrastructure management.
- C. Using Kubernetes cluster add-ons to automate worker node management.
- D. Creating and managing worker nodes using OCI compute instances.
正解：B
解説：
Explanation
The cluster option that is the best fit for ensuring reliable operations of Kubernetes at scale while minimizing the operational overhead of managing the worker node infrastructure is using OCI OKE virtual nodes to eliminate worker node infrastructure management. OKE is a fully managed service that allows you to run and manage your Kubernetes cluster on OCI. A Kubernetes cluster consists of a control plane and a set of worker nodes that run your containerized applications. OKE provides a highly available and secure control plane that is managed by Oracle, while you are responsible for managing the worker node infrastructure. However, OKE also supports virtual nodes, which are serverless compute resources that are automatically provisioned and scaled by OCI based on your application workload demands. Virtual nodes eliminate the need for managing worker node infrastructure, such as security patches, updates, scaling, etc. Virtual nodes also offer a serverless Kubernetes experience, where you can focus on developing and deploying your applications without worrying about the underlying infrastructure. Verified References: [Container Engine for Kubernetes - Oracle Cloud Infrastructure Developer Tools], [Virtual Nodes - Oracle Cloud Infrastructure Container Engine for Kubernetes]
質問 # 60
A DevOps engineer is asked to access an Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) cluster to deploy new applications and manage existing ones. Which three statements are true? (Setting Up Cluster Access). (Choose three.)
- A. To access the cluster using kubectl you have to set up a Kubernetes configuration file for the cluster.
The kubeconfig file by default is named config and stored in the $HOME/.kube directory. - B. When a cluster's Kubernetes API endpoint has a public IP address, you can access the cluster in Cloud Shell by setting up a kubeconfig file
- C. You cannot setup Cloud shell access to the cluster if the clusters Kubernetes API end-point has a private IP address.
- D. To access the cluster using kubectl you have to set up a Kubernetes manifest file for the cluster. The kubeconfig file by default is named config and stored in the $HOME/.manifest directory
- E. Generating an API signing key pair is a mandatory step while setting up cluster access using local machine if the public key is not already uploaded in the console.
正解：A、B、E
解説：
Explanation
The three statements that are true regarding setting up cluster access for an Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) cluster are: When a cluster's Kubernetes API endpoint has a public IP address, you can access the cluster in Cloud Shell by setting up a kubeconfig file. This allows you to authenticate and interact with the cluster using kubectl. Generating an API sign-ing key pair is a mandatory step when setting up cluster access using a local machine if the public key is not already uploaded in the console. This key pair is used for authentication and securing the connection to the cluster. To access the cluster using kubectl, you need to set up a Kubernetes con-figuration file (kubeconfig) for the cluster. By default, the kubeconfig file is named "config" and is stored in the $HOME/.kube directory. This file contains the necessary information and credentials to authenticate and communicate with the cluster. These steps enable the DevOps engineer to access and manage the OKE cluster, deploy new applications, and manage existing ones using kubectl or other Kubernetes management tools. Reference:
https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengdownloadkubeconfigfile.htm
質問 # 61
As a DevOps engineer working on an OCI project, you're setting up a deployment pipeline to automate your application deployments. Which statement is false about deployment pipeline in OCI DevOps?
- A. Using deployment pipeline, you can deploy artifacts to Kubernetes cluster, Instance Group, and OCI Compute Instances.
- B. You can add a Wait stage that adds a specified duration of delay in the pipeline.
- C. You can add a Traffic Shift stage that routes the traffic between two sets of backend IPs using preconfigured load balancer and listener.
- D. You can add an Approval stage that pauses the deployment for a specified duration for manual decision from the approver
正解：B
解説：
Explanation
The statement that is false about deployment pipeline in OCI DevOps is that you can add a Wait stage that adds a specified duration of delay in the pipeline. This is not a valid type of stage that you can add to your deployment pipeline. The types of stages that you can add to your deployment pipeline are:
* Deploy stage: A stage that deploys an artifact to a target environment, such as Kubernetes, Instance Group, or Compute Instance.
* Control stage approval: A stage that pauses the pipeline execution and requires manual approval before proceeding to the next stage.
* Traffic shift stage: A stage that routes the traffic between two sets of backend IPs using a preconfigured load balancer and listener.
* Invoke function stage: A stage that invokes an Oracle Function with specified parameters and payload.
Verified References: [Deployment Pipelines - Oracle Cloud Infrastructure DevOps], [Creating Deployment Pipelines - Oracle Cloud Infrastructure DevOps]
質問 # 62
As a small company that wants to adopt a DevOps framework and a consumption-based pricing model, which Oracle Cloud Infrastructure service can be used as a target deployment environment, providing features like automated rollouts and rollbacks, self-healing of failed containers, and configuration management, without the overhead of managing security patches and scaling?
- A. OCI Container Instances
- B. Compute Instance Group
- C. OCI Container Engine for Kubernetes (OKE) with virtual nodes
- D. OCI Serverless Functions
- E. OCI Container Engine for Kubernetes (OKE) with managed nodes
正解：C
解説：
Explanation
The OCI service that can be used as a target deployment environment for adopting a DevOps framework and a consumption-based pricing model, while providing features like automated rollouts and rollbacks, self-healing of failed containers, and configuration management, without the overhead of managing security patches and scaling, is OCI Container Engine for Kubernetes (OKE) with virtual nodes. OKE is a fully managed service that allows you to run and manage your containerized applications on OCI using Kubernetes, an open-source system for automating deployment, scaling, and management of containerized applications. OKE provides features such as automated rollouts and rollbacks, self-healing of failed containers, configuration management, service discovery, load balancing, etc. OKE also supports virtual nodes, which are serverless compute resources that are automatically provisioned and scaled by OCI based on your application workload demands.
Virtual nodes eliminate the need for managing worker node infrastructure, such as security patches, updates, scaling, etc. Virtual nodes also offer a consumption-based pricing model, where you only pay for the resources you consume when your containers are running. Verified References: [Container Engine for Kubernetes - Oracle Cloud Infrastructure Developer Tools], [Virtual Nodes - Oracle Cloud Infrastructure Container Engine for Kubernetes]
質問 # 63
You are working on a DevOps project to deploy Oracle Cloud Infrastructure (OCI) compute instances running web services. The development team indicated that when the compute Instances are deployed, it should automatically create OCI Object Storage buckets with respective instance names. Which two can help you meet this requirement?
- A. Events Service
- B. Oracle Functions
- C. Cloud Agent Plugin for the compute instance
- D. Service Connector Hub
- E. OCI CLI command "oci oj bucket create --auto <value>"
正解：B、C
質問 # 64
You as a DevOps Engineer are asked to manage an application to be deployed in Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE). This requires pulling images from Oracle Cloud Infrastructure Registry (OCIR) during deployment. Which three statements are true? (Choose three.)
- A. Use kubectl to create a Docker registry secret.
- B. Add an image section that specifies the name and location of the images you want to pull from OCIR along with other deployment details.
- C. Add an imagePullSecrets section to the manifest file that specifies the name of the Docker secret you created to access OCIR
- D. Add an Auth section to the manifest file that specifies the name of the Docker secret you create using Auth Token to access OCIR.
- E. Add a containers section that specifies the name and location of the images you want to pull from OCIR.
along with other deployment details.
正解：A、C、E
解説：
Explanation
The three statements that are true regarding managing an application deployed in Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) and pulling images from Oracle Cloud Infra-structure Registry (OCIR) are: Use kubectl to create a Docker registry secret: To access images from OCIR, you need to create a Docker registry secret in Kubernetes. This can be done using the ku-bectl create secret docker-registry command. Add a containers section that specifies the name and location of the images you want to pull from OCIR, along with other deployment details: In your deployment manifest (e.g., YAML file), you need to define a containers section that specifies the image names and locations from OCIR. This section includes other deployment details such as re-source limits and environment variables. Add an imagePullSecrets section to the manifest file that specifies the name of the Docker secret you created to access OCIR: To authenticate and pull images from OCIR, you need to specify the name of the Docker registry secret in the imagePullSecrets section of your manifest file. This ensures that the appropriate credentials are used to authenticate with OCIR and pull the required images. These steps enable your application deployed in OKE to pull the necessary container images from OCIR during deployment, ensuring smooth and secure deployment of your application. Reference:
https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengpullingimagesfromocir.htm
質問 # 65
You're using Oracle Cloud Infrastructure (OCI) DevOps service to automate your software releases to release features more frequently and with fewer errors. While deploying an update to production, one of your deployment stages failed. What action should you perform in your Deployment Pipeline?
- A. Rollback the failed stage in the pipeline to the previous successful released version.
- B. Automate backup and use the rerelease stage in the Deployment Pipeline.
- C. Use OCI DevOps Trigger and Rerun tool to avoid downtime.
- D. Add Rescue and Trigger stages to automatically trigger the failed deployment.
正解：A
解説：
Explanation
In the Deployment Pipeline, when a deployment stage fails during the deployment of an update to production, the recommended action is to: Rollback the failed stage in the pipeline to the previous successful released version. By rolling back the failed stage to the previous successful version, you can revert the deployment to a known stable state and prevent the failed changes from being re-leased to production. This helps to maintain the stability and integrity of the application. It allows you to address the issues encountered in the failed stage, make necessary fixes or adjustments, and then proceed with the deployment again once the issues are resolved.
The other options mentioned are not the most appropriate actions to perform in this scenario: Automating backup and using the rerelease stage: While backups are important for data protection, automating backup and using a rerelease stage would not directly address the failure in the deployment stage. It is more focused on data backup and recovery. Adding Rescue and Trigger stages: Adding Rescue and Trigger stages might help in certain situations, but they are not the primary solution for handling a failed deployment stage. They are more related to error recovery mechanisms or additional deployment steps, rather than specifically addressing the failed stage. Using OCI DevOps Trigger and Rerun tool: While OCI DevOps Trigger and Rerun tool can be useful for automating and managing deployments, it is not specifically designed to handle a failed deployment stage. It is more focused on triggering and rerunning pipelines or stages based on specific conditions or events.
質問 # 66
You are a DevOps engineer working on a project that requires you to push and pull Docker images to and from Oracle Cloud Infrastructure Registry (Container Registry) using Docker CLI. You have been given access to Container Registry and have installed Docker CLI on your local machine. Which should you create and use to securely authenticate and store your Docker image in a private Docker registry in OCI?
- A. Auth Token
- B. JSON Web Token
- C. Master Encryption Key in OCI Vault
- D. SSH Key Pair
- E. Docker Registry Secret
正解：A
解説：
Explanation
To securely authenticate and store your Docker image in a private Docker registry in OCI, you need to create and use an Auth Token. An Auth Token is a secure, encrypted token that you can use to authenticate with OCI services such as Container Registry. You can use the Auth Token as your password when you log in to Container Registry using the Docker CLI. You can also use the Auth Token to access other OCI services such as Object Storage and Compute. Verified References: [Pushing and Pulling Images - Oracle Cloud Infrastructure Registry], [Auth Tokens - Oracle Cloud Infrastructure Identity and Access Management]
質問 # 67
A developer is using the Oracle Cloud Infrastructure (OCI) DevOps service to build an application. They are currently in the process of setting up the required infrastructure using the available tools. In which two ways can you explain the difference between Ansible and Terraform? (Choose two.)
- A. Ansible supports lifecycle management: Terraform lacks lifecycle management support.
- B. Ansible is an OCI provided service for CM; Terraform is a third-party tool for infra-structure as code.
- C. Ansible uses declarative approach: Terraform is procedural in nature.
- D. Ansible automates software installation and application deployment: Terraform man-ages infrastructure as code.
- E. Ansible focuses on infrastructure configuration: Terraform specializes in infrastructure provisioning
正解：D、E
解説：
Explanation
The two correct explanations for the difference between Ansible and Terraform are: Ansible auto-mates software installation and application deployment, while Terraform manages infrastructure as code. This highlights the primary focus of each tool. Ansible is mainly used for automating tasks related to software installation, application deployment, and configuration management. It is well-suited for managing the software stack and ensuring consistency across systems. On the other hand, Terraform specializes in infrastructure provisioning and management, allowing users to define and manage their infrastructure resources using code. Ansible focuses on infrastructure configuration, while Terraform specializes in infrastructure provisioning. This highlights the different aspects of infrastructure management that each tool addresses. Ansible is designed to handle configuration management tasks, such as setting up software, managing files, and applying configuration changes across systems. It excels at ensuring the desired state of the infrastructure. In contrast, Terraform is focused on provisioning infrastructure resources, such as virtual machines, networks, and storage. It provides a way to define and manage these resources in a declarative manner, allowing for infra-structure as code. It's worth noting that while Ansible is supported and provided by OCI as a con-figuration management tool, Terraform is a third-party tool that has gained popularity for managing infrastructure across multiple cloud providers, including OCI.
質問 # 68
A startup is building an application and has decided to deploy it on Oracle Cloud Infrastructure (OCT) DevOps. They want to automate the infrastructure provisioning and con-figuration of OCI resources such as Compute, Load Balancing, and Database services. Which tool should they use for this purpose and why?
- A. Jenkins. In OCI, Jenkins is an automation tool for configuration management that focuses on automating delivery and management of entire IT infrastructure stacks.
- B. Resource Manager. In OCI, the "Resource Manager" automates infrastructure provisioning and configuring of OCI resources, such as Compute, Load Balancing, and Database services.
- C. Splunk. With the OCI DevOps service, users can manage OCI resources using the Splunk Plug- in, a CLI tool that provides help with managing repositories and automating infrastructure.
- D. OCI OKE. In OCI, Container Engine for Kubernetes is a configuration management tool that manages enterprise-scale server infrastructure with minimal human intervention using Infrastructure as Code (IaC).
正解：B
質問 # 69
A software development team is working on a prototype using Node.js and MongoDB as their programming language and database, respectively. They need to develop and test isolated web applications or RESTful APIs. They are looking for a simple, quick, and secure way to run containers without managing any servers.
Which OCI service is best suited for this use case?
- A. Container Instances
- B. OCI DevOps Project
- C. OCI Functions
- D. Container Engine for Kubernetes
- E. Compute Instances
正解：A
解説：
Explanation
The OCI service that is best suited for developing and testing isolated web applications or RESTful APIs using Node.js and MongoDB is Container Instances. Container Instances is a service that allows you to run containers without managing any servers. You can use Container Instances to create and manage single-container or multi-container deployments using Docker images. You can also use Container Instances to connect your containers to other OCI services, such as Object Storage, Database, or Networking. Container Instances is simple, quick, and secure, as it provides built-in isolation, encryption, and authentication for your containers. Verified References: [Container Instances - Oracle Cloud Infrastructure Developer Tools],
[Creating Container Instances - Oracle Cloud Infrastructure Developer Tools]
質問 # 70
You are a DevOps engineer responsible for managing the deployment pipeline of your organization's application hosted on Oracle Cloud Infrastructure (OCI). The pipeline is failing, and you need to troubleshoot the issue to identify the potential cause and fix it. You need the following information to investigate further: - Time spent for each deployment. - Number of times a deployment has failed. Which OCI service can provide you with the necessary information to identify the potential issue and help in debugging the same?
- A. OCI DevOps Agent
- B. OCI Logging service
- C. OCI Event service
- D. OCI Monitoring service
正解：B
解説：
Explanation
The OCI service that can provide you with the necessary information to identify the potential issue and help in debugging the deployment pipeline is OCI Logging service. OCI Logging service is a service that allows you to collect, manage, search, analyze, and monitor logs from your OCI resources and applications. You can use OCI Logging service to view the logs from your build and deployment pipelines, such as the start time, end time, status, output, error messages, etc. You can also use OCI Logging service to filter, query, and export the logs for further analysis or troubleshooting. Verified References: [Logging - Oracle Cloud Infrastructure Developer Tools], [Viewing Logs - Oracle Cloud Infrastructure Developer Tools]
質問 # 71
You are a DevOps engineer who has recently joined a new department. You have created 10 Terraform stacks using Oracle Cloud Infrastructure (OCI) Resource Manager. Each stack creates a different set of resources in OCI for your development team. What determines the cost of these Terraform stacks?
- A. The cost depends on the number of lines of text in your Terraform configuration files.
- B. The cost depends on the length of time it takes to build each resource using these Terraform stacks.
- C. Resource Manager stacks are free but you are charged for the resources they create.
- D. The cost for each stack will be higher for a Pay As You Go subscription than for monthly flex billing.
正解：C
解説：
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.
質問 # 72
You are a DevOps project administrator. You are creating Oracle Cloud Infrastruc-ture (OCI) Identity and Access Management (IAM) policies that will be used in a DevOps CI/CD pipeline for deployment to an Oracle Container Engine for Kubernetes (OKE) environment. Which OCI IAM policy can be used?
- A. Allow group <deployment pipeline> to manage devops-family in compartment <com-partment name>
- B. Allow dynamic-group <code repository> to manage devops-family in compartment <compartment name>
- C. Allow group <build pipeline> to manage all-resources in compartment <compartment name>
- D. Allow dynamic-group <deployment pipeline to manage all-resources in compartment <compartment name>
正解：D
解説：
Explanation
To create an OCI IAM policy that will be used in a DevOps CI/CD pipeline for deployment to an OKE environment, you need to use a dynamic group and grant it the permission to manage all-resources in the target compartment. A dynamic group is a group of OCI resources that match a set of rules defined by the administrator. You can use a dynamic group to assign IAM policies to resources such as build pipelines and deployment pipelines. By granting the dynamic group the permission to manage all-resources, you allow it to perform any action on any resource type in the compartment, including OKE clusters, node pools, and Kubernetes resources. Verified References: [Dynamic Groups - Oracle Cloud Infrastructure Identity and Access Management], [Creating Dynamic Groups - Oracle Cloud Infrastructure Identity and Access Management]
質問 # 73
How can customers rotate their master encryption keys in the Oracle Cloud Infra-structure (OCI) Vault service?
- A. Customers can only have OCI rotate their keys once a year.
- B. If you import your own key, you cannot rotate the key. You will have to import a new key to rotate.
- C. Customers can rotate their keys by creating a new Key Version.
- D. Customers can rotate their keys every 30 days. They may enter a service request (SR) to request a rotation sooner than 30 days since the last rotation.
正解：C
解説：
Explanation
The way that customers can rotate their master encryption keys in the OCI Vault service is by creating a new Key Version. A Key Version is an instance of a Vault managed key that has its own unique OCID and metadata. Customers can create a new Key Version for their Vault managed key at any time, which will generate a new encryption key material for that key. Customers can also specify which Key Version they want to use as the current Key Version for encrypting and decrypting secrets. Verified References: [Rotating Keys - Oracle Cloud Infrastructure Vault], [Creating Key Versions - Oracle Cloud Infrastructure Vault]
質問 # 74
What is the correct approach to upgrade an Oracle Container Engine for Kubernetes (OKE) Cluster to a newer version of Kubernetes?
- A. Upgrade the node pools one at a time, then once all node pools are upgraded, upgrade the control plane.
- B. Initiate the control plane and node pool upgrades simultaneously.
- C. Initiate the automated upgrade process using the OCI Console. CLI, or API.
- D. Upgrade the control plane, then upgrade the node pools.
正解：B
解説：
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:
https://docs.oracle.com/en-us/iaas/Content/ContEng/Concepts/contengaboutupgradingclusters.htm
質問 # 75
As a developer working on a software project to be deployed on OKE, you have created a Helm chart for your application. You want to deploy the chart using OCI DevOps service. Which statement is true about deploying a Helm Chart using OCI DevOps service?
- A. The Helm charts must be located in the OCI Container Registry repository for deployment.
- B. You cannot package and push the Helm chart to the Container Registry from the build pipeline.
- C. The values.yaml file is a generic file located in the OCI Container Registry. You must create a reference to this file.
- D. The Helm Upgrade options cannot be used to change the configuration of the Helm re-lease.
正解：A
解説：
Explanation
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]
質問 # 76
......
2023年最新のFast2test 1z0-1109-23のPDFで最近更新された問題です：https://jp.fast2test.com/1z0-1109-23-premium-file.html