Question 281 of 509
Arrays and MethodsmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to cast `sum` to `double` before division, changing `sum / numbers.length` to `(double) sum / numbers.length`. This fix is necessary because the original code performs integer division in the average method: both `sum` and `numbers.length` are integers, so Java truncates the fractional part, yielding a whole number instead of a precise double. For the array {10, 20, 30}, the correct average is 20.0, and while integer division coincidentally returns 20, the error becomes obvious with values like {10, 20, 31}, where the true average 20.333... would be incorrectly truncated to 20. On the Oracle Java Foundations 1Z0-811 exam, this question tests your understanding of type promotion and the common trap of forgetting that dividing two integers always produces an integer result, even when assigned to a double. A reliable memory tip: when computing averages, always cast one operand to double first—think "double before divide" to preserve the decimal.

1Z0-811 Arrays and Methods Practice Question

This 1Z0-811 practice question tests your understanding of arrays and methods. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A method 'public static double average(int[] numbers) { int sum = 0; for (int i = 0; i < numbers.length; i++) sum += numbers[i]; return sum / numbers.length; }' is called with array {10, 20, 30}. What change is needed to return the correct average?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Change 'sum / numbers.length' to '(double) sum / numbers.length'

The method performs integer division because both `sum` (int) and `numbers.length` (int) are integers, truncating the fractional part. Casting `sum` to `double` before division forces floating-point arithmetic, preserving the decimal value. For the array {10, 20, 30}, the correct average is 20.0, but integer division yields 20 (truncated from 20.0, though here it matches by coincidence; for non-integer averages like {10, 20, 31}, the error would be obvious).

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Change the loop to for (int i = 1; i <= numbers.length; i++)

    Why it's wrong here

    Loop index is off-by-one and does not solve division issue.

  • Change 'sum / numbers.length' to '(double) sum / numbers.length'

    Why this is correct

    Ensures floating-point division.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Change return type to int

    Why it's wrong here

    Still integer division, and average may be fractional.

  • Add a second parameter for the length

    Why it's wrong here

    Unnecessary and changes signature.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Oracle often tests the distinction between integer and floating-point division in Java, trapping candidates who overlook that dividing two ints always truncates the decimal, even when assigned to a double variable or returned from a double method.

Detailed technical explanation

How to think about this question

In Java, binary numeric promotion occurs for arithmetic operators: if both operands are integers, the result is an integer type (int, long, etc.). Casting one operand to `double` triggers widening primitive conversion, promoting the other operand to `double` as well, yielding a `double` result. This is a common pitfall in data analysis or scientific computing where precision matters, such as calculating mean temperatures or sensor readings.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the 1Z0-811 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related 1Z0-811 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free 1Z0-811 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this 1Z0-811 question test?

Arrays and Methods — This question tests Arrays and Methods — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Change 'sum / numbers.length' to '(double) sum / numbers.length' — The method performs integer division because both `sum` (int) and `numbers.length` (int) are integers, truncating the fractional part. Casting `sum` to `double` before division forces floating-point arithmetic, preserving the decimal value. For the array {10, 20, 30}, the correct average is 20.0, but integer division yields 20 (truncated from 20.0, though here it matches by coincidence; for non-integer averages like {10, 20, 31}, the error would be obvious).

What should I do if I get this 1Z0-811 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This 1Z0-811 practice question is part of Courseiva's free Oracle certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 1Z0-811 exam.