1Z0-829 · topic practice

Handling Date, Time, Text, Numeric and Boolean Values practice questions

Q: How should I use these Handling Date, Time, Text, Numeric and Boolean Values practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Q: Can I practise just Handling Date, Time, Text, Numeric and Boolean Values questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Handling Date, Time, Text, Numeric and Boolean Values domain.

Practise Oracle Certified Professional Java SE 17 Developer 1Z0-829 Handling Date, Time, Text, Numeric and Boolean Values practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

19 questionsDomain: Handling Date, Time, Text, Numeric and Boolean Values

Practice 10 questions Browse domain →

What the exam tests

What to know about Handling Date, Time, Text, Numeric and Boolean Values

Handling Date, Time, Text, Numeric and Boolean Values questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Handling Date, Time, Text, Numeric and Boolean Values exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Handling Date, Time, Text, Numeric and Boolean Values questions

19 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

A developer is writing a method that takes a LocalDate and a ZoneId and returns the current time in that time zone as an OffsetDateTime. Which approach correctly implements this?

Trap 1: OffsetDateTime.of(LocalDateTime.now(),…

Complicated and incorrect; ZoneOffset.from() may throw DateTimeException.

Trap 2: LocalDate.now(zone).atStartOfDay(zone).toOffsetDateTime()

atStartOfDay() returns start of day, not current time.

Trap 3: LocalDateTime.now().atZone(zone).toOffsetDateTime()

LocalDateTime.now() uses system default zone, not the given zone.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
OffsetDateTime.of(LocalDateTime.now(), ZoneOffset.from(ZonedDateTime.now(zone)))
Why wrong: Complicated and incorrect; ZoneOffset.from() may throw DateTimeException.
B
ZonedDateTime.now(zone).toOffsetDateTime()
Gets current instant in given zone and converts to OffsetDateTime.
C
LocalDate.now(zone).atStartOfDay(zone).toOffsetDateTime()
Why wrong: atStartOfDay() returns start of day, not current time.
D
LocalDateTime.now().atZone(zone).toOffsetDateTime()
Why wrong: LocalDateTime.now() uses system default zone, not the given zone.

Full breakdown with real-world context →

Question 2easymultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Which of the following correctly formats a NumberFormat instance to display a currency value for the US locale with exactly two decimal places, rounding half-up?

Trap 1: NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US);…

setRoundingMode is not available on NumberFormat.

Trap 2: NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US);…

Only sets minimum, not maximum; extra digits could appear.

Trap 3: NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US);…

Only sets maximum, not minimum; fewer digits could appear.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US); nf.setRoundingMode(RoundingMode.HALF_UP);
Why wrong: setRoundingMode is not available on NumberFormat.
B
NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US); nf.setMinimumFractionDigits(2);
Why wrong: Only sets minimum, not maximum; extra digits could appear.
C
NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US); nf.setMaximumFractionDigits(2);
Why wrong: Only sets maximum, not minimum; fewer digits could appear.
D
NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US);
Default behavior includes two decimal places and rounding half-up.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

A developer needs to parse the string "2023-12-31T23:59:60Z" (a leap second) into a java.time.Instant. Which statement is true?

Trap 1: It returns an Instant representing 2023-12-31T23:59:59Z, ignoring…

Leap second is not ignored; it is handled.

Trap 2: It throws a DateTimeParseException because 60 seconds is invalid.

Instant.parse handles leap seconds.

Trap 3: It returns null because the string is invalid.

It returns an Instant, not null.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
It returns an Instant representing 2023-12-31T23:59:59Z, ignoring the leap second.
Why wrong: Leap second is not ignored; it is handled.
B
It returns an Instant representing 2023-12-31T23:59:59Z with an added nanosecond.
The 60th second is treated as the last nanosecond of the minute.
C
It throws a DateTimeParseException because 60 seconds is invalid.
Why wrong: Instant.parse handles leap seconds.
D
It returns null because the string is invalid.
Why wrong: It returns an Instant, not null.

Full breakdown with real-world context →

Question 4easymultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

A method receives a Boolean reference and must set it to false if null. Which code accomplishes this correctly?

Trap 1: if (flag = null) flag = Boolean.FALSE;

Assignment instead of comparison; also unboxing null throws NPE.

Trap 2: if (flag == null) flag = false;

Autounboxing null to boolean throws NullPointerException.

Trap 3: if (flag.equals(Boolean.FALSE)) flag = null;

Throws NullPointerException if flag is null; logic reversed.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
if (flag = null) flag = Boolean.FALSE;
Why wrong: Assignment instead of comparison; also unboxing null throws NPE.
B
flag = Boolean.FALSE.equals(flag) ? Boolean.FALSE : flag;
Uses equals() safely; if flag is null, equals returns false, so ternary sets to false.
C
if (flag == null) flag = false;
Why wrong: Autounboxing null to boolean throws NullPointerException.
D
if (flag.equals(Boolean.FALSE)) flag = null;
Why wrong: Throws NullPointerException if flag is null; logic reversed.

Full breakdown with real-world context →

Question 5mediummultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Which of the following correctly uses DateTimeFormatter to parse the date "2023-01-15" into a LocalDate?

Trap 1: LocalDate.parse("2023-01-15",…

mm is minutes, not months.

Trap 2: MonthDay.parse("2023-01-15")

MonthDay expects format --MM-dd.

Trap 3: LocalDate.parse("2023-01-15", DateTimeFormatter.ISO_LOCAL_DATE)

ISO_LOCAL_DATE is the correct constant, but the given constant name is wrong.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
LocalDate.parse("2023-01-15", DateTimeFormatter.ofPattern("yyyy-MM-dd"))
Correct pattern and method.
B
LocalDate.parse("2023-01-15", DateTimeFormatter.ofPattern("yyyy-mm-dd"))
Why wrong: mm is minutes, not months.
C
MonthDay.parse("2023-01-15")
Why wrong: MonthDay expects format --MM-dd.
D
LocalDate.parse("2023-01-15", DateTimeFormatter.ISO_LOCAL_DATE)
Why wrong: ISO_LOCAL_DATE is the correct constant, but the given constant name is wrong.

Full breakdown with real-world context →

Question 6hardmulti select

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Which TWO statements are true about the java.time.Duration class? (Choose two.)

Trap 1: Duration.ofDays(1) returns a Duration that is daylight-saving-safe.

Duration is fixed 24 hours, not DST-aware.

Trap 2: Duration.between(LocalDate.now(), LocalDate.now().plusDays(1))…

Duration.between requires temporals that support seconds; LocalDate does not.

Trap 3: Duration can represent a period of months.

Period represents months, not Duration.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
Duration represents a time-based amount of time, such as hours, minutes, seconds.
Duration is based on seconds/nanoseconds.
B
Duration.ofDays(1) returns a Duration that is daylight-saving-safe.
Why wrong: Duration is fixed 24 hours, not DST-aware.
C
Duration.between(LocalDate.now(), LocalDate.now().plusDays(1)) returns a Duration of 1 day.
Why wrong: Duration.between requires temporals that support seconds; LocalDate does not.
D
Duration can represent a period of months.
Why wrong: Period represents months, not Duration.
E
Duration can be negative.
Duration can be negative.

Full breakdown with real-world context →

Question 7mediummulti select

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Which THREE statements are true about the Boolean class? (Choose three.)

Trap 1: The Boolean constructor is the preferred way to create a Boolean…

Boolean constructor is deprecated; valueOf is preferred.

Trap 2: Boolean has three possible values: true, false, and null.

Boolean is an object wrapper; it can be null, but the boolean primitive has only two values.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
The parseBoolean(String) method returns false if the string is null or not equal to "true" (case-insensitive).
parseBoolean returns false for non-matching strings.
B
The Boolean constructor is the preferred way to create a Boolean object.
Why wrong: Boolean constructor is deprecated; valueOf is preferred.
C
Boolean.TRUE and Boolean.FALSE are static constants.
Yes, they are predefined static final instances.
D
The valueOf(String) method returns Boolean.TRUE or Boolean.FALSE without creating a new instance.
valueOf returns cached constants.
E
Boolean has three possible values: true, false, and null.
Why wrong: Boolean is an object wrapper; it can be null, but the boolean primitive has only two values.

Full breakdown with real-world context →

Question 8hardmultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Given the exhibit, what is the output? (Assume America/New_York observes daylight saving time, with spring forward on March 12, 2023 at 2:00 AM to 3:00 AM.)

Exhibit

Refer to the exhibit.

DateTimeFormatter formatter = DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss");
ZonedDateTime zdt = ZonedDateTime.parse("2023-03-12 02:30:00 America/New_York", formatter);
System.out.println(zdt);

Trap 1: null is printed.

An exception is thrown, not null.

Trap 2: 2023-03-12T03:30:00-04:00[America/New_York]

Would be if the time existed after spring forward? Actually 02:30 would become 03:30? But parsing fails.

Trap 3: 2023-03-12T02:30:00-05:00[America/New_York]

Would be before spring forward, but the time is after 2:00.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
null is printed.
Why wrong: An exception is thrown, not null.
B
2023-03-12T03:30:00-04:00[America/New_York]
Why wrong: Would be if the time existed after spring forward? Actually 02:30 would become 03:30? But parsing fails.
C
A DateTimeException is thrown.
The time 02:30 does not exist due to DST gap.
D
2023-03-12T02:30:00-05:00[America/New_York]
Why wrong: Would be before spring forward, but the time is after 2:00.

Full breakdown with real-world context →

Question 9mediummultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Given the exhibit, what is the output?

Exhibit

Refer to the exhibit.

Locale locale = new Locale("en", "US");
NumberFormat nf = NumberFormat.getPercentInstance(locale);
nf.setMinimumFractionDigits(2);
System.out.println(nf.format(0.125));

Trap 1: 0.125

Percent instance multiplies by 100.

Trap 2: %12.50

US locale places percent sign after the number.

Trap 3: 12.5%

Minimum fraction digits override default; two digits required.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
0.125
Why wrong: Percent instance multiplies by 100.
B
12.50%
Formatted as percent with two decimal places.
C
%12.50
Why wrong: US locale places percent sign after the number.
D
12.5%
Why wrong: Minimum fraction digits override default; two digits required.

Full breakdown with real-world context →

Question 10hardmultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

A company's Java application processes time-sensitive data from IoT sensors. The system must handle timestamps across multiple time zones. The application runs on a server set to UTC. Developers have been using java.util.Date and SimpleDateFormat for date parsing. Recently, there have been intermittent failures where timestamps from sensors in the America/New_York time zone are parsed incorrectly around daylight saving time transitions. Specifically, during the spring forward (March 12, 2023, at 2:00 AM EST to 3:00 AM EDT), timestamps like "2023-03-12 02:30:00" are being interpreted as times that do not exist, causing DateTimeParseException. The team decides to migrate to the java.time API. They need to parse sensor timestamps that include a time zone offset (e.g., "2023-03-12 02:30:00 -05:00") into an OffsetDateTime. Which course of action correctly parses the timestamp and handles the DST issue?

Trap 1: Use LocalDateTime.parse(timestamp, formatter) and then apply a…

LocalDateTime has no offset; would not correctly represent the instant.

Trap 2: Use ZonedDateTime.parse(timestamp, formatter) with a formatter that…

ZonedDateTime.parse expects zone ID, not offset; and may still throw exception for invalid local times.

Trap 3: Keep using SimpleDateFormat but set the time zone of the parser to…

SimpleDateFormat does not handle DST gaps properly.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
Use LocalDateTime.parse(timestamp, formatter) and then apply a ZoneOffset.
Why wrong: LocalDateTime has no offset; would not correctly represent the instant.
B
Use ZonedDateTime.parse(timestamp, formatter) with a formatter that includes time zone ID, then convert to OffsetDateTime.
Why wrong: ZonedDateTime.parse expects zone ID, not offset; and may still throw exception for invalid local times.
C
Use DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss XXX") and OffsetDateTime.parse(timestamp, formatter).
Correctly parses a timestamp with offset into OffsetDateTime, avoiding DST ambiguity.
D
Keep using SimpleDateFormat but set the time zone of the parser to America/New_York.
Why wrong: SimpleDateFormat does not handle DST gaps properly.

Full breakdown with real-world context →

Question 11easymulti select

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Which TWO of the following are valid ways to create a LocalDate object in Java 17?

Trap 1: LocalDate.from(Instant.now())

Cannot derive LocalDate from Instant directly.

Trap 2: LocalDate.of(2023, 13, 1)

Month 13 is invalid.

Trap 3: LocalDate.ofEpochDay("19375")

ofEpochDay expects long, not String.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
LocalDate.from(Instant.now())
Why wrong: Cannot derive LocalDate from Instant directly.
B
LocalDate.of(2023, Month.JANUARY, 15)
Valid overload with Month enum.
C
LocalDate.of(2023, 13, 1)
Why wrong: Month 13 is invalid.
D
LocalDate.parse("2023-01-15")
Valid ISO-8601 parse.
E
LocalDate.ofEpochDay("19375")
Why wrong: ofEpochDay expects long, not String.

Full breakdown with real-world context →

Question 12hardmultiple choice

Read the full NAT/PAT explanation →

A financial application uses Java SE 17 with a custom date format. The requirement is to parse strings like "2023-12-31T23:59:59.999Z" into an Instant. The existing code uses SimpleDateFormat with pattern "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'" and then calls parse(). It works fine in single-threaded testing, but in production under load, intermittent parsing failures occur with DateTimeParseException or wrong values. The application is multi-threaded and reuses the same formatter instance. Which single change should be made to fix the issue while maintaining performance?

Trap 1: Wrap the parse call in a synchronized block

Thread-safe but causes contention, reducing performance.

Trap 2: Use a ThreadLocal<SimpleDateFormat> to give each thread its own…

Works but is more complex and less performant than using DateTimeFormatter.

Trap 3: Create a new SimpleDateFormat instance for each parse call

Avoids thread safety but creates many objects, hurting performance.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
Wrap the parse call in a synchronized block
Why wrong: Thread-safe but causes contention, reducing performance.
B
Use a ThreadLocal<SimpleDateFormat> to give each thread its own instance
Why wrong: Works but is more complex and less performant than using DateTimeFormatter.
C
Replace SimpleDateFormat with DateTimeFormatter.ISO_INSTANT and use Instant.from()
Thread-safe and correct for ISO 8601.
D
Create a new SimpleDateFormat instance for each parse call
Why wrong: Avoids thread safety but creates many objects, hurting performance.

Full breakdown with real-world context →

Question 13mediumdrag order

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Arrange the steps to create a custom exception class in Java in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 14mediumdrag order

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Arrange the steps to use a lambda expression to sort a list of strings by length.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 15mediummatching

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Match each Java keyword to its primary purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Prevents serialization of a field

Ensures visibility of changes across threads

Controls access to a block or method by threads

Ensures consistent floating-point behavior across platforms

Indicates a method is implemented in platform-dependent code

Question 16mediummatching

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Match each annotation to its retention policy.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

SOURCE

RUNTIME

SOURCE

RUNTIME

Question 17easymultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

A developer needs to parse a date string '2024-07-04' into a LocalDate object. Which approach is correct?

Trap 1: LocalDate.of(2024, 07, 04)

Incorrect: Leading zeros are allowed but method expects int values; however parse is the standard approach.

Trap 2: DateFormat.getDateInstance().parse("2024-07-04")

Incorrect: DateFormat returns a java.util.Date, not LocalDate, and is outdated.

Trap 3: new LocalDate(2024, 7, 4)

Incorrect: LocalDate has no public constructor; use of() or parse() instead.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
LocalDate.of(2024, 07, 04)
Why wrong: Incorrect: Leading zeros are allowed but method expects int values; however parse is the standard approach.
B
DateFormat.getDateInstance().parse("2024-07-04")
Why wrong: Incorrect: DateFormat returns a java.util.Date, not LocalDate, and is outdated.
C
LocalDate.parse("2024-07-04")
Correct: LocalDate.parse uses the ISO_LOCAL_DATE format by default.
D
new LocalDate(2024, 7, 4)
Why wrong: Incorrect: LocalDate has no public constructor; use of() or parse() instead.

Full breakdown with real-world context →

Question 18easymultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Which method checks if a String is empty or contains only whitespace?

Trap 1: length() == 0

Incorrect: Only checks if the string is empty, not whitespace-only.

Trap 2: isEmpty()

Incorrect: isEmpty() only returns true if length is 0, not for whitespace-only strings.

Trap 3: trim().isEmpty()

Incorrect: This works but is not a direct method and is less efficient.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
isBlank()
Correct: isBlank() returns true if the string is empty or contains only whitespace characters.
B
length() == 0
Why wrong: Incorrect: Only checks if the string is empty, not whitespace-only.
C
isEmpty()
Why wrong: Incorrect: isEmpty() only returns true if length is 0, not for whitespace-only strings.
D
trim().isEmpty()
Why wrong: Incorrect: This works but is not a direct method and is less efficient.

Full breakdown with real-world context →

Question 19easymultiple choice

Read the full Handling Date, Time, Text, Numeric and Boolean Values explanation →

Which of the following correctly creates a text block in Java?

Trap 1: "line1\nline2"

Incorrect: This is a regular string with escape sequence, not a text block.

Trap 2: 'line1\nline2'

Incorrect: Single quotes are not valid for strings in Java.

Trap 3: """line1\nline2"""

Incorrect: Text blocks must start on a new line after the opening delimiter; escapes are not needed.

Study all Handling Date, Time, Text, Numeric and Boolean Values common traps →

A
"line1\nline2"
Why wrong: Incorrect: This is a regular string with escape sequence, not a text block.
B
"""line1 line2"""
Correct: Text block spans multiple lines and preserves indentation.
C
'line1\nline2'
Why wrong: Incorrect: Single quotes are not valid for strings in Java.
D
"""line1\nline2"""
Why wrong: Incorrect: Text blocks must start on a new line after the opening delimiter; escapes are not needed.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Handling Date, Time, Text, Numeric and Boolean Values sessions

Start a Handling Date, Time, Text, Numeric and Boolean Values only practice session

Every question in these sessions is drawn from the Handling Date, Time, Text, Numeric and Boolean Values domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Handling Date, Time, Text, Numeric and Boolean Values questions →Mixed 1Z0-829 session

Frequently asked questions

What does the 1Z0-829 exam test about Handling Date, Time, Text, Numeric and Boolean Values?: Handling Date, Time, Text, Numeric and Boolean Values questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Handling Date, Time, Text, Numeric and Boolean Values questions in a focused session?: Yes — the session launcher on this page draws every question from the Handling Date, Time, Text, Numeric and Boolean Values domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other 1Z0-829 topics?: Use the topic links above to move to related areas, or go back to the 1Z0-829 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the 1Z0-829 exam covers. They are not copied from any real exam or dump site.

Handling Date, Time, Text, Numeric and Boolean Values only

10 questions 20 questions 30 questions 50 questions

Mixed 1Z0-829 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All 1Z0-829 questions Handling Date, Time, Text, Numeric and Boolean Values domain overview 1Z0-829 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Handling Date, Time, Text, Numeric and Boolean Values practice questions

What to know about Handling Date, Time, Text, Numeric and Boolean Values

Common Handling Date, Time, Text, Numeric and Boolean Values exam traps

Handling Date, Time, Text, Numeric and Boolean Values questions

A developer is writing a method that takes a LocalDate and a ZoneId and returns the current time in that time zone as an OffsetDateTime. Which approach correctly implements this?

Which of the following correctly formats a NumberFormat instance to display a currency value for the US locale with exactly two decimal places, rounding half-up?

A developer needs to parse the string "2023-12-31T23:59:60Z" (a leap second) into a java.time.Instant. Which statement is true?

A method receives a Boolean reference and must set it to false if null. Which code accomplishes this correctly?

Which of the following correctly uses DateTimeFormatter to parse the date "2023-01-15" into a LocalDate?

Which TWO statements are true about the java.time.Duration class? (Choose two.)

Which THREE statements are true about the Boolean class? (Choose three.)

Given the exhibit, what is the output? (Assume America/New_York observes daylight saving time, with spring forward on March 12, 2023 at 2:00 AM to 3:00 AM.)

Exhibit

Given the exhibit, what is the output?

Exhibit

Which TWO of the following are valid ways to create a LocalDate object in Java 17?

Arrange the steps to create a custom exception class in Java in the correct order.

Arrange the steps to use a lambda expression to sort a list of strings by length.

Match each Java keyword to its primary purpose.

Match each annotation to its retention policy.

A developer needs to parse a date string '2024-07-04' into a LocalDate object. Which approach is correct?

Which method checks if a String is empty or contains only whitespace?

Which of the following correctly creates a text block in Java?

Track your progress over time

Start a Handling Date, Time, Text, Numeric and Boolean Values only practice session

Related 1Z0-829 topic practice pages