Download Oracle.1z0-419.CertKiller.2018-11-27.53q.tqb
| Vendor: | Oracle |
| Exam Code: | 1z0-419 |
| Exam Name: | Oracle Application Development Framework 12c Essentials |
| Date: | Nov 27, 2018 |
| File Size: | 1 MB |
| Downloads: | 1 |
Demo Questions
Question 1
Which three statements are true about the default value for an entity object attribute? (Choose three.)
- It can be a literal value.
- It can be defined by a Groovy expression.
- It can be defined by a SQL select statement.
- It can be defined by an Expression Language (EL) statement.
- It can be defined by referencing a database stored procedure.
Correct answer: ABD
Explanation:
A: The Value field (in the Edit Attribute dialog) allows you to specify a static default value for the attribute when the Value Type is set to Literal. For example, you can set the default value of the ServiceRequest entity object's Status attribute to Open, or set the default value of the User entity object's UserRole attribute to user. B: You can use a Groovy expression to define a default value for an attribute. This approach is useful if you want to be able to change default values at runtime.D: Groovy scripting logic is similar to Expression Language (EL)References: http://docs.oracle.com/cd/E15586_01/web.1111/b31974/bcentities.htm#BABFBJAI A: The Value field (in the Edit Attribute dialog) allows you to specify a static default value for the attribute when the Value Type is set to Literal. For example, you can set the default value of the ServiceRequest entity object's Status attribute to Open, or set the default value of the User entity object's UserRole attribute to user.
B: You can use a Groovy expression to define a default value for an attribute. This approach is useful if you want to be able to change default values at runtime.
D: Groovy scripting logic is similar to Expression Language (EL)
References: http://docs.oracle.com/cd/E15586_01/web.1111/b31974/bcentities.htm#BABFBJAI
Question 2
A backing bean for a page must hold its value over multiple requests for the current user. Which three bean scopes are applicable? (Choose three.)
- requestScope
- backingBeanScope
- viewScope
- pageFlowScope
- sessionScope
- applicationScope
Correct answer: CDE
Explanation:
C: View scope: The object is available until the view ID for the current view activity changes. This becomes handy when you use partial page rendering. If you have a dependent list box, you might send a server request to refresh the list box. When a response is returned, the request scope will be gone but the view scope will be still there. D: A pageFlow scope exists for each task flow instance and has a lifespan between request and session scope. The lifetime of the scope spans across all pages in a bounded task flow. E: Session scope: The object is available for the duration of the session, which is user instance-specific. A use case for a session scope bean is a user info bean that stores information about a user, which is read from the database or an LDAP server, to avoid unnecessary queries. Incorrect Answers:A: Request scope: The object is available from the time an HTTP request is made until a response is sent back to the client. From another perspective, a request scope starts with a request to be issued from one view to another for navigation cases that don't perform a redirect but a default server-side forward. The scope spans across all non-view activities that follow the view of interest to the next view activity. B: The backing bean scope is comparable to the request scope, with the difference in that it exists for a specific client component. In general, all managed beans used in reusable components should be configured to backingBean scope. For example, bounded task flows that are designed to be regions on a page should use the backingBean scope if more than one instance of the task flow is expected to be on a single page. F: Application scope: An application scope object is available for the duration of the application and is shared among users. This scope may be used to hold static objects that are the same for all users. References: http://xmlandmore.blogspot.se/2009/10/types-of-scopes-in-fusion-web.html C: View scope: The object is available until the view ID for the current view activity changes. This becomes handy when you use partial page rendering. If you have a dependent list box, you might send a server request to refresh the list box. When a response is returned, the request scope will be gone but the view scope will be still there.
D: A pageFlow scope exists for each task flow instance and has a lifespan between request and session scope. The lifetime of the scope spans across all pages in a bounded task flow.
E: Session scope: The object is available for the duration of the session, which is user instance-specific. A use case for a session scope bean is a user info bean that stores information about a user, which is read from the database or an LDAP server, to avoid unnecessary queries.
Incorrect Answers:
A: Request scope: The object is available from the time an HTTP request is made until a response is sent back to the client. From another perspective, a request scope starts with a request to be issued from one view to another for navigation cases that don't perform a redirect but a default server-side forward. The scope spans across all non-view activities that follow the view of interest to the next view activity.
B: The backing bean scope is comparable to the request scope, with the difference in that it exists for a specific client component. In general, all managed beans used in reusable components should be configured to backingBean scope. For example, bounded task flows that are designed to be regions on a page should use the backingBean scope if more than one instance of the task flow is expected to be on a single page.
F: Application scope: An application scope object is available for the duration of the application and is shared among users. This scope may be used to hold static objects that are the same for all users.
References: http://xmlandmore.blogspot.se/2009/10/types-of-scopes-in-fusion-web.html
Question 3
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
