Test your JPA knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is a realistic tradeoff to weigh when relying heavily on JPA/Hibernate's automatic, convention-driven SQL generation for a performance-critical, high-throughput application feature?
Questions in this quiz
What is a realistic tradeoff to weigh when relying heavily on JPA/Hibernate's automatic, convention-driven SQL generation for a performance-critical, high-throughput application feature?
How can a JPQL query use `JOIN FETCH` to help address the N+1 query problem for a specific query?
What is the "N+1 query problem" as it commonly arises in JPA/Hibernate applications using lazy-loaded relationships?
What is the difference between "eager" and "lazy" fetching strategies for a JPA entity relationship (e.g. `fetch = FetchType.LAZY`)?
What does JPA's "dirty checking" mechanism do?
What is an `EntityManager` in JPA, and what role does it play?
What is JPQL (Java Persistence Query Language), and how does it differ from writing raw SQL?
What is the relationship between JPA and Hibernate?
What does a JPA "cascade" setting (like `cascade = CascadeType.ALL` on a relationship) control?
What is a realistic reason a Java application might choose to write raw native SQL queries (via `@Query(nativeQuery = true)` in Spring Data JPA, or `createNativeQuery` in raw JPA) rather than relying purely on JPQL?
Why is JPA commonly used together with the Spring Framework, specifically via Spring Data JPA?
What does JPA's support for entity relationships (`@OneToMany`, `@ManyToOne`, `@ManyToMany`) allow developers to express?