GWT Mock Test


Advertisements


This section presents you various set of Mock Tests related to GWT. You can download these sample mock tests at your local machine and solve offline at your convenience. Every mock test is supplied with a mock test key to let you verify the final score and grade yourself.

Questions and Answers

GWT Mock Test I

Answer : B

Explanation

GWT stands for Google Web Toolkit.

Q 8 - Which of the following is not a core component of GWT framework?

A - GWT Java to JavaScript compiler

B - JRE Emulation library

C - GWT UI building library

D - Web Browser

Answer : D

Explanation

Web Browser is not a core component of GWT framework.

Q 9 - Which of the following is not a mandatory component of GWT application?

A - Module descriptors

B - Public resources

C - Server-side code

D - Client-side code

Answer : C

Explanation

Server-side code is a optional part of a GWT application.

Answer : B

Explanation

'inherits' tag in *.gwt.xml file adds other gwt module in application just like import does in java applications. Any number of modules can be inherited in this manner.

Answer : C

Explanation

'entry-point' tag in *.gwt.xml file specifies the name of class which will start loading the GWT Application.

Q 14 - Can you have multiple entry-point classes in a *.gwt.xml file?

A - true

B - false

Answer : A

Explanation

Yes! Any number of entry-point classes can be added.

Q 15 - Which method of a entry-point class is called when GWT application starts?

A - main()

B - onModuleLoad()

C - process()

D - execute()

Answer : B

Explanation

onModuleLoad() function gets called and acts similar to main method of a java application.

Answer : A

Explanation

The default public path is the public subdirectory underneath where the Module XML File is stored.

Answer : C

Explanation

A module entry-point is any class that is assignable to EntryPoint and that can be constructed without parameters. When a module is loaded, every entry point class is instantiated and its EntryPoint.onModuleLoad() method gets called.

Answer : C

Explanation

*.nocache.js file contains the javascript code required to resolve deferred binding configuarations (for example, browser detection) and to use lookup table generated by GWT compiler to locate one of the .cache.html.

Answer : A

Explanation

*.cache.html contains the actual program of a GWT application.

Answer : C

Explanation

GWT compiler generates .nocache.js file every time with the same name whenever a GWT application is compiled. So browser should always download the .nocache.js file to get the latest gwt application. gwt.js code actually appends a unique timestamp at the end of the file name so that browser always treat it a new file and should never cache it.

Answer Sheet

Question Number Answer Key
1 B
2 D
3 D
4 D
5 C
6 C
7 C
8 D
9 C
10 D
11 A
12 B
13 C
14 A
15 B
16 A
17 B
18 C
19 D
20 A
21 C
22 C
23 A
24 D
25 C

gwt_questions_answers.htm

Advertisements