Oracle Mobile Development 2015 Essentials - 1z1-441 Exam Practice Test

A. <amx:commandButton rendered="#{deviceScope.device.hasCamera}"/>

B. <amx:commandButton rendered="#{device.hasCamera}"/>

C. <amx:commandButton rendered="#{deviceScope.camera}"/>

D. <amx:commandButton rendered="#{device.camera}"/>

A. Device has camera

B. Device screen diagonal size

C. Device OS

D. Device network status

E. Device barcode resolution

F. Device battery capacity

A. Create a TopLink persistence layer to query and update the database. The AMX user interface components bind to the EJB session facade.

B. Configure the SQLite database data control and use the data controls panel to drag and drop data collections and attributes onto the AMX view.

C. Use the REST service adapter to query data from SQLite in JSON format.

D. Use a JavaBean to wrap calls to SQLite database and create a JavaBean DataControlfrom it, that then appears in the data controls panel.

A. A data control is an adapter that exposes a simpler, unified development API for MAF application developers to declaratively and programmatically access data services.

B. Data controls are configured in one or moreDataControls.dcxfiles.

C. Data controls in MAF exist for remote SOAP and REST services only and handle all of the XML to Java object marshalling and unmarshalling.

D. Data controls expose data service structures in the data controls panel. The information exposed includes attributes, collections, and public methods.

E. MAF is restricted to ten data controls per mobile application.

A. Provide an Oracle MAF Application Archive file and he will use the Create a new MAF Application from Application Archive option in JDeveloper.

B. Provide an Oracle MAF Application Archive file and he will add this as another project in his workspace.

C. Provide an IPA file and he will use Xcode to decompile it and further modify the code.

D. Provide a JAR file containing your Oracle MAF Java code and he will add it as a JAR library to his MAF application.

A. local HTML

B. unbounded task flow

C. bounded task flow

D. fragment

E. remote URL

F. remote task flow

G. declarative component

H. local AMX

A. The URL scheme name and optionally ahierarchicalpart might be carried along with an optional
single parameter key-value pair. For example, it might carry:
myapp://
myapp://doSomething
myapp://doSomething?value1=123

B. The URL scheme name and optionally ahierarchicalpart might be carried. No other URL is
valid. For example, it might carry:
myapp://
myapp://doSomething

C. Only the URL scheme name might be carried. No other URL is valid. For example, it might
carry:
myapp://

D. The URL scheme name might be carried along with an optional hierarchical part and multiple
parameter key-value pairs. No other URL is valid. For example, it might carry:
myapp://
myapp://doSomething
myapp://doSomething?value1=123
myapp://doSomething?value1=123&value2=true

A. AMX page

B. unbounded task flow

C. side bar

D. menu items

E. feature

A. #{deviceScope.hardware.screen.width<deviceScope.hardware.screen.height?'portrait':'landscape' }

B. #{deviceScope.hardware.screen.availableWidth < deviceScope.hardware.screen.availableHeight ? 'portrait ':'landscape'}

C. #{device.screenWidth < device.screenHeight ?'portrait':'landscape'}

D. #{deviceScope.orientation}