Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-1109-23 Topic 8 Question 17 Discussion

Actual exam question for Oracle's 1Z0-1109-23 exam
Question #: 17
Topic #: 8
[All 1Z0-1109-23 Questions]

You host a microservices based application on the Oracle Cloud Infrastructure Con-tainer Engine for Kubernetes (OKE). Due to increased popularity of your application, you need to provision more resources to meet the growing demand. Which three statements are true for the given scenario?

Show Suggested Answer Hide Answer
Suggested Answer: A, B, E

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]


Contribute your Thoughts:

Lang
6 months ago
Yes, that's true. We can ensure optimal resource utilization by making such changes.
upvoted 0 times
...
Gail
6 months ago
Scaling a cluster up and down by changing the number of node pools can also help in managing the resources effectively.
upvoted 0 times
...
Bobbye
6 months ago
I agree with you, It's necessary to automatically resize node pools based on workload demands.
upvoted 0 times
...
Stefan
6 months ago
I think enabling cluster autoscaling by autoscaling node pools is also crucial in this situation.
upvoted 0 times
...
Janey
6 months ago
I agree with that. It's important to scale resources dynamically.
upvoted 0 times
...
Lang
6 months ago
I think we should enable autoscaling by autoscaling Pods to meet the demand.
upvoted 0 times
...
Jerry
6 months ago
Scaling a node pool up and down to adjust the number of worker nodes makes sense to me.
upvoted 0 times
...
Ivan
6 months ago
I prefer using Kubernetes Metrics Server and Vertical Pod Autoscaler for cluster autoscaling.
upvoted 0 times
...
Ming
7 months ago
Scaling a cluster up and down by changing the number of node pools seems crucial.
upvoted 0 times
...
Kimi
7 months ago
I believe enabling cluster autoscaling for node pools is more efficient.
upvoted 0 times
...
Lilli
7 months ago
I think we should enable autoscaling for Pods using Kubernetes Autoscaler.
upvoted 0 times
...
Abraham
8 months ago
Option D is incorrect. The Kubernetes Metrics Server is used for monitoring, not autoscaling. The Vertical Pod Autoscaler adjusts resource requests and limits, not node pools.
upvoted 0 times
...
Charlene
8 months ago
Option C is correct too. We can scale the cluster up and down by adding or removing node pools. This gives us flexibility to adjust the overall cluster capacity.
upvoted 0 times
...
Fabiola
8 months ago
Option B is also correct. We can use the Kubernetes Autoscaler to automatically resize our node pools based on workload demands. This allows the cluster to scale up and down as needed.
upvoted 0 times
Barney
7 months ago
We should also consider enabling autoscaling for Pods to collect resource metrics.
upvoted 0 times
...
Vannessa
7 months ago
That's good to know. It helps in ensuring our application can handle increased traffic.
upvoted 0 times
...
Elli
7 months ago
Option B is correct. We can use the Kubernetes Autoscaler to automatically resize our node pools based on workload demands.
upvoted 0 times
...
...
Aretha
8 months ago
Option A is correct, we can use the Kubernetes Autoscaler to automatically scale pods based on resource metrics. This is useful for scaling out our application as demand increases.
upvoted 0 times
...
Verdell
8 months ago
I agree, this question seems straightforward but it's important to carefully read each option and understand the differences between cluster autoscaling, node pool scaling, and pod autoscaling.
upvoted 0 times
...
Giuseppe
8 months ago
This question is a good test of our understanding of autoscaling and scaling options in OKE. The key is to identify the statements that accurately describe the capabilities available in the given scenario.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77