HOTSPOT
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case.
However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review scree will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements. Existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
You have a database named Sales.
The Customer table includes a column that stores the date for the last order that the customer placed.
You plan to create a table named Leads. The Leads table is expected to contain approximately 20,000 records. Storage requirements for the Leads table must be minimized.
Tables
You need to create triggers on the Orders table that meet the following requirements:
Optimize the performance and data integrity of the tables.
Display a custom error if a user attempts to create an order for a customer that does not exist.
In the Customers table, update the value for the LastOrderPlaced field.
Complete all actions as part of the original transaction. In the table below, identify the trigger types that meet the requirements. NOTE: Make only selection in each column. Each correct selection is worth one point.
Answer: 
Explanation:
Display Custom Error: INSTEAD OF INSERT trigger Before we insert, we check if the customer already exist or not.
Update Customer table: AFTER UPDATE trigger
References:
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-trigger-transact-sql