when to use entity bean?
-
when business object should be stored in persistant storage mechanism.
-
if information have to be passed from one group to other.
-
to review the data in other application
-
to check with the client.
Entity beans are designed to represent business objects that need persistent storage - data that survives beyond application sessions. Option A correctly states this purpose. Entity beans map to database tables and handle CRUD operations. Options B, C, and D describe other concerns (communication, review, validation) not related to persistence.
Entity beans model persistent business data that needs to be stored and retrieved from a durable storage mechanism (typically a database), with each entity bean instance representing a row of persistent data. They aren't used for passing data between groups or reviewing data in other applications — that's not their purpose.