Why logging matters in Spring Boot - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to log an info message in a Spring Boot application.

Spring Boot

logger.[1]("Application started successfully.");

Drag options to blanks, or click blank then click option'

Ainfo

Bdebug

Cwarn

Derror

Attempts:

3 left

💡 Hint

Common Mistakes

Using debug instead of info for general messages

Using error for normal startup messages

The info method logs informational messages, which are useful for general application events like startup.

2fill in blank

medium

Complete the code to create a logger instance in a Spring Boot class.

Spring Boot

private static final Logger logger = LoggerFactory.[1](MyApplication.class);

Drag options to blanks, or click blank then click option'

AbuildLogger

BcreateLogger

CnewLogger

DgetLogger

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like createLogger

Confusing with constructor calls

The getLogger method from LoggerFactory creates a logger for the given class.

3fill in blank

hard

Fix the error in the logging statement to correctly log an error message with an exception.

Spring Boot

logger.[1]("Failed to process request", e);

Drag options to blanks, or click blank then click option'

Awarn

Bdebug

Cerror

Dinfo

Attempts:

3 left

💡 Hint

Common Mistakes

Using warn or info instead of error for exceptions

Using debug which is too low level

The error method is used to log error messages along with exceptions.

4fill in blank

hard

Fill both blanks to log a warning message only if the variable 'user' is null.

Spring Boot

if ([1] == null) {
    logger.[2]("User object is null");
}

Drag options to blanks, or click blank then click option'

Auser

Binfo

Cwarn

DuserId

Attempts:

3 left

💡 Hint

Common Mistakes

Checking wrong variable

Using info instead of warn for warnings

Check if user is null, then log a warning with warn method.

5fill in blank

hard

Fill all three blanks to create a log message with the user's name and age using placeholders.

Spring Boot

logger.[1]("User {} is {} years old", [2], [3]);

Drag options to blanks, or click blank then click option'

Ainfo

BuserName

CuserAge

Ddebug

Attempts:

3 left

💡 Hint

Common Mistakes

Using debug instead of info

Swapping the order of variables

Not using placeholders properly

Use info to log the message, and pass userName and userAge as parameters for placeholders.

Practice

1. Why is logging important in a Spring Boot application?

easy

A. It improves the speed of the application.

B. It automatically fixes bugs in the code.

C. It helps track what the application is doing and find problems.

D. It replaces the need for testing.

Solution

1. Step 1: Understand the purpose of logging

   Logging records events and actions in the application, showing what is happening internally.

2. Step 2: Identify the benefit of logging

   It helps developers find and fix problems by providing detailed information about the app's behavior.

3. Final Answer:

   It helps track what the application is doing and find problems. -> Option C

4. Quick Check:

   Logging shows app activity [OK]

Hint: Logging tracks app actions and errors clearly [OK]

Common Mistakes:

• Thinking logging fixes bugs automatically
• Confusing logging with performance improvement
• Believing logging replaces testing

2. Which of the following is the correct way to log an info message in Spring Boot using SLF4J?

easy

A. logger.info("Application started successfully");

B. logger.logInfo("Application started successfully");

C. logger.printInfo("Application started successfully");

D. logger.writeInfo("Application started successfully");

Solution

1. Step 1: Recall SLF4J logging syntax

   The SLF4J logger uses methods like info(), debug(), error() to log messages at different levels.

2. Step 2: Identify the correct method name

   The correct method to log an info message is info(), so logger.info("message") is correct.

3. Final Answer:

   logger.info("Application started successfully"); -> Option A

4. Quick Check:

   SLF4J info method = info() [OK]

Hint: Use logger.info() for info messages in Spring Boot [OK]

Common Mistakes:

• Using incorrect method names like logInfo or printInfo
• Confusing logging methods with print statements
• Missing parentheses after method name

3. Given the following Spring Boot code snippet, what will be the output if the log level is set to WARN?

logger.info("Info message");
logger.warn("Warning message");
logger.error("Error message");

medium

A. No output

B. Info message, Warning message, Error message

C. Error message only

D. Warning message, Error message

Solution

1. Step 1: Understand log level filtering

   When log level is set to WARN, only messages with level WARN and ERROR (higher severity) are shown.

2. Step 2: Identify which messages appear

   Info messages are below WARN level, so they are ignored. Warning and error messages are shown.

3. Final Answer:

   Warning message, Error message -> Option D

4. Quick Check:

   Log level WARN shows WARN and ERROR [OK]

Hint: Log level filters out lower severity messages [OK]

Common Mistakes:

• Expecting info messages to appear at WARN level
• Confusing log levels order
• Assuming all messages always print

4. You see no logs appearing in your Spring Boot console even though you added logger.info("Starting app");. What is the most likely cause?

medium

A. The log level is set higher than INFO, so info messages are hidden.

B. The logger.info() method is misspelled.

C. Spring Boot does not support logging by default.

D. The application has no internet connection.

Solution

1. Step 1: Check log level configuration

   If the log level is set to WARN or ERROR, info messages will not show in the console.

2. Step 2: Rule out other causes

   Logger method spelling is correct, Spring Boot supports logging by default, and internet connection does not affect logging.

3. Final Answer:

   The log level is set higher than INFO, so info messages are hidden. -> Option A

4. Quick Check:

   Log level hides lower severity logs [OK]

Hint: Check log level if logs don't appear [OK]

Common Mistakes:

• Assuming logging needs extra setup always
• Blaming internet connection for logging issues
• Ignoring log level settings

5. You want to log an error with a message and the exception stack trace in Spring Boot. Which code snippet correctly does this?

hard

A. logger.warn("Error occurred", exception);

B. logger.error("Error occurred", exception);

C. logger.info("Error occurred" + exception);

D. logger.error(exception);

Solution

1. Step 1: Understand logging exceptions

   To log an error with stack trace, use logger.error(message, throwable) method.

2. Step 2: Identify correct usage

   logger.error("Error occurred", exception); passes both a message and the exception object, so it logs the message and stack trace properly.

3. Step 3: Rule out other options

   Other options are incorrect: logging only the exception misses the message, using warn level is less severe than error, using info level and string concatenation does not properly log the stack trace.

4. Final Answer:

   logger.error("Error occurred", exception); -> Option B

5. Quick Check:

   Use logger.error(message, exception) for errors [OK]

Hint: Use logger.error(msg, exception) to log errors with stack trace [OK]

Common Mistakes:

• Logging exceptions as strings instead of passing throwable
• Using wrong log level for errors
• Omitting the error message