Master Microservices with Spring Boot and Spring Cloud - Step 31 – Updating GET Methods on User Resource to Use JPA

The video tutorial explains how to transition from an in-memory list to an embedded database using JPA. It covers creating a new JPA resource, setting up a user repository, and integrating it with the existing system. The tutorial also addresses potential server issues due to URL conflicts and demonstrates testing and debugging techniques to ensure data is retrieved correctly from the database.

What is the main reason for creating a new user JPA resource?

• To enhance security features

• To improve server performance

• To avoid disturbing the existing user resource

• To reduce memory usage

What is the primary purpose of creating a user repository in Spring Data?

• To improve application speed

• To manage user authentication

• To handle user interface design

• To manage entities and their primary keys

Which of the following is NOT a step in integrating the user repository into the user JPA resource?

• Auto-wiring the user repository

• Creating a private user repository variable

• Using the repository to retrieve all users

• Deleting the static array list

What method is used to retrieve all users from the user repository?

• fetchAll()

• findAll()

• getAll()

• retrieveAll()

What does the findById method return in JPA?

• An Optional of user

• A single user object

• A list of users

• A boolean indicating success

How can you check if a user is present when using findById?

• By checking if the user is null

• By using user.exists()

• By using user.isPresent()

• By comparing user to an empty string

What should be done if a user is not present when retrieved by ID?

• Return a default user

• Retry the request

• Log an error message

• Throw an exception