Fetch types (LAZY vs EAGER) in Spring Boot - Quick Revision & Key Differences

Recall & Review

beginner

What does LAZY fetch type mean in Spring Boot?

LAZY fetch type means related data is loaded only when it is accessed for the first time, not when the main entity is loaded.

beginner

What does EAGER fetch type mean in Spring Boot?

EAGER fetch type means related data is loaded immediately with the main entity, even if it is not accessed right away.

intermediate

Which fetch type can cause performance issues if many related entities are loaded unnecessarily?

EAGER fetch type can cause performance issues because it loads all related data immediately, even if not needed.

intermediate

How does LAZY fetch type improve application performance?

LAZY fetch type improves performance by loading related data only when needed, reducing initial data load and memory use.

intermediate

In which scenario is EAGER fetch type preferred?

EAGER fetch type is preferred when related data is always needed immediately with the main entity, avoiding extra database calls later.

What happens when you use LAZY fetch type in Spring Boot?

A Data loads randomly

B Related data loads immediately with main entity

C No data is loaded at all

D Related data loads only when accessed

LAZY fetch type delays loading related data until it is accessed.

Which fetch type loads all related entities immediately?

A EAGER

B DEFERRED

C NONE

D LAZY

EAGER fetch type loads related entities immediately with the main entity.

What is a downside of using EAGER fetch type?

A Data loads only on user request

B Related data never loads

C Slower initial loading due to loading all related data

D It causes syntax errors

EAGER fetch can slow down loading because it fetches all related data upfront.

When is LAZY fetch type most useful?

A When related data is always needed

B When related data is rarely needed

C When no related data exists

D When you want to load everything immediately

LAZY fetch is best when related data is not always required, saving resources.

Which annotation attribute controls fetch type in Spring Boot JPA?

A fetch

B load

C type

D mode

The 'fetch' attribute in annotations like @OneToMany controls LAZY or EAGER loading.

Explain the difference between LAZY and EAGER fetch types in Spring Boot.

Think about when related data is loaded and how it affects speed.

Describe a situation where you would choose LAZY fetch type over EAGER.

Consider saving resources by loading data only when necessary.