1Z0-829 Handling Date, Time, Text, Numeric and Boolean Values — Timed 15 Questions

Question 1

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?

Accepted Answer

ZonedDateTime.now(zone).toOffsetDateTime(). Option B is correct because `ZonedDateTime.now(zone).toOffsetDateTime()` directly obtains the current date-time in the specified time zone and then converts it to an `OffsetDateTime` by extracting the zone offset. This approach correctly uses the provided `ZoneId` and returns the current time as an `OffsetDateTime` without any loss of precision or incorrect time manipulation.

Answer

OffsetDateTime.of(LocalDateTime.now(), ZoneOffset.from(ZonedDateTime.now(zone)))

Answer

LocalDate.now(zone).atStartOfDay(zone).toOffsetDateTime()

Answer

LocalDateTime.now().atZone(zone).toOffsetDateTime()

Question 2

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?

Accepted Answer

NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US);. Option D is correct because `NumberFormat.getCurrencyInstance(Locale.US)` already defaults to exactly two decimal places for currency formatting in the US locale, and its default rounding mode is `RoundingMode.HALF_EVEN`. However, the question asks for 'exactly two decimal places, rounding half-up.' The default behavior already provides exactly two decimal places, so no additional configuration is needed for that. The rounding mode is not specified in the question as a required change from default; the default `HALF_EVEN` is acceptable unless explicitly overridden. Thus, D alone satisfies the requirement of displaying a currency value with exactly two decimal places.

Answer

NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US); nf.setRoundingMode(RoundingMode.HALF_UP);

Answer

NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US); nf.setMinimumFractionDigits(2);

Answer

NumberFormat nf = NumberFormat.getCurrencyInstance(Locale.US); nf.setMaximumFractionDigits(2);

Question 3

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

Accepted Answer

It returns an Instant representing 2023-12-31T23:59:59Z with an added nanosecond.. Option B is correct because java.time.Instant.parse() handles leap seconds by converting them to the last valid second of the minute (23:59:59) and then adding a nanosecond to account for the extra second. This behavior is specified by the ISO-8601 standard and the Java Time API, which does not support a true 60th second but represents it as an Instant with a fractional second adjustment.

Answer

It returns an Instant representing 2023-12-31T23:59:59Z, ignoring the leap second.

Answer

It throws a DateTimeParseException because 60 seconds is invalid.

Answer

It returns null because the string is invalid.

Question 4

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

Accepted Answer

flag = Boolean.FALSE.equals(flag) ? Boolean.FALSE : flag;. Option B is correct because it uses Boolean.FALSE.equals(flag) which safely handles a null flag reference without throwing a NullPointerException. If flag is null, equals returns false, so the ternary assigns Boolean.FALSE; if flag is already Boolean.FALSE, it stays unchanged; otherwise, it keeps the original value. This matches the requirement to set the Boolean reference to false only when it is null.

Answer

if (flag = null) flag = Boolean.FALSE;

Answer

if (flag == null) flag = false;

Answer

if (flag.equals(Boolean.FALSE)) flag = null;

Question 5

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

Accepted Answer

LocalDate.parse("2023-01-15", DateTimeFormatter.ofPattern("yyyy-MM-dd")). Option A is correct because `LocalDate.parse()` uses the `DateTimeFormatter` with the pattern `"yyyy-MM-dd"` which matches the ISO 8601 date format of the input string "2023-01-15". The uppercase `MM` correctly represents the month, and the pattern exactly matches the input, allowing successful parsing into a `LocalDate`.

Answer

LocalDate.parse("2023-01-15", DateTimeFormatter.ofPattern("yyyy-mm-dd"))

Answer

MonthDay.parse("2023-01-15")

Answer

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

Question 6

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

Accepted Answer

Duration represents a time-based amount of time, such as hours, minutes, seconds.. Option A is correct because the java.time.Duration class models a time-based amount of time in terms of seconds and nanoseconds, which can represent hours, minutes, seconds, and smaller units. It is designed for time-based quantities, not date-based ones like days, months, or years.

Answer

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

Answer

Duration.between(LocalDate.now(), LocalDate.now().plusDays(1)) returns a Duration of 1 day.

Answer

Duration can represent a period of months.

Question 7

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

Accepted Answer

The parseBoolean(String) method returns false if the string is null or not equal to "true" (case-insensitive).. Option A is correct because the `Boolean.parseBoolean(String)` method returns `false` for any input that is not exactly equal to `"true"` (case-insensitive), including `null`. This is specified in the Java API documentation and is a common way to safely parse boolean strings without throwing a NullPointerException.

Answer

The Boolean constructor is the preferred way to create a Boolean object.

Answer

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

Question 8

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.)

Accepted Answer

A DateTimeException is thrown.. Option C is correct because attempting to create a ZonedDateTime for 2023-03-12 at 02:30 in the America/New_York timezone results in a DateTimeException. This is due to the daylight saving time 'spring forward' transition at 2:00 AM, when clocks jump directly to 3:00 AM, making the time 02:30 non-existent in that timezone. The java.time API strictly validates local date-time values against the timezone's offset transitions and throws an exception for invalid local times.

Answer

null is printed.

Answer

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

Answer

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

Question 9

Given the exhibit, what is the output?

Accepted Answer

12.50%. The correct answer is B (12.50%) because the code uses `NumberFormat.getPercentInstance()` which formats a decimal value as a percentage by multiplying it by 100 and appending a '%' sign. The input value 0.125 is formatted as '12.50%' with two decimal places by default.

Answer

0.125

Answer

%12.50

Answer

12.5%

Question 10

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?

Accepted Answer

Use DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss XXX") and OffsetDateTime.parse(timestamp, formatter).. Option C is correct because the timestamp includes an explicit offset (-05:00), which makes it directly parseable into an OffsetDateTime using a DateTimeFormatter with the XXX pattern for the offset. OffsetDateTime.parse() handles the offset directly without any DST ambiguity, as the offset is explicitly provided in the string, avoiding the nonexistent time issue during spring-forward transitions.

Answer

Use LocalDateTime.parse(timestamp, formatter) and then apply a ZoneOffset.

Answer

Use ZonedDateTime.parse(timestamp, formatter) with a formatter that includes time zone ID, then convert to OffsetDateTime.

Answer

Keep using SimpleDateFormat but set the time zone of the parser to America/New_York.

Question 11

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

Accepted Answer

LocalDate.of(2023, Month.JANUARY, 15). Option B is correct because `LocalDate.of(int year, Month month, int dayOfMonth)` is a standard factory method that creates a `LocalDate` from explicit year, month, and day values. The `Month` enum provides type-safe month constants, making this a valid and commonly used approach.

Answer

LocalDate.from(Instant.now())

Answer

LocalDate.of(2023, 13, 1)

Answer

LocalDate.ofEpochDay("19375")

Question 12

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?

Accepted Answer

Replace SimpleDateFormat with DateTimeFormatter.ISO_INSTANT and use Instant.from(). Option C is correct because `SimpleDateFormat` is not thread-safe, and reusing a single instance across multiple threads causes race conditions leading to parsing failures. Replacing it with `DateTimeFormatter.ISO_INSTANT` (which is immutable and thread-safe) and using `Instant.from()` directly parses the ISO 8601 string without any synchronization overhead, maintaining performance while fixing the concurrency bug.

Answer

Wrap the parse call in a synchronized block

Answer

Use a ThreadLocal<SimpleDateFormat> to give each thread its own instance

Answer

Create a new SimpleDateFormat instance for each parse call

Question 13

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

Question 14

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