Most Recent Oracle 1Z0-1109-23 Exam Dumps

The statements that are true for scaling an OKE cluster to meet growing demand are:

Enable autoscaling by autoscaling Pods by deploying Kubernetes Autoscaler to collect resource metrics from each worker node in the cluster. Pod autoscaling is a feature that allows you to adjust the number of pods in a deployment or replica set based on the CPU or memory utilization of the pods. You can use Kubernetes Autoscaler, which is an add-on component that you can install on your OKE cluster, to collect resource metrics from each worker node and scale the pods up or down accordingly.

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. Cluster autoscaling is a feature that allows you to adjust the number of nodes in a node pool based on the pod requests and limits of the pods running on the nodes. You can use Kubernetes Autoscaler, which is an add-on component that you can install on your OKE cluster, to monitor the pod requests and limits and scale the node pools up or down accordingly.

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. A node pool is a group of worker nodes within an OKE cluster that share the same configuration, such as shape, image, subnet, etc. You can use OCI Console, CLI, or API to scale a node pool up and down by adding or removing worker nodes from it. You can also change the availability domains and subnets for your node pool to distribute your nodes across different fault domains. Scaling a node pool allows you to adjust your cluster capacity according to your application workload demands. Verified Reference: [Scaling Clusters - Oracle Cloud Infrastructure Container Engine for Kubernetes], [Scaling Node Pools - Oracle Cloud Infrastructure Container Engine for Kubernetes]

The statement that is true about managing cluster add-ons in OCI OKE Cluster is that when creating a new cluster, essential cluster add-ons cannot be disabled. A cluster add-on is a software component that provides additional functionality or integration for your OKE cluster. OCI OKE Cluster supports two types of cluster add-ons: essential and optional. Essential cluster add-ons are required for your cluster to function properly and cannot be disabled or customized. These include CoreDNS, Kubernetes Dashboard, Metrics Server, and WebLogic Operator. Optional cluster add-ons are not required for your cluster to function but provide additional features or benefits. These include Kiali Operator, Istio Operator, Vault Agent Injector, and Vault KMS Plugin. You can enable or disable optional cluster add-ons as per your needs. Verified Reference: [Cluster Add-Ons - Oracle Cloud Infrastructure Container Engine for Kubernetes], [Managing Cluster Add-Ons - Oracle Cloud Infrastructure Container Engine for Kubernetes]

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 Reference: [Deployment Pipelines - Oracle Cloud Infrastructure DevOps], [Creating Deployment Pipelines - Oracle Cloud Infrastructure DevOps]

The command that creates the docker registry secret required in the application manifests for OKE to pull images from OCI Registry is:

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>

This command creates a secret of type docker-registry with the specified name and parameters. The parameters are:

--docker-server: The server URL of OCI Registry in the format <region-key>.ocir.io, where <region-key> is the region identifier such as us-ashburn-1.

--docker-username: The username for OCI Registry in the format <tenancy-namespace>/<oci-username>, where <tenancy-namespace> is the tenancy name or ID and <oci-username> is the OCI user name or ID.

--docker-password: The password for OCI Registry, which is the OCI Auth Token that you can generate from the Console or CLI.

--docker-email: The email address associated with the OCI user.

Verified Reference: [Deploying Applications to Oracle Cloud Infrastructure Container Engine for Kubernetes]