Answer:
C) OpenID Connect
Explanation:
The best option is OpenID Connect because is based in OAuth, and supports multiple web based and mobile clients, and supports REST.
With OAuth, we cannot make any user authentication just provide a token to access data.
RADIUS is a networking protocol, and Shibboleth is a single sign-on log-in system for computer networks and the Internet, both not support REST.
Answer: TOS
Explanation:
Terms of service is the agreement and the set of rules and regulations for the site visitors. It include all the terms and condition or the disclaimer when addressing the particular website.
Terms of service are set before designing the any type of the site and content in the system that restrict all the types of business that the users conduct in the site.
Answer:
Joe should read the explanatory text and complete the learning activities.
Explanation:
Given
See attachment for options
Required
Best strategy to get through the module
First off, rushing through the activities and taking guess for each question (as suggested by (a)) will not help him;
He may complete the activities but sure, he won't learn from the module.
Also, reading through the units without completing the activities is not an appropriate method because Joe will not be able to test his knowledge at the end of the module.
The best strategy to employ is to read through the units and complete the activities, afterwards (option (b)).
Answer:
1) Yes, Publisher relation should have a publisherID primary key.
2) NOT NULL and UNIQUE for the BookID, BranchID, CardNumber and name of the borrower in the Book, Book_Copies, Library_branch, and Borrower relations respectively. The DueDate field of the book_loan relation must be a time constraint. The BookID of the Book relation must be serial number for automatic addition and update of bookid across the database.
Explanation:
The Publisher relation should have primary key publisherID which should replace the publisherName in the Book relation to easily make a join query and attain a third-level database model.
