Explanation:
You are loading data into Table1, which means there is some inserts going on. Note that insert statements is also considered a query. It should be scale resource in order to reduce the time insert data into Table1.

Configure a license-free standby replica (preview) for Azure SQL Database You can save on licensing costs by designating your secondary disaster recovery (DR) database for standby when using Azure SQL Database.
Configure a standby replica
You can designate a replica for standby when you configure a new active geo-replication relationship by using the Azure portal, PowerShell, or the Azure CLI.
To create a new active geo-replication relationship and designate your secondary database for standby in the Azure portal, follow these steps:
Step 1: Go to your SQL database [Here db1] resource in the Azure portal.
Step 2: Choose Replicas under Data management from the resource menu, and then select + Create replica to open the Create SQL Database - Geo Replica page.

Step 3: On the Create SQL Database - Geo Replica page, select Standby replica for Replica type under Replica configuration. Check the box to confirm you'll use the replica for standby.

Step 4: Provide a new or existing server for the new standby database and then use Review + create to do a final validation of your database and server details.
Step 5: Use Create to confirm your settings and create your new standby database replica.
Reference:
https://learn.microsoft.com/en-us/azure/azure-sql/database/standby-replica-how-to-configure

This procedure is necessary and correct, as there is no option in Azure SQL Database to directly restore a database.
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/statements/restore-statements-transact-sql

Explanation:
Box 1: CREATE EXTERNAL TABLE
An external table points to data located in Hadoop, Azure Storage blob, or Azure Data Lake Storage. External tables are used to read data from files or write data to files in Azure Storage.
With Synapse SQL, you can use external tables to read external data using dedicated SQL pool or serverless SQL pool.
Syntax:
CREATE EXTERNAL TABLE { database_name.schema_name.table_name |
schema_name.table_name | table_name }
( <column_definition> [ ,...n ] )
WITH (
LOCATION = 'folder_or_filepath',
DATA_SOURCE = external_data_source_name,
FILE_FORMAT = external_file_format_name
Box 2. OPENROWSET
When using serverless SQL pool, CETAS is used to create an external table and export query results to Azure Storage Blob or Azure Data Lake Storage Gen2.
Example:
AS
SELECT decennialTime, stateName, SUM(population) AS population FROM
OPENROWSET(BULK
'https://azureopendatastorage.blob.core.windows.net/censusdatacontainer/ release/us_population_county/year=*/*.parquet', FORMAT='PARQUET') AS [r] GROUP BY decennialTime, stateName GO Reference:
https://docs.microsoft.com/en-us/azure/synapse-analytics/sql/develop-tables-external-tables

Explanation:
Send application metrics using Dropwizard.
Spark uses a configurable metrics system based on the Dropwizard Metrics Library.
To send application metrics from Azure Databricks application code to Azure Monitor, follow these steps:
Step 1: Configure your Azure Databricks cluster to use the Databricksmonitoring library.
Prerequisite: Configure your Azure Databricks cluster to use the monitoring library.
Step 2: Build the spark-listeners-loganalytics-1.0-SNAPSHOT.jar JAR file Step 3: Create Dropwizard counters in your application code Create Dropwizard gauges or counters in your application code