which three are true about the EJB business component tier?

A developer needs to deliver a large-scale enterprise application that connects developer chooses
an EJB 3.1-compliant application server, which three are true about the EJB business component
tier? (Choose three.)

A developer needs to deliver a large-scale enterprise application that connects developer chooses
an EJB 3.1-compliant application server, which three are true about the EJB business component
tier? (Choose three.)

A.
Load-balancing is NOT a guarantee for all EJB 3.1 containers.

B.
Clustering is guaranteed to be supported by the EJB 3.1 container.

C.
Thread pooling can be optimized by the Bean Provider programmatically.

D.
Bean Providers are NOT required to write code for transaction demarcation.

E.
Support for server fail-over is guaranteed for an EJB 3.1-compliant application server.

F.
EJB 3.1 compliant components are guaranteed to work within any Java EE 6 application server

Explanation:
The EJB tier hosts the business logic of a J2EE application and provides systemlevel services to the business componentsproblems include state maintenance, transaction
management, and availability to local and remote clients.
The EJB 3.1 specification does not address “high-end” features like clustering (not B), loadbalancing (A) and fail-over (not E).
F: The target platform for EJB is Java EE.



Leave a Reply 6

Your email address will not be published. Required fields are marked *


Alex

Alex

I think it’s ADF.
Bean provider can’t take control of thread pool at all. Also it’s possible to use transactions without writing any special code for it (REQUIRED CMT demarcation as default).

WonderWoman

WonderWoman

Is it ACF or ADF finally?

atef30

atef30

Is it ACF or ADF finally????

Andrei

Andrei

In my opinion ADF,Thread pooling is configured only from xml file.

JavaBatman

JavaBatman

No its ACF