Configure and manage automation of tasks →mediumMultiple ChoiceObjective-mapped

DP-300 Configure and manage automation of tasks Practice Question

Exhibit

Refer to the exhibit.

$params = @{
    ResourceGroupName = 'rg-sql-prod'
    ServerName = 'sql-prod-01'
    DatabaseName = 'SalesDB'
    Edition = 'Standard'
    RequestedServiceObjectiveName = 'S3'
    ElasticPoolName = 'pool-prod'
}

Set-AzSqlDatabase @params

Refer to the exhibit. A PowerShell script is used to update an Azure SQL Database. The script runs without errors, but the database is not moved to the specified elastic pool. What is the most likely cause?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The script sets both Edition and RequestedServiceObjectiveName, which is invalid when moving to an elastic pool.

The Set-AzSqlDatabase cmdlet can move a database into an elastic pool by specifying the ElasticPoolName parameter. However, when moving a database to an elastic pool, you must not specify the RequestedServiceObjectiveName parameter because the service objective is determined by the pool. The script incorrectly sets both Edition and RequestedServiceObjectiveName, causing a conflict. Option C correctly identifies this issue. Option A is incorrect because the pool not existing would cause an error, not a silent failure. Option B is incorrect because the ServerName parameter does not require a fully qualified domain name; the resource group and server name suffice. Option D is incorrect because the -Force parameter is not required for pool moves.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The elastic pool 'pool-prod' does not exist.
Why it's wrong here
The script runs without errors, so the pool likely exists.
✗
The ServerName parameter is missing the fully qualified domain name.
Why it's wrong here
The ServerName is just the name; the cmdlet assumes the domain.
✓
The script sets both Edition and RequestedServiceObjectiveName, which is invalid when moving to an elastic pool.
Why this is correct
When moving a database to an elastic pool, you should not specify RequestedServiceObjectiveName; the pool's tier determines the service objective.
✗
The cmdlet requires the -Force parameter to move a database.
Why it's wrong here
-Force is used to suppress confirmation, not required for the operation to succeed.

Go deeper

DP-300 Configure and manage automation of tasks Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question