A GUI bean deployment utility
|
Synchronous invocation for all bean types.
|
Transaction support for all bean types.
|
Remote client views for all bean types.
|
JNDI namespace
|
Local home interfaces for message –driven beans
|
Dirty detection mechanism to reduce memory footprints.
|
Run as security identity funtionality.
|
The JDBC 2.0 extension.
|
Session Bean failover.
|
Portable finder query syntax.
|
Container managed persistence.
|
Local interfaces for session beans.
|
XML based deployment descriptors.
|
Synchronous message-driven beans.
|
True
|
False
|
5. An entity session bean can be shared between multiple client, as long as the entity being shared is the same.
True
|
False
|
True
|
False
|
True
|
False
|
True
|
False
|
True
|
False
|
10. Each Entity Bean must have its EJBObject
True
|
False
|
11. Which capabilities are provided by both remote and local home interfaces for session beans ( Choose all that apply)
Creating a session object
|
Removing a session object
|
Getting a session object’s EJBMeteData
|
Getting a session object’s handle
|
The session context must be narrowed, and the narrowed result cast.
|
The result of the JNDI lookup must be narrowed, and the narrowed result cast.
|
The initial context must be narrowed, and the narrowed result cast.
|
The result of the JNDI lookup must be cast to an initial context, and then narrowed re
|
The bean provider must write the method public void remove() in both stateless and stateful session classes.
|
Local clients can remove session beans by calling a method on the bean’s home.
|
The remove() method in the component interface can be used on ly by remote clients.
|
To ask the EJBHome to remove a session bean. The client must provide the bean’s handle.
|
Transactional components.
|
Distributed object components.
|
Server-side components.
|
All of the options.
|
A web server.
|
An application server.
|
An EJB container.
|
A Database Server
|
java.rmi.Remote
|
javax.ejb.EJBHome
|
javax.ejb.EJBObject
|
javax.ejb.EntityBean
|
An XML file format used by the container to learn about the attributes of a bean, such as transactional characteristics and access control
|
A method for transporting enterprise beans back and forth between systems
|
An XML file used by enterprise bean clients to learn about the attributes of a bean, such as access control and transactional characteristics.
|
A format for bundling enterprise beans for delivery to customers
|
18. What distinguishes a bean-managed persistent (BMP) enterprise bean from a container-managed persistent (CMP) enterprise bean ? |
A BMP bean must implement the ejbLoad() and ejbStore() methods
|
A BMP bean can implement persistence to custom datastores such as legacy systems
|
A BMP bean is responsible for managing its own persistence to a persistent datastore
|
All of the options
|
The Remote object reference
|
A local copy of the remote object.
|
None of these
|
The Remote object's stub
|
Has a client view
|
Doesn't feature a component interface.
|
Has a Remote interface
|
Has a local interface
|
SMS
|
Email
|
JMS
|
EJB
|
The client
|
The transaction
|
The database
|
The server connection
|
EJB Entity beans
|
EJB Session beans
|
EJB Container
|
EJB Server
|
A is true
|
B is false
|
Both A and B are false
|
Both A and B are true
|
Container –Managed Persistence
|
Bean managed persistence
|
All of the options
|
None of the options
|
The entity bean
|
The session bean
|
The Message-Driven bean
|
None of the options
|
They have container bean persistence
|
The state of an entity bean is permanently stored in the database
|
All of the options
|
None of the options
|
Database independence as well as portability
|
Not having to write the logic for storing fields in the database
|
All of the options
|
None of the options
|
one – to – one
|
one – to – many
|
None of the above
|
All of the above
|
cascade - delete
|
relationship – role – source
|
ejb – name
|
None of the options
|
Realization
|
Composition Aggregation
|
Basic Aggregation
|
Generalization
|
jboss.xml
|
jbosscmp-jdbc.xml
|
ejb-jar.xml
|
web.xml
|
ejbCreate()
|
ejbFindByPrimaryKey()
|
All of the the options
|
None of the options
|
Publish/Subscribe
|
Peer to peer
|
Point to Point
|
Client/Server
|
Publish/Subscribe
|
Peer to peer
|
Point to Point
|
Client/Server
|
JMS
|
JNDI
|
JDBC
|
EJB
|
MessageListener
|
QueueListener
|
TopicListener
|
JMSListener
|
The Client
|
The EJB Server
|
The Database
|
The Application - Assembler
|
Object representations
|
Direct copies
|
All of the options
|
None of the options
|
JMS destination
|
EJB container
|
EJB Server
|
Message-driven bean itself
|
41. Which of these is not a feature of EJB containers?
|
Transaction support
|
Security support
|
Message sending
|
Persistence management
|
ejbLoad()
|
ejbRemove()
|
ejbPostCreate()
|
create()
|
Release the bean-dependent resources
|
Dissociate the bean from the context object
|
Free connection instances
|
Destroy enbtity bean instances
|
Enterprise beans
|
Security Context
|
EJB Objects
|
EJB Context Objects
|
Application Components
|
Resource Managers
|
Transaction Manager
|
All of the above
|
None of the above
|
It is not serializable
|
The public fields are from the home class container fields
|
All of the above
|
None of the above
|
Enterprise beans
|
Security Context
|
EJB Context Objects
|
EJB Objects
|
isCallerInRole()
|
getHome()
|
getCallerPrincipal()
|
getUserTransaction()
|
< security-role-ref >
|
< security-identity >
|
< security-role >
|
< role-name >
|
getHome()
|
getRololbackOnly()
|
getCallerPrincipal()
|
getUserTransaction()
|