Oracle
1Z0-860 · Question #102
A developer is creating a long-running Java Persistence reporting application that accesses a set of related entities. The application is NOT expected to add, change, or remove records in the…
The correct answer is D. Call the Entity Manager refresh on each parent entity that is added to the report, and specify. See the full explanation below for the reasoning.
Question
A developer is creating a long-running Java Persistence reporting application that accesses a set of related entities. The application is NOT expected to add, change, or remove records in the database but the data can be changed by another application running on the same database. Which option will guarantee that the report does NOT contain stale data?
Options
- ACall the Entity Manager flush API before preparing the report.
- BCall the Entity Manager create Ouery API before preparing the report.
- CCall the Entity Manager clear API before accessing the fields or properties of the entities used in the
- DCall the Entity Manager refresh on each parent entity that is added to the report, and specify
How the community answered
(35 responses)- A3% (1)
- B6% (2)
- C9% (3)
- D83% (29)
Community Discussion
No community discussion yet for this question.