A. Use the builder call right-click menu Sort option.

B. Click on the # column header in the builder call view.

C. Use the model right-click menu to order the builder calls.

D. Drag the builder calls into execution order.

A. In the Project Explorer, right-click the Model and select Open with Dependency Tracker.

B. Click the arrow next to the Builder call or right-click the Builder call and select Show Elements in Application Tree.

C. Select the Model XML view and click the Builder Call in the Outline view.

D. In the Application Tree, right-click each element to see the name of the Builder call that created it.

A. Receive data in a Data Page builder, examine the data, enrich the data.

B. Receive data in a Data page builder, modify the schema, apply modifiers.

C. Examine received data in the context of a View and Form builder, build a presentation for the data, document the schema.

D. Set up a data provider model, create a consumer model, select the highest level page automation builder that fits the requirement, customize the generated UI to the requirements.

A. Add a Portlet Adapter builder call to a model.

B. Generate a portlet WAR file, which automatically deploys all models as portlets.

C. Modify the portlet.xml file with a text editor to include file paths.

D. Generate a model with a specific file path to its resources.

A. <%=webAppAccess.getBackchannelURL("getAddress", false)%>

B. <%=webAppAccess.getAjaxURL("getAddress", false)%>

C. <%=webAppAccess.getActionURL("getAddress", false)%>

D. <%=webAppAccess.getBackchannelActionURL("getAddress", false)%>

A. Place the bundles into the project ensuring that the bundles include the appropriate language and country codes. Then use a Localized Resource builder to import the proper bundle according to the locale determined for the user of the portlet.

B. Use the Data Services builder to generate a service that selects the appropriate bundle based upon the locale of the request and returns it as an XML structure that can be fed directly into the Data Page or View and Form builders.

C. Phil can use the Imported Resource builder and the Simple Locale Profile Selection Handler to select and import the correct bundle. Then use Data Page, View and Form, and the other UI builders to construct the localized UI with strings from the imported bundle.

D. Place the bundles into the project and use the Imported Page builder and it's localization inputs to automatically apply the correct resource bundle to the page imported into the portlet.

A. Click-to-Action

B. Property Broker Action

C. Property Broker Link

D. Factory Events

A. Customize the appropriate values in styles defined within the client_dojo_mobile.uitheme directory.

B. Add a Client-Side CSS builder to the model.

C. Add client-side builders to the model and specify preferences in the builder inputs.

D. Modify the CSS in the model's theme.

A. Load when event is fired. Load the content upon receipt of an event.

B. Load when visible. Load the content when its location becomes visible.

C. Load when method completes. Load the content when a specified JavaScript method completes execution.

D. Load when timer is complete. Load the content when a specified time interval is complete.

A. This feature is not yet supported.

B. She must purchase full rights to the IBM Web Experience Factory source to debug generated Java.

C. System.out.println is the only way to debug Java associated with Method builders.

D. Right-click a method in the Application Tree view to set/toggle a breakpoint. Start the application server in debug mode and run the model with a remote Java debug configuration, as documented in the Web Experience Factory help.