Row-Level Security enables you to use group membership or execution context to control access to rows in a database table. Implement RLS by using the CREATE SECURITY POLICY Transact- SQL statement, and predicates created as inline table-valued functions.
Reference:
https://docs.microsoft.com/en-us/azure/synapse-analytics/security/synapse-workspace-synapse-rbac
https://docs.microsoft.com/en-us/security/benchmark/azure/baselines/synapse-analytics-security-baseline
https://docs.microsoft.com/en-us/sql/relational-databases/security/row-level-security?view=sql-server-ver15

Explanation:
If your top wait type is RESOURCE_SEMAHPORE and you don't have a high CPU usage issue, you may have a memory grant waiting issue.
Determine if a RESOURCE_SEMAHPORE wait is a top wait
Use the following query to determine if a RESOURCE_SEMAHPORE wait is a top wait SELECT wait_type, SUM(wait_time) AS total_wait_time_ms FROM sys.dm_exec_requests AS req JOIN sys.dm_exec_sessions AS sess ON req.session_id = sess.session_id WHERE is_user_process = 1 - GROUP BY wait_type - ORDER BY SUM(wait_time) DESC; Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/monitoring-with-dmvs

To ensure that all tables in a new Azure SQL database automatically provide cryptographic proof when data is altered and allow for auditor verification, you must enable the Ledger feature at the database level.
T-SQL to Create a Ledger Database
When creating the database, use the following T-SQL statement:
CREATE DATABASE [YourDatabaseName]
WITH LEDGER = ON;
Key Features of a Ledger Database
Automatic Enforcement: When LEDGER = ON is specified at the database level, all future tables created in that database will be ledger tables by default, even if you do not explicitly include the LEDGER = ON clause in your CREATE TABLE statements.
Tamper-Evidence: This feature uses centralized blockchain technology to cryptographically hash and link all transactions, making any unauthorized data modification evident to auditors.
Auditor Verification: Auditors can use database digests-stored in a secure, immutable location like Azure Confidential Ledger-to verify that the database's current state matches the cryptographically signed history.
Table Types: By default, new tables are created as updatable ledger tables, which maintain a history of all changes (inserts, updates, and deletes) in a transparently managed history table.
Reference:
https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-overview

https://learn.microsoft.com/en-us/answers/questions/122544/azure-sql-managed-instance-sql-agent-job-output-st

Explanation:
To configure connectivity from the Power BI service to an Azure SQL managed instance, you should use a Public endpoint for SQL1 1. You can control the connections to SQL1 by using a Network Security Group (NSG) 1. Therefore, the correct answer is Endpoint type: Public and Control connections by using: A network security group (NSG).