You have a class annotated with @ConfigurationProperties(prefix = "app") but after running the app, the properties are not injected. What is the most likely cause?

medium📝 Debug Q6 of 15

Spring Boot - Application Configuration

You have a class annotated with @ConfigurationProperties(prefix = "app") but after running the app, the properties are not injected. What is the most likely cause?

AThe class has no default constructor

BThe prefix in properties file is misspelled

CThe class is not registered as a Spring bean

DThe properties file is missing

Step-by-Step Solution

Solution:

Step 1: Check bean registration requirement
Classes annotated with @ConfigurationProperties must be registered as Spring beans to enable binding.
Step 2: Understand other causes
While misspelled prefix or missing file can cause issues, the most common cause is missing bean registration.
Final Answer:
The class is not registered as a Spring bean -> Option C
Quick Check:
Bean registration required for binding [OK]

Quick Trick: Register @ConfigurationProperties class as a bean [OK]

Common Mistakes:

Ignoring bean registration
Assuming default constructor is mandatory
Overlooking prefix spelling

Master "Application Configuration" in Spring Boot

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Spring Boot Quizzes

You have a class annotated with @ConfigurationProperties(prefix = "app") but after running the app, the properties are not injected. What is the most likely cause?

Step 1: Check bean registration requirement

Step 2: Understand other causes

Final Answer:

Quick Check:

Want More Practice?