DP-201 Exam QuestionsBrowse all questions from this exam
Go to Exam

DP-201 Exam - Question 151

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

A company is developing a solution to manage inventory data for a group of automotive repair shops. The solution will use Azure Synapse Analytics as the data store.

Shops will upload data every 10 days.

Data corruption checks must run each time data is uploaded. If corruption is detected, the corrupted data must be removed.

You need to ensure that upload processes and data corruption checks do not impact reporting and analytics processes that use the data warehouse.

Proposed solution: Insert data from shops and perform the data corruption check in a transaction. Rollback transfer if corruption is detected.

Does the solution meet the goal?

Show Answer
Correct Answer: B

The proposed solution does not meet the goal. Performing data corruption checks within the same transaction as the data insert means that the data insertion process could impact the reporting and analytics processes, as they could be paused while the transaction is still open. Ideally, data should be uploaded to a staging area where corruption checks can be performed before moving the validated data to the main database, thereby ensuring that reporting and analytics processes are not affected during uploads.

Discussion

3 comments
Sign in to comment
services1
Jun 10, 2021

why not just upload to a separate table and drop it if it is corrupted, move it over if it isn't

azurrematt123
Jun 16, 2021

Yes Absolutely, populate to a staging table and run your data corruption checks there.

BigMF
Jun 14, 2021

I feel the answer should be NO. If the data is loaded and found to be corrupt, it's possible reporting has already been performed on the bad data before the data can be reset to the restore point and therefore reporting WAS impacted.

lgtiza
Aug 15, 2021

But technically the proposed solution is correct. I wouldn't do it this way -I prefer the staging table- but from a technical perspective the answer could be YES. Any other thoughts on why it would be NO?