Download Oracle Application Development Framework 12c Essentials.1z0-419.ActualTests.2018-10-15.50q.tqb

Vendor:	Oracle
Exam Code:	1z0-419
Exam Name:	Oracle Application Development Framework 12c Essentials
Date:	Oct 15, 2018
File Size:	2 MB

Download Exam

How to open VCEX files?

Files with VCEX extension can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase
Coupon: EXAM_HUB

Discount: 20%

Demo Questions

Identify three statements that are true about JSF. (Choose three.)

Components are used to define page structure.
Navigation between pages is defined outside of the JSF page in the metadata.
Managed beans can have only one of two memory scopes.
Managed beans can be accessed from more than one page.
JSF does not support template creation for pages.

Correct answer: ABD

Explanation:

Incorrect:Not C: Managed beans can have the following scopes: Application, session, PageFlow, view, request, BackingBean.Not E: JavaServer Faces (JSF) technology provides the tools to implement user interfaces that are easy to extend and reuse. Templating is a useful Facelets feature that allows you to create a page that will act as the base, or template, for the other pages in an application. By using templates, you can reuse code and avoid recreating similarly constructed pages. Templating also helps in maintaining a standard look and feel in an application with a large number of pages. References: http://docs.oracle.com/javaee/6/tutorial/doc/giqxp.html

Incorrect:

Not C: Managed beans can have the following scopes: Application, session, PageFlow, view, request, BackingBean.

Not E: JavaServer Faces (JSF) technology provides the tools to implement user interfaces that are easy to extend and reuse. Templating is a useful Facelets feature that allows you to create a page that will act as the base, or template, for the other pages in an application. By using templates, you can reuse code and avoid recreating similarly constructed pages. Templating also helps in maintaining a standard look and feel in an application with a large number of pages.

References: http://docs.oracle.com/javaee/6/tutorial/doc/giqxp.html

Your page contains the following code that is invoked on an action by the current user:

<af:setPropertyListener from="#{applicant:surname}" to="#(...)" type="action"/>

To receive the value from the to property of the af:setPropertyListener, you create a managed bean as follows:

package view;

public class Employee {

String lastName;

public void setLastName(String lastName) { this.lastName = lastName; }

public String getLastName() { return lastName;

}

In the adfc-сonfig.xml file, the managed bean is configured as:>

<managed-bean>

<managed-bean-name>emp</managed-bean-name>

<managed-bean-class>view. Employee</managed-bean-class>

<managed bean-scope>pageFlowScope</managed-bean-scope>

</managed-bean>

What EL expression would you write in the af:setPropertyListener "to" property to write the value to the lastName string of the Employee class?

(Choose the best answer.)

to=”#{lastName}”
to=”#{LastName}”
to=”#{pageFlowScope.emp.lastName)”
to=”#{pageFlowScope.Emp.lastName}”
to=”#{emp.lastName}”
to=”#{pageFlowScope.emp.LastName}”

Correct answer: C

Explanation:

For example, the page might specify #{pageFlowScope.empno} as a page parameter and a bounded task flow might specify #{pageFlowScope.employeeID} as the value of an input parameter definition. The from-value on the view activity input page parameter would be #{pageFlowScope.employeeID} and the to-value would be #{pageFlowScope.empno}. This enables reuse of both the page definition and bounded task flow because you don't have to redefine parameters for every context in which each is used. References: https://docs.oracle.com/cd/E23943_01/web.1111/b31974/taskflows_parameters.htm#ADFFD19858

For example, the page might specify #{pageFlowScope.empno} as a page parameter and a bounded task flow might specify #{pageFlowScope.employeeID} as the value of an input parameter definition.

The from-value on the view activity input page parameter would be #{pageFlowScope.employeeID} and the to-value would be #{pageFlowScope.empno}. This enables reuse of both the page definition and bounded task flow because you don't have to redefine parameters for every context in which each is used.

References: https://docs.oracle.com/cd/E23943_01/web.1111/b31974/taskflows_parameters.htm#ADFFD19858

Consider the following code: