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

（A）Enable cluster autoscaling by autoscaling node pools by deploying Kubernetes Metrics Server and using the Kubernetes Vertical Pod Autoscaler to adjust the resource re-quests and limits.

（B）Scale a cluster up and down by changing the number of node pools in the cluster.

（C）Enable cluster autoscaling by autoscaling node pools by deploying the Kubernetes Autoscaler to automatically resize a cluster's node pools based on application workload demands.

（D）Scale a node pool up and down to change the number of worker nodes in the node pool, and the availability domains and subnets in which to place them.

（E）Enable autoscaling by autoscaling Pods by deploying Kubernetes Autoscaler to collect resource metrics from each worker node in the cluster.

（A）Container Registry can be used as a public docker registry, allowing any internet user with the appropriate URL knowledge to pull images from public repositories.

（B）When intending to push images to the root compartment, creating an empty repository in advance is not strictly necessary.

（C）You can create up to 500 repositories in Oracle Cloud Infrastructure Registry, consuming a maximum of
500 GB in total, in every enabled region of your tenancy.

（D）In each region that is enabled for your tenancy, you are charged for stored images and managed OCIR services.

（E）Docker images and manifest lists (also known as multi-architecture images) can be stored in Oracle Cloud Infrastructure Registry as long as they adhere to Open Container Initiative specifications. Helm charts aren't included.

（A）Scanning the image upon ingestion and comparing the image size for changes

（B）Signing the image using the Container Registry CLI and creating an image signature that associates the image with the master encryption key and key version in the Vault service

（C）Deploying a manifest to the Kubernetes cluster that references the container image and its unique hash

（D）Enabling scanning of container images stored in OCI Registry

（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）More than one code repository was assigned to the DevOps project

（B）A deployment Dynamic Group was assigned an incorrect OCID for its compartment.

（C）An administrator created the code repository policy in the parent compartment rather than the main working compartment.

（D）A vault secret has an incorrect OCID assigned to it.

（A）Export packages

（B）Deliver artifacts

（C）Trigger deployment

（D）Managed build

（A）Deploy the application to two separate OCI tenancies to ensure complete isolation be-tween environments.

（B）Use a single OCI region and create two separate Virtual Cloud Networks (VCNs), one for the blue environment and one for the green environment.

（C）Use two separate Oracle Container Engine for Kubernetes (OKE) clusters to ensure complete separation between environments.

（D）Use a single Kubernetes cluster with two node pools, one for the blue environment and one for the green environment.

（A）The VCN hosting the OKE cluster worker nodes needs to have a NAT gateway to access OCIR repositories.

（B）The OKE cluster needs to have a secret with credentials of their OCIR repository and use that secret in the Kubernetes deployment manifest.

（C）They need to add a security list rule for TCP port 22 to connect to the OCIR service.

（D）They need to add IAM credentials for each user that deploys applications to the OKE cluster.

（A）pattern validations for string-type variables

（B）dependency relationships between variables.

（C）information about the application such as its name, description, and version.

（D）a logo for the Resource Manager template

（E）permissions for which OCI users may provision the template

（A）Users can view limited lifecycle phases as needed to assess application performance.

（B）Users can avoid downtime during deployments and automate the complexity of updating applications.

（C）Users can only store code on public repositories and cannot access internal code repositories.

（D）Users can migrate workloads from on-premises, but not from other cloud platforms.