Start Quiz: Enterprise javabeans (ejb)

Question: What is not a state in the EJB 3 Entity beans life cycle states?

Choices:

Does not exist

Removed

Passive

Detached

Question: EJB 3.0 specifications are implemented in :

Choices:

Java EE 3

Java EE 4

Java EE 5

Question: What is true about EJB ?

Choices:

In a deployed application, both session and entity beans are managed by what is called a session container

In a deployed application, both session and entity beans are managed by what is called EJB container

In a deployed application, session beans are managed by what is called SessionContext

In a deployed application, entity beans are managed by what is called EntityContext

Question: When to opt an EJB-centric solution for your yet to be developed system?

Choices:

when the system is distributed

when the system is transactional

to create a data entry system

when you are developing a content-management system, which serves only static pages

Question: What is NOT true about Entity beans?

Choices:

Entity beans can survive a system crash

Entity beans are not pooled

Entity beans cannot be stateless

Entity beans are transactional

Question: What is an Entity Bean?

Choices:

It is an object representing data which is fetched from and can be stored to a persistent data store

It holds the state of the associated stateful session bean

It is the facade to access the system data store

Question: Managing permissions to methods (securing invoking methods to specific roles), can be applied by:

Choices:

using the xml deployment descriptor

using annotations (in EJB 3.x)

using digital signature

programmatically using isCallerInRole() and getCallerPrincipal()

Question: The three types of EJBs are :

Choices:

POJO

Transfer object

Session bean

Message-driven bean

Transaction bean

Entity bean

Question: A Stateful session bean can remember its state and the conversation with the client, but sometimes due to performance issues, the container needs to remove the Stateful session bean from the memory releasing its attached resources, what is true about this process?

Choices:

The Stateful session bean itself persists itself for later activation

The EJB container is the one responsible for managing and serializing the state of the Stateful Session bean

Just before this process (passivating), the container calls the ejbPassivate() method

Just before this process (passivating), the container calls the ejbRemove() method

Question: When to opt BMP (bean-managed persistence) over CMP (container-managed persistence)?

Choices:

when the application developed will serve a large number of users

when the project budget permits

when you would like to add to your CV a BMP experience

when you data is a mix of relational database and legacy data sources

when CMP does not provided the intended tasks

Question: What is the difference between stateful session beans and stateless session beans?

Choices:

Stateless session beans are lighter in weight and easier to manage than their stateful counterparts

Stateful session beans are pooled to increase performance due to their heavy content, whereas stateless beans are not pooled for the opposite reason

Both stateful session beans and stateless session beans can survive a server crash.

As the name implies, a Stateful session bean can remember its state with a client, in contrast to a Stateless session bean, which cannot