Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Oracle Exam 1Z0-1119-1 Topic 1 Question 15 Discussion

Actual exam question for Oracle's 1Z0-1119-1 exam
Question #: 15
Topic #: 1
[All 1Z0-1119-1 Questions]

You observe that during peak hours, the resources used in Sunbird ED are not enough for the deployed microservices. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

Using the Kubernetes Cluster Autoscaler with OCI Container Engine for Kubernetes (OKE) is an effective way to dynamically adjust the resources allocated for containerized workloads based on demand. This ensures that during peak hours, additional resources are automatically provisioned to accommodate the increased load, thereby maintaining performance and availability.


by Peter at Jun 22, 2024, 06:08 AM

Limited Time Offer

25%

Off

Get Premium 1Z0-1119-1 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Tawny
11 months ago
I'd go with Option B. Kubernetes Cluster Autoscaler is designed for this kind of scenario. Plus, it's always fun to watch the pods multiply like bunnies during peak hours.
upvoted 0 times
...
Shaniqua
11 months ago
I think both options could work, but the Autoscaler might be more dynamic in adjusting resources.
upvoted 0 times
...
Venita
11 months ago
But wouldn't creating Instance Pools for the VMs also help in managing resources efficiently?
upvoted 0 times
...
Tammy
11 months ago
Option D, creating Volume Groups for the VMs? Sounds a bit overkill, don't you think? We need a more scalable solution here.
upvoted 0 times
Beatriz
9 months ago
Option D might be overkill, but it could still be a viable option depending on the specific needs of the system.
upvoted 0 times
...
Fernanda
9 months ago
B) Use the Kubernetes Cluster Autoscaler in (XI Container Engine for Kubernetes.
upvoted 0 times
...
Isabelle
10 months ago
A) Create Instance Pools for the virtual machines (VMs) that run the non-containerized workload.
upvoted 0 times
...
Yuriko
10 months ago
B) Use the Kubernetes Cluster Autoscaler in (XI Container Engine for Kubernetes.
upvoted 0 times
...
Mariko
10 months ago
Option D might be overkill. We need a scalable solution.
upvoted 0 times
...
Felton
11 months ago
B) Use the Kubernetes Cluster Autoscaler in (XI Container Engine for Kubernetes.
upvoted 0 times
...
Lavelle
11 months ago
A) Create Instance Pools for the virtual machines (VMs) that run the non-containerized workload.
upvoted 0 times
...
...
Louvenia
11 months ago
I agree with Roslyn, it will automatically adjust resources based on demand.
upvoted 0 times
...
Gayla
11 months ago
Hmm, Option C about Auto-Tiering the Object Storage bucket doesn't seem relevant to the question. That's more for data management, not resource scaling.
upvoted 0 times
...
Albina
11 months ago
I'm not sure about Option A. Creating Instance Pools for non-containerized workloads might not be the most efficient approach in this case.
upvoted 0 times
Noel
11 months ago
B) Use the Kubernetes Cluster Autoscaler in (XI Container Engine for Kubernetes.
upvoted 0 times
...
Bulah
11 months ago
A) Create Instance Pools for the virtual machines (VMs) that run the non-containerized workload.
upvoted 0 times
...
...
Roslyn
12 months ago
I think we should use the Kubernetes Cluster Autoscaler.
upvoted 0 times
...
Magdalene
12 months ago
Option B seems like the way to go. Kubernetes Cluster Autoscaler should be able to handle the peak hour workload automatically.
upvoted 0 times
Jerilyn
11 months ago
Yeah, that sounds like the best option to handle the peak hour workload automatically.
upvoted 0 times
...
Annita
11 months ago
I think we should use the Kubernetes Cluster Autoscaler.
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