HOTSPOT (Drag and Drop is not supported)
You configure a long-term retention policy for an Azure SQL database as shown in the exhibit. (Click the Exhibit tab.)
The first weekly backup occurred on January 4, 2020. The dates for the first 10 weekly backups are:
-January 4, 2020
-January 11, 2020
-January 18, 2020
-January 25, 2020
-February 1, 2020
-February 8, 2020
-February 15, 2020
-February 22, 2020
-February 29, 2020
-March 7, 2020
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic.
NOTE: Each correct selection is worth one point.
Hot Area:
- See Explanation section for answer.
Answer(s): A
Explanation:
Box 1: 12 months
The January 4, 2020 backup is the first backup of the month, and it will keep for 12 months.
Box 2: 10 years.
The January 11, 2020 backup is the Week 2 backup. This backup will be the yearly backup, and it will be retained for 10 years.
Note: Long-term backup retention (LTR) leverages the full database backups that are automatically created to enable point in time restore (PITR). If an LTR policy is configured, these backups are copied to different blobs for long-term storage. The copy is a background job that has no performance impact on the database workload. The LTR policy for each database in SQL Database can also specify how frequently the LTR backups are created.
To enable LTR, you can define a policy using a combination of four parameters: weekly backup retention (W), monthly backup retention (M), yearly backup retention (Y), and week of year (WeekOfYear). If you specify W, one backup every week will be copied to the long-term storage. If you specify M, the first backup of each month will be copied to the long-term storage. If you specify Y, one backup during the week specified by WeekOfYear will be copied to the long-term storage. If the specified WeekOfYear is in the past when the policy is configured, the first LTR backup will be created in the following year. Each backup will be kept in the long-term storage according to the policy parameters that are configured when the LTR backup is created.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/long-term-retention-overview?view=azuresql
Reveal Solution Next Question