Why service layer matters in Spring Boot - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a service class in Spring Boot.

Spring Boot

@[1]
public class UserService {
    // service methods
}

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

AComponent

BController

CRepository

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Using @Controller instead of @Service

Forgetting the @Service annotation

The @Service annotation marks the class as a service layer component in Spring Boot.

2fill in blank

medium

Complete the code to inject the repository into the service class.

Spring Boot

@Service
public class UserService {
    private final UserRepository userRepository;

    public UserService([1] userRepository) {
        this.userRepository = userRepository;
    }
}

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

AUserService

BUserRepository

CUserController

DUserEntity

Attempts:

3 left

💡 Hint

Common Mistakes

Using the service class as parameter

Using the entity class instead of repository

The constructor parameter must be the repository type to inject it into the service.

3fill in blank

hard

Fix the error in the service method that calls the repository.

Spring Boot

public List<User> getAllUsers() {
    return userRepository.[1]();
}

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

AgetUsers

BfindAllUsers

CfindAll

DlistAll

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent repository methods

Misspelling method names

The correct repository method to get all records is findAll().

4fill in blank

hard

Fill both blanks to create a service method that saves a user entity.

Spring Boot

public User [1](User user) {
    return userRepository.[2](user);
}

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

AsaveUser

Bsave

CaddUser

Dinsert

Attempts:

3 left

💡 Hint

Common Mistakes

Using repository method names as service method names

Using incorrect repository methods

The service method name can be saveUser, and the repository method to save is save.

5fill in blank

hard

Fill all three blanks to create a service method that deletes a user by id.

Spring Boot

public void [1](Long [2]) {
    userRepository.[3]([2]);
}

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

AdeleteUserById

Bid

CdeleteById

DremoveUser

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong parameter names

Using incorrect repository delete methods

The service method is named deleteUserById, the parameter is id, and the repository method to delete by id is deleteById.

Practice

1. Why is the service layer important in a Spring Boot application?

easy

A. It replaces the need for controllers.

B. It separates business logic from controllers and repositories.

C. It is used only for UI rendering.

D. It handles database connections directly.

Solution

1. Step 1: Understand the role of service layer

   The service layer contains business logic and acts as a bridge between controllers and repositories.

2. Step 2: Identify incorrect roles

   Handling database connections is the repository's job, and UI rendering is done by the view layer, not the service layer.

3. Final Answer:

   It separates business logic from controllers and repositories. -> Option B

4. Quick Check:

   Service layer = business logic separation [OK]

Hint: Service layer holds business rules, not UI or DB code [OK]

Common Mistakes:

• Confusing service layer with repository layer
• Thinking service layer handles UI rendering
• Assuming service layer manages database connections

2. Which annotation is used to mark a service layer class in Spring Boot?

easy

A. @Service

B. @Controller

C. @Repository

D. @ComponentScan

Solution

1. Step 1: Recall Spring stereotypes

   @Service is the annotation used to mark service layer classes in Spring Boot.

2. Step 2: Differentiate other annotations

   @Repository is for data access, @Controller for web controllers, and @ComponentScan is for scanning components, not marking services.

3. Final Answer:

   @Service -> Option A

4. Quick Check:

   @Service marks service classes [OK]

Hint: Use @Service for business logic classes [OK]

Common Mistakes:

• Using @Repository instead of @Service
• Confusing @Controller with service annotation
• Mistaking @ComponentScan as a service marker

3. Given this Spring Boot service method, what will be the output when calling getDiscountedPrice(100)?

public double getDiscountedPrice(double price) {
    if (price > 50) {
        return price * 0.9;
    }
    return price;
}

medium

A. 90.0

B. 100.0

C. 50.0

D. 10.0

Solution

1. Step 1: Analyze the input and condition

   The input price is 100, which is greater than 50, so the if condition is true.

2. Step 2: Calculate the discounted price

   Price * 0.9 = 100 * 0.9 = 90.0

3. Final Answer:

   90.0 -> Option A

4. Quick Check:

   Price > 50 applies 10% discount [OK]

Hint: Check if price > 50 to apply 10% discount [OK]

Common Mistakes:

• Returning original price without discount
• Confusing multiplication factor
• Misreading the condition operator

4. Identify the error in this service class snippet:

@Service
public class UserService {
    public void saveUser(User user) {
        userRepository.save(user);
    }
}

medium

A. Method saveUser should return a value.

B. Service class should be annotated with @Repository.

C. Missing @Autowired for userRepository injection.

D. User class cannot be used in service layer.

Solution

1. Step 1: Check dependency injection

   The userRepository is used but not injected or declared, so it needs @Autowired or constructor injection.

2. Step 2: Verify annotations and method signature

   @Service is correct for service classes; saveUser can be void; User class is valid here.

3. Final Answer:

   Missing @Autowired for userRepository injection. -> Option C

4. Quick Check:

   Dependencies must be injected in service [OK]

Hint: Inject dependencies with @Autowired or constructor [OK]

Common Mistakes:

• Forgetting to inject repository
• Changing service annotation incorrectly
• Expecting return value unnecessarily

5. You want to add logging and transaction management to your business logic in Spring Boot. Where should you implement these features to keep your code clean and maintainable?

hard

A. In the main application class

B. Directly inside controller methods

C. Within the repository classes

D. Inside the service layer methods

Solution

1. Step 1: Understand separation of concerns

   Controllers handle web requests, repositories handle data access, so business logic like logging and transactions belong in the service layer.

2. Step 2: Apply best practices for maintainability

   Service layer is the right place to add cross-cutting concerns like logging and transaction management to keep code clean and reusable.

3. Final Answer:

   Inside the service layer methods -> Option D

4. Quick Check:

   Logging and transactions belong in service layer [OK]

Hint: Put business logic and cross-cutting concerns in service layer [OK]

Common Mistakes:

• Adding business logic in controllers
• Mixing transactions in repositories
• Placing logic in main application class