All questions pertain to the Billington Pharmaceuticals case study.
| Question 1 | You have determined that to handle prescriptions, a patient can be on more than one drug from one or more prescriptions, have more than one doctor, but have only a single HMO. Based on this information, which of the following relationships are correct? (Choose all that apply.) A. Doctor 1-* Doctor-HMO *-1 HMO B. Patient 1-* Prescription C. Patient 1-* Drug D. Doctor *-1 Doctor-Patient 1-* E. Prescription 1-* Prescription-Drug *-1 Drug
|
| A1: | The correct answers are B and E. The doctor and HMO should not be related (this might even be illegal in the United States), so answer A is incorrect. The patient is likely to have many prescriptions, so answer B is correct. The correct relationship of Patient to Drug should be through the Prescription entity, so answer C is incorrect. Answer D is incorrect, as it has reversed the relationship (many doctors to one patient/doctor) and should be represented as a many-to-many relationship. A single prescription can contain multiple drugs and each drug can be found on many prescriptions, so answer E is correct. |
| Question 2 | A signed and dated prescription from a physician's office indicates what patient is to have which drug (or drugs). The prescription has the date, doctor's name, address information for the office, drug, route (drug medium), and dosage/frequency. Given that you are planning separate entities for Doctor, Patient, HMO, Prescription, and Drug, which of the following attributes would not belong as part of the Prescription entity? |
| A2: | The correct answer is B. In a normalized data structure, the doctor's information would be maintained in the Doctor entity, with only an ID in the Prescription entity. The prescription date, prescription ID, and patient ID are all prescription-specific information that would likely stay within the entity. |
| Question 3 | For non-prescription items ordered from the Web site, customer information will be maintained and stored in the Patient entity. General order information will be maintained in an Order entity, and details for each item purchased will be maintained in an Order Item entity. Which of the following keys are needed in the Order entity? (Choose all that apply.) A. A primary key called Order B. A foreign key called Patient C. A foreign key called Order Item D. A primary key called Order Item E. A foreign key called Order Date
|
| A3: | The correct answers are A and B. The Order entity requires a primary key so that each item in the Order Item table can be related back to the correct order. Answer A serves this purpose. The Order itself must relate back to the correct customer, and answer B serves this purpose. The Order Item primary key is required in the Order Item entity, not the Order entity. There is no need for an Order Item or Order Date foreign key anywhere in the system as described. |
| Question 4 | For non-prescription items ordered from the Web site, customer information will be maintained and stored in the Patient entity. General order information will be maintained in an Order entity, and details for each item purchased will be maintained in an Order Item entity. Which of the following represents the data relationships? (Choose all that apply.) A. Patient 1-* Order B. Patient 1-* Order *-1 Order Item C. Order 1-* Order Item D. Patient *-1 Order 1-* Order Item E. Patient 1-* Order Item
|
| A4: | The correct answers are A and C. Each customer can make multiple orders, and each order can have multiple items. Answer B indicates that each order could have only one item, which, of course, is incorrect. Answer D indicates that each customer can make only one order and the order can be shared by multiple customers, both of which are incorrect. Answer E directly relates the customer information with the Order Item entity without using the Order entity. This direct relationship is incorrect. |
| Question 5 | A Call entity is needed to record the calls that the "on call" pharmacist and help desk staff answer. This entity must track information about the caller. Each caller must be recognized in the Patient or Doctor entity. Date and time information and a short description of the call need to be able to be recorded. Which of the following attributes would not be needed in the Call entity? A. Call Date-Time B. Call ID C. Doctor ID D. Patient ID E. Doctor-Patient ID
|
| A5: | The correct answer is E. The Patient and Doctor IDs need to be separate attributes. Each attribute could be Null if the other contains data; answers C and D serve this purpose. A Call ID would be used as a surrogate primary key, and the call's date and time could be held in a single attribute, as required by the definition. |
| Question 6 | A Call entity is needed to record the calls that the "on call" pharmacist and help desk staff answer. This entity must track information about the caller. Each caller must be recognized in the Patient or Doctor entity. Date and time information and a short description of the call need to be able to be recorded. Which of the following represents the correct relationship of the Call entity to the other system entities? (Choose all that apply.) |
| A6: | The correct answers are A and B. A patient or a doctor can have one or more calls. Calls are not shared by multiple patients and/or doctors, as in answers C and D. Answer E is incorrect because there is no direct correlation of the Patient entity to the calls, except through a doctor, and it is not a system requirement that the doctor make the call on behalf of the patient. |
| Question 7 | You need statistical analysis by U.S. or Canadian regions for both patients and doctors. You would like to know if Billington's services are more popular in one state or province than another. This information would help you create promotional materials for Billington. What must be done to the logical structure to support this functionality? A. Decompose all address data into separate attributes. B. Decompose the address elements of the patient and doctor into separate attributes. C. Create a Region entity to record statistical information for each state and province. D. Develop a concatenation process for the applications to analyze the regional data. E. Develop a parsing process for the applications to analyze the regional data.
|
| A7: | The correct answer is B. By decomposing the address attribute into its separate entries, you can achieve statistical gathering based on the attribute's divisions. In answer A, you also assume the HMO address to be decomposed, which is unnecessary given the problem statement; often this type of decomposition is present in normalized systems, however. Concatenation brings elements together, which is undesirable at this stage, and parsing data adds an unnecessary level of processing, which can be avoided with a fully normalized data structure. |
| Question 8 | You are preparing a Web service model for use in the Billington Web site and are in the data definition phase of this design. You need to prepare a model of the data that is suitable for use with this new service. What type of model will you be preparing? |
| A8: | The correct answer is A. At this stage, the ER model has likely already been prepared, and because the design is for data used in a Web service, the XML schema to be used on the site needs to be developed. The logical and physical database models and database schema would be done outside the scope of the Web service development. |
| Question 9 | There are a number of possible relationships that when modeled will have a many-to-many dependency requiring associate joining tables. Which of the following represents possible many-to-many relationships in the system? (Choose all that apply.) A. Doctor - Patient B. Prescription - Drug C. Patient - HMO D. Order - Product E. Patient - Call
|
| A9: | The correct answers are A, B, and D. A doctor can have many patients, and the reverse is true as well. A prescription can have multiple medications on it, and each medication can be present on multiple prescriptions. An order can have multiple products, and each product multiple orders. An HMO will have many patients, but the reverse is not true. A patient can have many calls but each call is made by a single patient (or doctor). |
| Question 10 | A Product entity is needed to contain information for the selection of products that can be ordered. This entity must contain references to the supplier of the product, provide information about the product itself, and track the current selling price as well as the last price paid to the supplier. Which of the following attributes would not be needed in the Call entity? A. Brand B. Product Description C. Selling Price D. Supplier ID E. Order Item ID
|
| A10: | The correct answer is E. The order item ID will be an identifier of the order item table and most likely its primary key, but will not be referenced by the Product entity. The Product entity will most likely require brand and description information and a selling price as stated in the problem. The Supplier ID will be required to indicate the company from which the product is ordered. |
