Why configuration matters in Spring Boot - Challenge Your Understanding

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Spring Boot use configuration files?

Consider a Spring Boot application with an application.properties file setting server.port=8081. What happens when you run the app?

A The app runs on port 8081 instead of the default 8080.

B The app ignores the property and runs on port 8080.

C The app throws an error because the port must be set in code.

D The app runs on a random port each time.

💡 Hint

Spring Boot reads configuration files to set properties like ports.

Spring Boot reads application.properties at startup and applies settings like server.port. This changes the port the app listens on.

❓ state_output

intermediate

What is the value of a bean property from configuration?

Given a Spring Boot bean with @Value("${app.name}") and app.name=MyApp in application.properties, what is the value of the bean's property after startup?

A null

B "${app.name}"

C "MyApp"

D Throws an exception

💡 Hint

Spring Boot replaces placeholders with values from configuration files.

The @Value annotation injects the value from the configuration file. So the property becomes "MyApp".

📝 Syntax

advanced

Which configuration syntax correctly sets a list property in Spring Boot YAML?

You want to set a list of servers in application.yml. Which option is correct?

A servers: [server1, server2, server3]

B

servers:
  - server1
  - server2
  - server3

C servers: {server1, server2, server3}

D servers: server1, server2, server3

💡 Hint

YAML uses dashes for list items.

In YAML, lists are defined with dashes before each item. Option B uses this correct syntax.

🔧 Debug

advanced

Why does this Spring Boot app fail to load configuration?

Given application.properties with myapp.timeout=30 and a bean with @Value("${myapp.timeout}") private int timeout;, the app throws a NumberFormatException. Why?

A The bean field is private and not accessible for injection.

B The property value is a string and needs conversion to int, but Spring Boot handles this automatically, so this is unlikely.

C The property key is misspelled in the properties file.

D The property value contains spaces or invalid characters causing parsing to fail.

💡 Hint

Check the exact value in the properties file for hidden characters.

If the property value has spaces or non-numeric characters, Spring Boot cannot convert it to int, causing NumberFormatException.

🧠 Conceptual

expert

Why is externalized configuration important in Spring Boot?

Which best explains why externalized configuration matters in Spring Boot applications?

A It allows changing app behavior without recompiling code, enabling flexibility across environments.

B It forces all configuration to be hardcoded, improving security.

C It makes the app slower because it reads files at runtime.

D It prevents the app from running if configuration files are missing.

💡 Hint

Think about how apps run in different places like development, testing, and production.

Externalized configuration lets you adjust settings like database URLs or ports without changing code, making apps flexible and easier to manage.

Practice

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

easy

A. It allows changing app behavior without modifying the code.

B. It makes the app run faster by skipping code.

C. It automatically fixes bugs in the code.

D. It prevents the app from starting without internet.

Solution

1. Step 1: Understand the role of configuration

   Configuration controls how the app behaves without changing the source code.

2. Step 2: Identify the benefit in Spring Boot

   Spring Boot uses configuration files to adjust settings easily for different environments.

3. Final Answer:

   It allows changing app behavior without modifying the code. -> Option A

4. Quick Check:

   Configuration changes behavior without code edits [OK]

Hint: Think: config changes settings, not code [OK]

Common Mistakes:

• Confusing configuration with code changes
• Believing configuration speeds up app runtime
• Assuming configuration fixes bugs automatically

2. Which of the following is the correct way to specify a property in Spring Boot's application.properties file?

easy

A. server port = 8080

B. server-port: 8080

C. server.port=8080

D. serverPort=8080

Solution

1. Step 1: Recall Spring Boot property syntax

   Spring Boot uses key=value pairs in application.properties files.

2. Step 2: Match the correct syntax

   The correct syntax uses dots to separate words and equals sign to assign values, like server.port=8080.

3. Final Answer:

   server.port=8080 -> Option C

4. Quick Check:

   Properties use dot notation and equals sign [OK]

Hint: Properties use dot notation and equals sign [OK]

Common Mistakes:

• Using colon instead of equals sign
• Using camelCase instead of dot notation
• Adding spaces around equals sign

3. Given the following application.properties content:

spring.profiles.active=dev
server.port=9090

What will be the server port when running the app with the dev profile?

medium

A. 9090 (from properties file)

B. 8080 (default port)

C. Random port assigned at runtime

D. Application will fail to start

Solution

1. Step 1: Identify active profile and property

   The active profile is set to dev, and server.port=9090 is defined.

2. Step 2: Understand profile effect on configuration

   Since server.port is set in the active profile, the app uses port 9090.

3. Final Answer:

   9090 (from properties file) -> Option A

4. Quick Check:

   Active profile sets server.port to 9090 [OK]

Hint: Active profile properties override defaults [OK]

Common Mistakes:

• Assuming default port 8080 always applies
• Thinking profile disables server port setting
• Believing app fails without explicit port

4. You have two configuration files: application.properties and application-prod.properties. You want to run the app with the prod profile but the app still uses settings from application.properties. What is the likely cause?

medium

A. Spring Boot does not support multiple configuration files.

B. The application-prod.properties file is missing a required property.

C. The app needs to be restarted twice to apply profiles.

D. The spring.profiles.active property is not set to prod.

Solution

1. Step 1: Check profile activation

   Spring Boot uses spring.profiles.active to select which profile config to load.

2. Step 2: Identify cause of fallback

   If spring.profiles.active is not set to prod, the app uses default application.properties.

3. Final Answer:

   The spring.profiles.active property is not set to prod. -> Option D

4. Quick Check:

   Profile must be activated to load its config [OK]

Hint: Activate profile with spring.profiles.active [OK]

Common Mistakes:

• Assuming file presence auto-activates profile
• Thinking missing properties cause fallback
• Believing multiple config files are unsupported

5. You want to have different database URLs for dev and prod environments in Spring Boot. Which approach correctly manages this using configuration?

hard

A. Hardcode both URLs in the main code and use if-else to select at runtime.

B. Create application-dev.properties and application-prod.properties with respective URLs, then set spring.profiles.active accordingly.

C. Use environment variables only and ignore Spring Boot profiles.

D. Put both URLs in application.properties separated by commas.

Solution

1. Step 1: Understand profile-based configuration

   Spring Boot supports multiple config files for different profiles to separate environment settings.

2. Step 2: Apply correct method for environment URLs

   Creating application-dev.properties and application-prod.properties with URLs and activating profiles is the standard way.

3. Final Answer:

   Create application-dev.properties and application-prod.properties with respective URLs, then set spring.profiles.active accordingly. -> Option B

4. Quick Check:

   Profiles separate environment configs cleanly [OK]

Hint: Use profile-specific properties files for environments [OK]

Common Mistakes:

• Hardcoding URLs in code instead of config
• Ignoring profiles and mixing URLs in one file
• Using environment variables without profiles