When you want to be certain your application data persists between program invocations, even in the event of a crash.

If you need to initiate a database transaction.

To process transient data that can be re-created in the event of a crash.

To keep people who do not know how to program from accidentally changing important logic code.

To make the user interface more interesting.

To simplify application deployment.

To prevent malicious programs from gaining access to sensitive information on your database server.

To make the application much easier to update, maintain, and manage.

XML imposes important limitations on the receiving program or tool.

The receiving program or tool can use the XML tagging information to determine how to best handle the incoming data.

XML tags offer an extra level of security.

XML tags specify to the receiving program or tool exactly how to format and display the data.

The thin client.

Deployment descriptors.

The JAR file.

The bean's container

When you implement entity or session bean methods to use SQL commands you provide.

When the bean's container handles data storage and retrieval.

When the J2EE server is never shut down.

When changes to database data are lost during a crash.

By thin clients.

By calls to the database.

By the J2EE server.

By the bean's container.

First tier.

Second tier.

Third tier.

Fourth tier.

16

130

610

22

false

true

none of the above

All of the above

NaN

null

string

None of the above

6

5

true

NaN

11

10

12

None of the above

022

18

9

None of the above

b

a

c

None of the above

o

NaN

null

10

a

\u0061

0061

"0061"

True

False

Infinity

NaN

number

null

no

yes but except service()

yes except init()

yes except destroy()

True

False