The video tutorial covers the Entity Manager, a key interface in JPA, and its interaction with the persistence context. It explains how the persistence context manages entities during transactions and the various methods provided by the Entity Manager, such as persist, merge, remove, flush, refresh, and detach. The tutorial emphasizes the importance of understanding these concepts and encourages further exploration of the Entity Manager interface.

What is the primary role of the Entity Manager in JPA?

• To handle user authentication

• To generate SQL queries

• To serve as an interface to the persistence context

• To manage database connections

Which method would you use to save a new entity to the database?

• Persist

• Remove

• Merge

• Detach

How does the merge method differ from the persist method?

• Merge updates existing entities, while persist saves new ones

• Merge is used to refresh entities

• Merge is used to delete entities

• Merge detaches entities from the context

What is the purpose of the flush method in a transaction?

• To detach entities from the persistence context

• To override changes from the database

• To persist changes to the database mid-transaction

• To delete entities from the database

What happens when an entity is detached using the detach method?

• The entity is permanently deleted

• The entity's changes are no longer tracked

• The entity is merged with another

• The entity is refreshed from the database