Michelle is editing an existing XPage: ?The page has a "tags" Edit Box with Type Ahead enabled, which provides suggestions for possible tags or keywords to add to the document. ?The HTML source of the Edit Box includes a dojoType attribute. ?After the edit box there is a panel named "tagsHint" explaining the concept of tags. ?Now Michelle wants to hide the "tagsHint" panel when values are already present in the "tags" field. ?She adds an Output Script control containing the following code: var tags = dijit.byId("#{id:tags}"); if( tags.value.length > 0 ){ // already set some tag var tagsHint = XSP.getElementById("#{id:tagsHint}"); tagsHint.style.display = "none"; } ?When she opens the page in a web browser, the JavaScript Error Console reports the error: tags is undefined at the line: if( tags.value.length > 0 ){ // already set some tag What is the problem with the sample code?

• A. The dijit is not yet loaded; the code in the Output Script control should be in an "addOnLoad" listener function.
• B. There is no initial value in the tags field, so it is not possible to find the length of the value.
• C. The script should be in the "onload" event of the XPage control corresponding to the HTML "body" tag.
• D. The first line should be: var tags = XSP.getElementById("#{id:tags}");

Marco has built an XPage that has increased in complexity over time and now contains several hundred lines of XSP markup, with many postback actions that conditionalize the display of the page. He feels that the page does not perform well and is looking to improve the responsiveness for the end-user. He is considering the following actions to improve performance. All of the following actions may improve performance EXCEPT which one:

• A. Use Partial Refresh to conditionally redraw only those parts of the page impacted by postback actions.
• B. Conditionally set the "loaded" property to "true" for controls and data sources that are displayed, and "false" when they are hidden.
• C. Reduce the size of the page by splitting it up into several custom controls wherever possible.
• D. Use scoped variables to store/retrieve data that will not change between postback requests.

Tim has an XPage containing an Edit Box. He has read that it is possible to use the Dojo Toolkit NumberSpinner control in XPages, and he wishes to modify his XPage so that the Edit Box will appear as a Number Spinner in the browser. What would the steps be to accomplish this?

• A. In the XPage, in the Resources tab of the Properties view, add a Dojo Module resource for
  "dijit.form.NumberSpinner" to the XPage.
  Configure the Edit Box to set the dojoType to "dijit.form.NumberSpinner".
• B. From the Dojo Tollkit Website, get the URL to the most recent version of the NumberSpinner.js control (where the URL begins with http://). In the XPage, in the Resources tab of the Properties view, add a JavaScript Library using that
  URL.
  Configure the Edit Box to set the dojoType to "dijit.form.NumberSpinner".
• C. Import the NumberSpinner.js file from Dojo into the application as a JavaScript Library.
  In the XPage, in the Resources tab of the Properties view, add a JavaScript Library resource for
  that NumberSpinner.js file to the XPage.
  Configure the Edit Box to set the dojoType to "dijit.form.NumberSpinner".
• D. Import the NumberSpinner.js file from Dojo into the application as a Dojo Module.
  In the XPage, in the Resources tab of the Properties view, add that Dojo Module resource for that
  NumberSpinner.js file to the XPage.
  Configure the Edit Box to set the dojoType to "dijit.form.NumberSpinner".

Rachel needs to enable her XPages application for multi-language use. Where should she go to enable localization?

• A. In Lotus Notes, open up the Application Properties and on the Advanced tab click 'Enable localization'
• B. In Domino Designer, open up the Application Properties and on the Advanced tab click 'Enable localization'
• C. It is not possible to enable localization at application-level in XPages.
• D. In Domino Designer, open up the Application Properties and on the XPages tab click 'Enable localization'