Answer in Web Development for Tom Boyle #278726
1. Which of the following would all be considered part of the presentation layer?
a. Java Persistence API (JPA), java transaction API (JTA)
b. JSF Pages, Named backing bean controller
c. MariaDB Database, Derby Database
d. EntityFacade session bean, AbstractFacade
e. None of these answers
2. Which of the following is NOT an annotation in Java EE?
c. None of these answers
3. Which of the following statements about REST is true?
a. SOAP and HTTP are two of the six architectural constraints
b. HTTP is one of the architectural constraints, but SOAP is not
c. Neither HTTP nor SOAP, even when used well, satisfy the six architectural constraints
d. HTTP, when used well, satisfies the six architectural constraints
e. None of these answers.
Presentation layer format and encrypts data to be sent across the network.
This layer takes care that the data is sent in such a way that the receiver will understand the information (data) and will be able to use the data efficiently and effectively.
Answer: a. Java Persistence API (JPA), java transaction API (JTA)
Mapping Java objects to database tables and vice versa is called Object-relational mapping (ORM). The Java Persistence API (JPA) is one possible approach to ORM. Via JPA the developer can map, store, update and retrieve data from relational databases to Java objects and vice versa.
The Java™ Transaction API (JTA) allows applications to perform distributed transactions, that is, transactions that access and update data on two or more networked computer resources.
Annotations start with ‘@’.
Answer: c. None of these answers
REST and SOAP are 2 different approaches to online data transmission. Representational state transfer (REST) is a set of architectural principles. Simple object access protocol (SOAP) is an official protocol maintained by the World Wide Web Consortium (W3C). The main difference is that SOAP is a protocol while REST is not.
Unlike REST, the HyperText Transfer Protocol (HTTP) is a standard with well-defined constraints.
the use of HTTP is not required for a RESTful system
Answer: c. Neither HTTP nor SOAP, even when used well, satisfy the six architectural constraints