Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure Data Lake Storage account that contains a staging zone.
You need to design a daily process to ingest incremental data from the staging zone, transform the data by executing an R script, and then insert the transformed data into a data warehouse in Azure Synapse Analytics.
Solution: You schedule an Azure Databricks job that executes an R notebook, and then inserts the data into the data warehouse.
Does this meet the goal?
Must use an Azure Data Factory, not an Azure Databricks job.
https://docs.microsoft.com/en-US/azure/data-factory/transform-data
You have an Azure subscription that contains a server named Server1. Server1 hosts two Azure SQL databases named DB1 and DB2.
You plan to deploy a Windows app named App1 that will authenticate to DB2 by using SQL authentication.
You need to ensure that App1 can access DB2. The solution must meet the following requirements:
App1 must be able to view only DB2.
Administrative effort must be minimized.
What should you create?
https://docs.microsoft.com/en-us/sql/relational-databases/security/contained-database-users-making-your-database-portable?view=sql-server-ver15
SIMULATION
Task 2
You need to configure your user account as the Azure AD admin for the server named sql3700689S.
To configure your user account as the Azure AD admin for the server named sql3700689S, you can use the Azure portal or the Azure CLI. Here are the steps for both methods:
Using the Azure portal:
Go to the Azure portal and selectSQL Server -- Azure Arc.
Select the server namedsql3700689Sand click onActive Directory admin.
Click onSet adminand choose your user account from the list of Azure AD users.
Click onSelectand thenSaveto confirm the change.
You can verify the Azure AD admin by clicking onActive Directory adminagain and checking the current admin.
Using the Azure CLI:
Install the Azure CLI and log in with your Azure account.
Run the following command to get the object ID of your user account:az ad user show --id <your-user-name> --query objectId -o tsv
Run the following command to set your user account as the Azure AD admin for the server:az sql server ad-admin create --server sql3700689S --object-id <your-object-id> --display-name <your-user-name>
You can verify the Azure AD admin by running the following command:az sql server ad-admin show --server sql3700689S
These are the steps to configure your user account as the Azure AD admin for the server named sql3700689S.
You have an Azure data solution that contains an enterprise data warehouse in Azure Synapse Analytics named DW1.
Several users execute adhoc queries to DW1 concurrently.
You regularly perform automated data loads to DW1.
You need to ensure that the automated data loads have enough memory available to complete quickly and
successfully when the adhoc queries run.
What should you do?
The performance capacity of a query is determined by the user's resource class.
Smaller resource classes reduce the maximum memory per query, but increase concurrency.
Larger resource classes increase the maximum memory per query, but reduce concurrency.
https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/resource-classes-for-workloadmanagement
SIMULATION
Task 10
You need to ensure that indexes are created automatically for all the databases on sql60152867. You may need to use SQL Server Management Studio and the Azure portal.
Enable Automatic tuning at the server level and turn Create Index to On.
Microsoft states that Azure SQL Database automatic tuning can create indexes automatically, verify performance improvement, and roll back changes if performance regresses. Server-level automatic tuning settings are applied to all databases on the server by default, unless a database has its own override.
Azure Portal Method --- Recommended for Simulation
Step 1: Open the SQL logical server
Sign in to the Azure portal.
Search for SQL servers.
Open:
sql60152867
Do not open only db1. The task says all databases on sql60152867, so configure this at the server level.
Step 2: Open Automatic tuning
In the SQL server left menu:
Go to Intelligent Performance.
Select Automatic tuning.
Microsoft's documented path is to open the Azure SQL server in the portal and select Automatic tuning from the menu.
Step 3: Enable automatic index creation
On the Automatic tuning page, configure:
Setting
Value
Create index
On
Drop index
Leave unchanged unless required
Force last good plan
Leave unchanged unless required
The only required setting is:
Create index = On
Do not confuse this with Drop index. The task only asks to ensure indexes are created automatically.
Step 4: Apply the setting
Select Apply or Save.
Wait for the portal confirmation.
The setting is now configured at the SQL logical server level.
Important Database Inheritance Check
This is the part people miss.
Server-level automatic tuning applies to databases that inherit from the server. Microsoft states that individual databases can override server-level automatic tuning settings. Therefore, if the simulation shows any database with custom automatic tuning settings, set that database to Inherit from server or manually set Create index = On for that database.
For each database, the correct inherited state should be:
Automatic tuning = Inherit from server
Create index = Inherited / On
If a database is set to:
Custom
Create index = Off
then the server-level setting might not affect that database. Fix it.
Database-Level T-SQL Method
Use this only if the portal is unavailable or you need to correct a specific database override.
Connect to each database and run:
ALTER DATABASE CURRENT
SET AUTOMATIC_TUNING (
CREATE_INDEX = ON
);
Microsoft documents this exact syntax for enabling the CREATE_INDEX automatic tuning option by T-SQL on an individual Azure SQL Database.
To make an individual database inherit server settings, run:
ALTER DATABASE CURRENT
SET AUTOMATIC_TUNING = INHERIT;
But this must be executed inside each database, not from master as a single server-wide T-SQL command.
Verification with T-SQL
Connect to a database and run:
SELECT
name,
desired_state_desc,
actual_state_desc
FROM sys.database_automatic_tuning_options
WHERE name = 'CREATE_INDEX';
Expected result:
name CREATE_INDEX
desired_state_desc ON or DEFAULT
actual_state_desc ON
If desired_state_desc is DEFAULT, that usually means the database is inheriting the server-level setting. The key result is:
actual_state_desc = ON
SSMS Clarification
SSMS can be used to verify or configure the setting per database using T-SQL, but it is not the best tool for the requirement as written.
Because the task says:
all the databases on sql60152867
the correct primary method is:
Azure portal > SQL server > Automatic tuning > Create index = On
Final Exam-Lab Action
Configure this:
SQL server: sql60152867
Automatic tuning
Create index: On
Apply
Then verify databases are inheriting the server setting or have CREATE_INDEX = ON.
That completes the task.
Stephanie Baker
1 month agoDaniel Perez
2 months agoCharles Lewis
2 months agoPatricia Walker
3 months agoSandra Clark
3 months agoHarold Thomas
4 months agoDennis White
4 months agoRichard Williams
5 months agoRonald Harris
5 months agoAdam Nguyen
6 months agoBrian Young
6 months agoBrenda Davis
6 months agoJennifer Morgan
6 months agoCharles Rivera
6 months agoMaria Carter
6 months agoRebecca Edwards
6 months agoKatina
7 months agoKarl
7 months agoOmer
8 months agoLisandra
8 months agoJosephine
8 months agoSunny
8 months agoAnnett
9 months agoVeronika
9 months agoAbel
9 months agoLeonida
9 months agoTracie
10 months agoJosphine
10 months agoGlory
10 months agoRana
10 months agoSabrina
10 months agoElza
11 months agoEliseo
11 months agoBrett
11 months agoAleisha
11 months agoJavier
12 months agoHassie
12 months agoSabrina
1 year agoBulah
1 year agoAmalia
1 year agoNelida
1 year agoMauricio
1 year agoArletta
1 year agoLouvenia
1 year agoJeannine
1 year agoKip
1 year agoDaniel
1 year agoLashaunda
2 years agoParis
2 years agoBeula
2 years agoElbert
2 years agoVi
2 years agoAshlee
2 years agoMerilyn
2 years agoWendell
2 years agoKayleigh
2 years agoHannah
2 years agoLeonora
2 years agoAshlee
2 years agoKenny
2 years agoCharlene
2 years agoGussie
2 years agoFelicidad
2 years agoGeorgeanna
2 years agoDierdre
2 years agoOdette
2 years agoDulce
2 years agoVernice
2 years agoArt
2 years agoGeraldo
2 years agoLindsey
2 years agoJannette
2 years ago