Oracle 1Z0-1093-25 Exam - Topic 1 Question 5 Discussion

Actual exam question for Oracle's 1Z0-1093-25 exam

Question #: 5
Topic #: 1

When considering autoscaling for provisioned throughput in NoSQL Database Cloud Service, which metric is LEAST relevant for determining when to scale up the capacity units?

ACPU utilization of the compute instances hosting the database.

BNumber of rejected read requests due to insufficient RCUs.

CNumber of rejected write requests due to insufficient WCUs.

DLatency of read and write operations.

Show Suggested Answer

Suggested Answer: A

A . CPU utilization of the compute instances hosting the database:

Autoscaling in NoSQL Database Cloud Service primarily focuses on RCUs (Read Capacity Units) and WCUs (Write Capacity Units).

The objective is to dynamically adjust capacity based on query workload, not on CPU utilization.

Even if CPU usage is high, it might not necessarily indicate that the capacity units are inadequate.

Why the other options are more relevant:

B . Rejected read requests (RCUs): Direct indicator that read capacity is insufficient, requiring scaling.

C . Rejected write requests (WCUs): Indicates that the write throughput is inadequate, necessitating scaling.

D . Latency of read and write operations: Increased latency often points to under-provisioned throughput.

Oracle NoSQL Database Cloud Service Documentation: Autoscaling Throughput

by Malissa at Apr 06, 2025, 02:34 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Casie

2 months ago

B and C are way more important for scaling decisions.

upvoted 0 times

...

Jess

3 months ago

Wait, so CPU doesn't matter? That seems odd.

upvoted 0 times

...

Eura

3 months ago

I agree, CPU utilization doesn't directly impact throughput.

upvoted 0 times

...

Jamal

3 months ago

I thought latency would be less relevant too, but I guess not!

upvoted 0 times

...

Cristal

3 months ago

A is definitely the least relevant metric here.

upvoted 0 times

...

Peggie

4 months ago

I have a feeling that CPU utilization doesn't directly impact throughput, so I might lean towards A as the answer.

upvoted 0 times

...

Lynelle

4 months ago

I'm not entirely sure, but I feel like latency could also be a factor in scaling decisions, so that might not be the least relevant.

upvoted 0 times

...

Roosevelt

4 months ago

I remember a practice question where we discussed rejected requests being key indicators for scaling, so maybe options A or D are less important?

upvoted 0 times

...

Rutha

4 months ago

I think CPU utilization might be the least relevant since it's more about the database's read/write capacity, right?

upvoted 0 times

...

Cristy

4 months ago

The question is asking for the LEAST relevant metric, so I'm going to eliminate the ones that are more directly tied to throughput capacity.

upvoted 0 times

...

Yun

5 months ago

I'm a bit confused on this one. I'll need to review the concepts around autoscaling for NoSQL databases before I can confidently answer.

upvoted 0 times

...

Francisca

5 months ago

Okay, I think I've got it. The number of rejected requests due to insufficient capacity units is the key metric here, not the latency.

upvoted 0 times

...

Dorthy

5 months ago

Hmm, CPU utilization doesn't seem directly relevant to scaling throughput. I'm leaning towards one of the request-related metrics.

upvoted 0 times

...

Arleen

5 months ago

This seems like a tricky one. I'll need to think carefully about the different metrics and how they relate to autoscaling.

upvoted 0 times

...

Patrick

10 months ago

I bet the answer is option C. After all, who needs to write data when you can just make it up as you go along? That's the true spirit of the cloud, am I right?

upvoted 0 times

Kenneth

8 months ago

I agree, option D, latency of read and write operations, is also important to consider when deciding to scale up capacity units.

upvoted 0 times

...

Norah

9 months ago

I think the least relevant metric would be option A, CPU utilization. It's more about the read and write operations than the compute instances.

upvoted 0 times

...

Buck

9 months ago

Option C is actually very relevant for determining when to scale up capacity units. Writing data is a crucial operation in a database.

upvoted 0 times

...

Irma

10 months ago

Ah, the age-old question: which metric is the least relevant? I say we just throw a dart at the options and call it a day. That's how I usually approach these things.

upvoted 0 times

Jame

8 months ago

D) Latency of read and write operations.

upvoted 0 times

...

Nieves

8 months ago

C) Number of rejected write requests due to insufficient WCUs.

upvoted 0 times

...

Domonique

8 months ago

B) Number of rejected read requests due to insufficient RCUs.

upvoted 0 times

...

Erasmo

9 months ago

A) CPU utilization of the compute instances hosting the database.

upvoted 0 times

...

Lavonda

10 months ago

Hmm, I'm going with option B. I mean, who even reads these days? Writes are where it's at. Gotta keep those writes flowing!

upvoted 0 times

Adelina

9 months ago

User 3: Agreed, keeping the writes flowing is key. Option B it is.

upvoted 0 times

...

Gilma

9 months ago

User 2: Yeah, writes are definitely more important. Can't have those rejected write requests.

upvoted 0 times

...

Cecilia

9 months ago

User 1: I think option B is the way to go. Reads are so last season.

upvoted 0 times

...

Olive

10 months ago

I'd say option D is the least relevant. Latency? Who cares about that? As long as the data gets in and out, that's all that matters!

upvoted 0 times

Shawna

9 months ago

User 3: I still think latency is not as important as the other metrics. We should focus on throughput.

upvoted 0 times

...

Louann

9 months ago

User 2: I agree with Louann. Latency can impact user experience.

upvoted 0 times

...

Mona

10 months ago

User 1: I think option D is actually important. Latency can affect performance.

upvoted 0 times

...

Thad

10 months ago

But if the CPU is not being fully utilized, why would we need to scale up?

upvoted 0 times

...

Kate

11 months ago

I disagree, I believe latency of read and write operations is the least relevant.

upvoted 0 times

...

Thad

11 months ago

I think CPU utilization is the least relevant metric.

upvoted 0 times

...

Kami

11 months ago

Option A seems like the obvious choice here. I mean, if the CPU is maxed out, that's a pretty clear sign that you need to scale up, right?

upvoted 0 times

Izetta

9 months ago

Latency can also be a crucial factor in determining when to scale up.

upvoted 0 times

...

Rueben

9 months ago

D) Latency of read and write operations.

upvoted 0 times

...

Jerry

9 months ago

Yeah, the number of rejected write requests is also important to consider for scaling up.

upvoted 0 times

...

Franklyn

9 months ago

C) Number of rejected write requests due to insufficient WCUs.

upvoted 0 times

...

Marylin

9 months ago

I think the number of rejected read requests is a good indicator of when to scale up.

upvoted 0 times

...

Alline

9 months ago

B) Number of rejected read requests due to insufficient RCUs.

upvoted 0 times

...

Rosina

10 months ago

D) Latency of read and write operations.

upvoted 0 times

...

Rex

10 months ago

C) Number of rejected write requests due to insufficient WCUs.

upvoted 0 times

...

Antonette

10 months ago

B) Number of rejected read requests due to insufficient RCUs.

upvoted 0 times

...

Timothy

11 months ago

A) CPU utilization of the compute instances hosting the database.

upvoted 0 times

...