Explanation:
Box 1: Column encryption Key
Always Encrypted uses two types of keys: column encryption keys and column master keys. A column encryption key is used to encrypt data in an encrypted column. A column master key is a key-protecting key that encrypts one or more column encryption keys.
Incorrect Answers:
TDE encrypts the storage of an entire database by using a symmetric key called the Database Encryption Key (DEK).
Box 2: Deterministic
Always Encrypted is a feature designed to protect sensitive data, such as credit card numbers or national identification numbers (for example, U.S. social security numbers), stored in Azure SQL Database or SQL Server databases. Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to the Database Engine (SQL Database or SQL Server).
Always Encrypted supports two types of encryption: randomized encryption and deterministic encryption. Deterministic encryption always generates the same encrypted value for any given plain text value. Using deterministic encryption allows point lookups, equality joins, grouping and indexing on encrypted columns.
Incorrect Answers:
Randomized encryption uses a method that encrypts data in a less predictable manner.
Randomized encryption is more secure, but prevents searching, grouping, indexing, and joining on encrypted columns.
Transparent data encryption (TDE) helps protect Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics against the threat of malicious offline activity by encrypting data at rest. It performs real-time encryption and decryption of the database, associated backups, and transaction log files at rest without requiring changes to the application.
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine

Explanation:
Box 1: sqlserver.login
This is an abbreviated version of process_login_finish, containing only the columns required by external monitoring telemetry pipeline.
Use this for Box 1 as it has fewer parameters.
Box 2: sqlserver.process_login_finish
This event is generated when server is done processing a login (success or failure).
Reference:
https://www.sqlskills.com/blogs/bobb/over-1000-xevents-in-sql-server-2016-ctp2-here-are-the-new-ones/

Manage administrator accounts in Azure Active Directory B2C
You can assign a role when you create a user or invite a guest user. You can add a role, change the role, or remove a role for a user:
Solution 1:
Provision Microsoft Entra admin (SQL Managed Instance)
Your SQL Managed Instance needs permission to read Microsoft Entra ID to accomplish tasks such as authentication of users through security group membership or creation of new users. For this to work, you must grant the SQL Managed Instance permission to read Microsoft Entra ID.
You can do this using the Azure portal or PowerShell.
To grant your SQL Managed Instance read permissions to Microsoft Entra ID using the Azure portal, sign in as a Global Administrator and follow these steps:
Step 1: In the Azure portal, in the upper-right corner select your account, and then choose Switch directories to confirm which directory is your Current directory. Switch directories, if necessary.

Step 2: Choose the correct Microsoft Entra directory as the Current directory.
This step links the subscription associated with Microsoft Entra ID to the SQL Managed Instance, ensuring the Microsoft Entra tenant and SQL Managed Instance use the same subscription.
Step 3: Now, you can choose your Microsoft Entra admin for your SQL Managed Instance. For that, go to your managed instance resource in the Azure portal and select Microsoft Entra admin under Settings.

Step 4: Select the banner on top of the Microsoft Entra admin page and grant permission to the current user.

Step 5: After the operation succeeds, the following notification will show up in the top-right corner:

Step 6: On the Microsoft Entra admin page, select Set admin from the navigation bar to open the Microsoft Entra ID pane.

Step 7: On the Microsoft Entra ID pane, search for a user, check the box next to the user or group to be an administrator, and then press Select to close the pane and go back to the Microsoft Entra admin page for your managed instance. [Select yourself] Step 8: From the navigation bar of the Microsoft Entra admin page for your managed instance, select Save to confirm your Microsoft Entra administrator.

The process of changing the administrator might take several minutes. Then the new administrator appears in the Microsoft Entra admin box.
Solution 2:
Step 1: Sign in to the Azure portal with Global Administrator or Privileged Role Administrator permissions.
Step 2: (If you have access to multiple tenants, select the Settings icon in the top menu to switch to your Azure AD B2C tenant from the Directories + subscriptions menu.) Step 3: Under Azure services, select Azure AD B2C. Or use the search box to find and select Azure AD B2C.
Step 4: Under Manage, select Users.
Step 5: Select the user you want to change the roles for. [Select your user account]. Then select Assigned roles.
Step 6: Add a role assignment
Step 7: Select Add assignments, select the role to assign (for example, Application administrator),
[Select Microsoft Entra administrator] and then choose Add.
Reference:
https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure
https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-manage- administrator

General purpose has disk latency, Business critical puts the logs on SSD, Premium is a DTU offering which is not supported on Azure SQL MI, Hyperscale is not on Managed Instance.

Explanation:
Note: There is also another older very similar question with three steps, instead of four.
Unfreeze in two steps in this version.
Step 1: ALTER SERVER CONFIGURATION SET SUSPEND_FOR_SNAPSHOT_BACKUP = ON (GROUP = (DB1, DB2), MODE = COPY_ONLY); ALTER SERVER CONFIGURATION ... GROUP = (DB1, DB2): Freezes the write I/O on multiple specified databases simultaneously. This keeps other databases on the server unaffected, which rules out BACKUP SERVER or instance-wide alternatives.
Suspend multiple user databases for snapshot backup
If multiple databases on the same underlying disk, you could suspend multiple databases with the following command.
ALTER SERVER CONFIGURATION
SET SUSPEND_FOR_SNAPSHOT_BACKUP = ON
(GROUP = (testdb1, testdb2));
Step 2: BACKUP GROUP DB1, DB2 TO DISK = 'D:\Backups\GroupSnapshot.bkm' WITH METADATA_ONLY, FORMAT; Perform snapshots of multiple databases simultaneously with the new BACKUP GROUP and BACKUP SERVER commands. With this option, snapshots can be performed at the snapshot granularity of the underlying storage, eliminating the need to perform a snapshot of the same disk multiple times.
Step 3: ALTER DATABASE DB1
SET SUSPEND_FOR_SNAPSHOT_BACKUP = OFF
Resume write I/O on the DB1 to unfreeze the databases for normal operation.
In SQL Server 2022, the command ALTER DATABASE databasename SET
SUSPEND_FOR_SNAPSHOT_BACKUP = OFF unfreezes a database's write I/O operations and resumes normal database processing. It explicitly cancels or ends a manual database freeze state that was previously initiated for a storage-level backup.
Step 4: ALTER DATABASE DB2
SET SUSPEND_FOR_SNAPSHOT_BACKUP = OFF
Resume write I/O on the DB2 to unfreeze the databases for normal operation.
Reference:
https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/create-a-transact-sql-snapshot-backup