SCBCD Mock Questions - 11 - Answers

1)1,2,4,5
Answers 1,2,4 and 5 are correct.
Answer 1 is correct. Synchronization would not work if the EJB Container distributed enterprise beans instances across multiple JVMs.
Answer 2 is correct. The file system APIs are not well-suited for business components to access data. Business components should use a resource manager API, such as JDBC, to store data.
Answer 4 is correct. The same reason applied as answer 2.
Answer 5 is correct. These functions are reserved for the EJB Container. Allowing the enterprise bean to use these functions could compromise security and decrease the Container's ability to properly manage the runtime environment.
Answer 3 is incorrect. The bean provider can make use of the JMS API.

2),2,4
Answers 1, 2 and 4 are correct.
The following are considered to be goals of the EJB 2.0 Specification:
* Define the integration of EJB with the Java Message Service.
* Provide a local client view and support for efficient, lightweight access to enterprise beans from local clients.
* Provide improved support for the persistence of entity beans.
* Provide improved support for the management of relationships among entity beans.
* Provide a query syntax for entity bean finder methods.
* Provide support for additional methods in the home interface.
* Provide for network interoperability among EJB servers.

3)1,2,5
Answers 1, 2 and 5 are correct.
Answer 1 is correct. This rule is required to ensure consistent runtime semantics because while some EJB Containers may use a single JVM to execute all enterprise bean's instances, others may distribute the instances across multiple JVMs.
Answer 2 is correct. Most servers do not allow direct interaction between an application program and a keyboard/display attached to the server system.
Answer 5 is correct. This function is reserved for the EJB Container. Allowing the enterprise bean to perform this function would create a security hole.
Answer 3 is incorrect. It is possible to create an interface and implement the interface to make available in the enterprise bean business method.
Answer 4 is incorrect. The enterprise bean can make use of the JavaMail API.

4)2
Answer 2 is correct.
The following is a shortlist of the roles identified in the EJB 2.0 specification:
Enterprise Bean provider: The Enterprise Bean Provider is the producer of enterprise beans. His or her output is an ejb-jar file that contains one or more enterprise beans.
Application Assembler: The Application Assembler combines enterprise beans into larger deployable application units. The input to the Application Assembler is one or more ejb-jar files produced by the Bean Provider(s).
Deployer: The Deployer takes one or more ejb-jar files produced by a Bean Provider or Application Assembler and deploys the enterprise beans contained in the ejb-jar files in a specific operational environment.
EJB Server Provider: The EJB Server Provider is a specialist in the area of distributed transaction management, distribute objects, and other lower-level system-level services. A typical EJB Server Provider is an OS vendor, middleware vendor, or database vendor.
EJB Container Provider: The EJB Container Provider (Container Provider for short) provides: 1) The deployment tools necessary for the deployment of enterprise beans and 2) The runtime support for the deployed enterprise bean instances.
System Administrator: The System Administrator is responsible for the configuration and administration of the enterprise's computing and networking infrastructure that includes the EJB Server and Container.

5)1,4
Answers 1 and 4 are correct.
The following are high level requirements for the enterprise deployment descriptor: ejb-jar.xml
The ejb-jar file must contain, either by inclusion or by reference, the class files of each enterprise bean as follows:
* The enterprise bean class.
* The enterprise bean home and component interfaces.
* The primary key class if the bean is an entity bean.
* The ejb-jar file must also contain, either by inclusion or by reference, the class files for all the classes and interfaces that each enterprise bean class and the home and component interfaces depend on, except J2EE and J2SE classes.
* The Application Assembler must not package the stubs of the EJBHome and EJBObject interfaces in the ejb-jar file.

6)2
Answer 2 is correct.
The following is a shortlist of the roles identified in the EJB 2.0 specification:
Enterprise Bean provider: The Enterprise Bean Provider is the producer of enterprise beans. His or her output is an ejb-jar file that contains one or more enterprise beans.
Application Assembler: The Application Assembler combines enterprise bean's into larger deployable application units. The input to the Application Assembler is one or more ejb-jar files produced by the Bean Provider(s).
Deployer: The Deployer takes one or more ejb-jar files produced by a Bean Provider or Application Assembler and deploys the enterprise bean's contained in the ejb-jar files in a specific operational environment.
EJB Server Provider: The EJB Server Provider is a specialist in the area of distributed transaction management, distribute objects, and other lower-level system-level services. A typical EJB Server Provider is an OS vendor, middleware vendor, or database vendor.
EJB Container Provider: The EJB Container Provider (Container Provider for short) provides: 1) The deployment tools necessary for the deployment of enterprise beans and 2) The runtime support for the deployed enterprise bean instances.
System Administrator: The System Administrator is responsible for the configuration and administration of the enterprise's computing and networking infrastructure that includes the EJB Server and Container.

7)2,4
Answers 2 and 4 are correct. Answer 1 is incorrect. The EJB 2.0 specification provided message driven beans, this is seen as a feature and not as a goal of the EJB architecture. Answer 3 is incorrect. The EJB architecture is focused on distributed applications and not on client applications. Answer 5 is incorrect.

8)1
Answer 1 is correct.
The following is a shortlist of the roles identified in the EJB 2.0 specification:
Enterprise Bean provider: The Enterprise Bean Provider is the producer of enterprise beans. His or her output is an ejb-jar file that contains one or more enterprise beans.
Application Assembler: The Application Assembler combines enterprise beans into larger deployable application units. The input to the Application Assembler is one or more ejb-jar files produced by the Bean Provider(s).
Deployer: The Deployer takes one or more ejb-jar files produced by a Bean Provider or Application Assembler and deploys the enterprise beans contained in the ejb-jar files in a specific operational environment.
EJB Server Provider: The EJB Server Provider is a specialist in the area of distributed transaction management, distribute objects, and other lower-level system-level services. A typical EJB Server Provider is an OS vendor, middleware vendor, or database vendor.
EJB Container Provider: The EJB Container Provider (Container Provider for short) provides:
1. The deployment tools necessary for the deployment of enterprise beans
2. The runtime support for the deployed enterprise bean instances.
System Administrator: The System Administrator is responsible for the configuration and administration of the enterprise's computing and networking infrastructure that includes the EJB Server and Container.

9)1,3,5
Answers 1, 3 and 5 are correct.
Message driven beans are introduced in the EJB 2.0 specification. A message-driven bean is a stateless component that is invoked by the container as a result of the arrival of a JMS message.
The local client view or local interfaces and local home interfaces for session beans and entity beans to provide support for lightweight access from enterprise beans that are local clients are part of the EJB 2.0 specification.
EJB-QL (Enterprise Javabeans Query language) this is a declarative syntax for the definition of query methods for entity beans with container-managed persistence that allows the implementation of finder and select methods to be provided by the container.
Answer 2 is incorrect, the remote client view was already part of the EJB 1.1 specification.
Answer 4 is incorrect, PL/SQL or stored procedures are not a direct requirement of the EJB specification.

10)1,3
Answers 1 and 3 are correct.
An EJB 2.0 Container must make these APIs available:
* Java 2 Platform, Standard Edition v1.3 (J2SE) APIs
* EJB 2.0 APIs
* JNDI 1.2
* JTA 1.0.1, the UserTransaction interface only
* JDBC 2.0 extension
* JMS 1.0.2
* JavaMail 1.1, sending mail only
* JAXP 1.0
These are only minimum requirements. The container may choose to provide additional functionality that is not required by the EJB specification.