In this section you will see one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem, and you must determine whether the solution meets the stated goals. More than one solution might solve the problem. It is also possible that none of the solutions solve the problem.

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.

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 stayed 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 on the review screen.

You have a Microsoft Azure Database for MySQL server named SQLDB1.

Four database administrators manage SQLDB1.

You need to prevent any administrator from deleting the server that hosts SQLDB1.

Solution: You create a delete lock on the server resource in Azure.

Does this meet the goal?

A. Yes

B. No

Explanation:

As an administrator, you may need to lock a subscription, resource group, or resource to prevent other users in your organization from accidentally deleting or modifying critical resources. You can set the lock level to CanNotDelete or ReadOnly. In the portal, the locks are called Delete and Read-only respectively. It can help prevent accidental deletion resources such as a SQL Server by adding a level of protection.

Example: A lock that will prevent the server from being deleted and provide a note that it should never be deleted.

References: https://blogs.msdn.microsoft.com/azuresqldbsupport/2017/06/19/protecting-deletions-of-azure-sql-resources/