Azure SQL Database, Create, configure, and manage elastic jobs
There are two methods of authentication for the job agent to target server(s)/database(s), Microsoft Entra authentication with a user-assigned managed identity (UMI), or database-scoped credentials.
Reference:
https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-jobs-tutorial

Explanation:
Box 1: max_worker_percent
Maximum concurrent workers (requests) in percentage of the limit of the database's service tier.
Box 2: dm_db_resource_stats:
This dynamic management view (DMV) in Azure SQL Database provides real-time resource utilization data.
The query SELECT avg_memory_usage_percent FROM sys. is used in Azure SQL Database to retrieve the average memory usage percentage of a database. This information is provided by the sys.dm_db_resource_stats dynamic management view (DMV). The avg_memory_usage_percent column represents the average memory usage as a percentage of the maximum allowed memory for the database's service tier and performance level.
Reference:
https://learn.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-db-resource-stats-azure-sql-database

Automatic tuning is a fully managed intelligent performance service that uses built-in intelligence to continuously monitor queries executed on a database, and it automatically improves their performance.
Automatic tuning for Azure SQL Database uses the CREATE INDEX, DROP INDEX, and FORCE LAST GOOD PLAN database advisor recommendations to optimize your database performance.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-overview

Explanation:
The NCHAR(10) data type is a fixed-length Unicode character data type. Each character in NCHAR takes 2 bytes because it uses UTF-16 encoding. Therefore, NCHAR(10) will always occupy 20 bytes on disk (2 bytes per character for 10 characters), not 10 bytes. However, the statement is asking if each field occupies 10 bytes, which is misleading; it should be 20 bytes.
The statement "ALTER TABLE table1 REBUILD WITH (DATA_COMPRESSION = ROW);" specifies row-level compression, not dictionary compression. Row compression reduces the size of the data by storing fixed-length data types in variable-length storage format and by reducing metadata overhead. Dictionary compression is a feature of page compression, not row compression.
Column1 (TINYINT): Supports compression. Row compression can store this as a smaller size if possible. Column2 (VARCHAR(255)): Supports compression. Row compression can store only the used length of the string. Column4 (BINARY(50)): Supports compression. Row compression can store binary data more efficiently by removing unnecessary padding.

Azure Private Link enables you to access Azure PaaS Services (for example, Azure Storage and SQL Database) and Azure hosted customer-owned/partner services over a private endpoint in your virtual network.
Traffic between your virtual network and the service travels the Microsoft backbone network.
Exposing your service to the public internet is no longer necessary.
Reference:
https://docs.microsoft.com/en-us/azure/private-link/private-link-overview