SC500-SQLENTRA-001SC-500Study guide skill: Implement platform-level security configurations in Azure SQLReviewed

Fabrikam's Azure SQL Database logical server SQL1 doesn't have a Microsoft Entra admin set yet. For separation of duties, the database administrator Admin1 is assigned the SQL Server Contributor role, and the security officer Sec1 is assigned the SQL Security Manager role. Without assigning any other role to either person, how should you enable Microsoft Entra-only authentication on SQL1?

  1. A. Admin1 sets the Microsoft Entra admin, and then Sec1 enables Microsoft Entra-only authenticationCorrect
  2. B. Sec1 sets the Microsoft Entra admin and then enables Microsoft Entra-only authenticationIncorrect
  3. C. Admin1 sets the Microsoft Entra admin and also enables Microsoft Entra-only authenticationIncorrect
  4. D. Sec1 deletes all existing SQL authentication logins and then enables Microsoft Entra-only authenticationIncorrect
Show answer and explanation

Answer: A

Explanation

The Microsoft Entra admin must be set before you can enable Microsoft Entra-only authentication. If the admin isn’t set, the setting remains inactive.[1] A SQL Server Contributor can set a Microsoft Entra admin, and a SQL Security Manager can change the Microsoft Entra-only authentication setting.[1] So Admin1 sets the admin, then Sec1 enables the feature, and the two roles are enough.

A SQL Security Manager can’t set or remove a Microsoft Entra admin.[1] Consistent with separation of duties, the SQL Server Contributor role doesn’t have permission to enable or disable Microsoft Entra-only authentication.[1] Microsoft Entra-only authentication doesn’t remove existing SQL authentication logins; it only prevents them from connecting, so deleting logins isn’t needed, and deleting them doesn’t set the missing admin.[1]


Sources

  1. Microsoft Entra-only authentication with Azure SQLMicrosoft Learn · Location: Feature description, Permissions, Remarks · Checked