Administering Microsoft Azure SQL Solutions DP-300 Practice Test 63
Question 620
After remediating "A production SQL elastic job appears enabled but its schedule is set to an unintended UTC hour", which evidence BEST shows the intended outcome was achieved?
- A supported task scheduler performs the stored procedure and records execution status
- The job selects only approved tenant targets and a protected test tenant remains untouched
- Only approved database maintenance commands succeed under the job execution identity
- The execution occurs in the correct approved time window across date changes
Explanation
Correct Answer
D:The execution occurs in the correct approved time window across date changes. This observation tests the actual effect of review UTC schedule semantics and convert business time-zone requirements safely instead of assuming that a configuration change alone was successful. The underlying database behavior is that elastic job schedules use UTC and require deliberate handling of daylight-saving transitions. The control matters because entering a local wall-clock hour as UTC can run database maintenance during peak traffic.
Incorrect Answers
A:A supported task scheduler performs the stored procedure and records execution status could validate a separate fix, for example when an Azure SQL Database deployment needs recurring processing but does not support SQL Server Agent. Here the required proof is that the execution occurs in the correct approved time window across date changes. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
B:The job selects only approved tenant targets and a protected test tenant remains untouched could validate a separate fix, for example when an elastic job includes a destructive schema step that must not run against production tenants by accident. Here the required proof is that the execution occurs in the correct approved time window across date changes. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
C:Only approved database maintenance commands succeed under the job execution identity could validate a separate fix, for example when a job step connecting to customer databases fails with a permission error under its current credential. Here the required proof is that the execution occurs in the correct approved time window across date changes. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
Question 621
The team corrects "A database migration stalls because log growth exceeds the planned target storage capacity" by applying "Inspect migration telemetry storage forecast and source log generation rates". Which validation is MOST convincing?
- A repaired run drains backlog and the target storage remains within its allocation
- Connectivity and prechecks pass from the migration worker to both endpoints
- A rehearsal achieves the measured cutover RPO and business downtime target
- A trial run produces a complete cutover timeline within the approved maintenance window
Explanation
Correct Answer
A:A repaired run drains backlog and the target storage remains within its allocation. This observation tests the actual effect of inspect migration telemetry storage forecast and source log generation rates instead of assuming that a configuration change alone was successful. The underlying database behavior is that online migration lag depends on source changes and target throughput and capacity. The control matters because restarting an unchanged transfer without resolving capacity issues can recreate the backlog.
Incorrect Answers
B:Connectivity and prechecks pass from the migration worker to both endpoints could validate a separate fix, for example when a data center wants to migrate to Azure SQL Managed Instance via an approved online service. Here the required proof is that a repaired run drains backlog and the target storage remains within its allocation. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
C:A rehearsal achieves the measured cutover RPO and business downtime target could validate a separate fix, for example when a large customer database must move from SQL Server with only minutes of planned downtime. Here the required proof is that a repaired run drains backlog and the target storage remains within its allocation. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
D:A trial run produces a complete cutover timeline within the approved maintenance window could validate a separate fix, for example when a legacy database requires downtime analysis before migrating a large binary archive. Here the required proof is that a repaired run drains backlog and the target storage remains within its allocation. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
Question 622
Given the Azure SQL condition "A regulator requires Azure SQL Database files and backups encrypted while applications keep normal query access", the proposed change is "Enable or verify transparent data encryption with approved protector management". Which explanation BEST supports the change?
- End-to-end SQL transport security depends on compatible clients and validated server identities
- TDE protects database files and backups at rest without requiring each query to encrypt column values
- Azure SQL Private Link exposes a private network endpoint with controlled VNet reachability
- Azure SQL firewall rules evaluate incoming connection sources before database authentication
Explanation
Correct Answer
B:TDE protects database files and backups at rest without requiring each query to encrypt column values. This is the mechanism that makes the proposed change, enable or verify transparent data encryption with approved protector management, appropriate to the database environment described. The key limitation is that assuming TDE prevents a privileged query from reading plaintext misunderstands its purpose. A concrete confirmation is that encryption status reports the expected protector and ordinary SQL queries still function.
Incorrect Answers
A:End-to-end SQL transport security depends on compatible clients and validated server identities is a valid distinction for a different database situation, for example when a hybrid application has configured TLS for Azure SQL but legacy clients still negotiate unsupported encryption behavior. Here the determining mechanism is that tDE protects database files and backups at rest without requiring each query to encrypt column values. The alternative does not explain why the selected solution addresses this requirement.
C:Azure SQL Private Link exposes a private network endpoint with controlled VNet reachability is a valid distinction for a different database situation, for example when a PaaS SQL server allows public network access from every IPv4 address despite private connectivity policy. Here the determining mechanism is that tDE protects database files and backups at rest without requiring each query to encrypt column values. The alternative does not explain why the selected solution addresses this requirement.
D:Azure SQL firewall rules evaluate incoming connection sources before database authentication is a valid distinction for a different database situation, for example when a SQL logical server permits a broad IP firewall rule used during a former migration. Here the determining mechanism is that tDE protects database files and backups at rest without requiring each query to encrypt column values. The alternative does not explain why the selected solution addresses this requirement.
Question 623
For the requirement "A production SQL Server VM needs jobs transferred after an instance migration", the proposed remediation is "Export or recreate SQL Agent jobs schedules operators and credentials using supported methods". Which result BEST demonstrates success?
- A test event triggers the documented alert and response workflow
- A release rehearsal runs the updated job with the new procedure successfully
- The new SQL instance contains the intended jobs and a scheduled test run passes
- The service and schedule are active and an unattended execution appears in history
Explanation
Correct Answer
C:The new SQL instance contains the intended jobs and a scheduled test run passes. This observation tests the actual effect of export or recreate SQL Agent jobs schedules operators and credentials using supported methods instead of assuming that a configuration change alone was successful. The underlying database behavior is that sQL Agent job metadata belongs to the instance and requires separate migration handling. The control matters because restoring only user databases can leave production maintenance schedules absent.
Incorrect Answers
A:A test event triggers the documented alert and response workflow could validate a separate fix, for example when a DBA wants recurring alerts when a SQL Server Agent step exits with a defined error severity. Here the required proof is that the new SQL instance contains the intended jobs and a scheduled test run passes. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
B:A release rehearsal runs the updated job with the new procedure successfully could validate a separate fix, for example when a deployment replaces a stored procedure referenced by a SQL Agent job with a new parameter list. Here the required proof is that the new SQL instance contains the intended jobs and a scheduled test run passes. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
D:The service and schedule are active and an unattended execution appears in history could validate a separate fix, for example when an agent job runs successfully when launched manually but never starts on schedule. Here the required proof is that the new SQL instance contains the intended jobs and a scheduled test run passes. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
Question 624
This database condition remains unresolved: A production SQL elastic job appears enabled but its schedule is set to an unintended UTC hour. What is the MOST direct operational or security risk?
- Assigning a job owner in a central resource group does not automatically grant database access
- Storing SQL admin passwords directly in function code adds unnecessary credential exposure
- Blindly rerunning a non-idempotent script against every tenant can duplicate data modifications
- Entering a local wall-clock hour as UTC can run database maintenance during peak traffic
Explanation
Correct Answer
D:Entering a local wall-clock hour as UTC can run database maintenance during peak traffic. This concern directly arises because elastic job schedules use UTC and require deliberate handling of daylight-saving transitions. The appropriate remediation is to review UTC schedule semantics and convert business time-zone requirements safely. A successful control check would show that the execution occurs in the correct approved time window across date changes.
Incorrect Answers
A:Assigning a job owner in a central resource group does not automatically grant database access can matter in a separate case, such as when a job step connecting to customer databases fails with a permission error under its current credential. In this question, the principal consequence is that entering a local wall-clock hour as UTC can run database maintenance during peak traffic. That different risk does not best characterize the missing control in the given scenario.
B:Storing SQL admin passwords directly in function code adds unnecessary credential exposure can matter in a separate case, such as when a small database estate runs SQL automation from Azure Functions using a managed identity. In this question, the principal consequence is that entering a local wall-clock hour as UTC can run database maintenance during peak traffic. That different risk does not best characterize the missing control in the given scenario.
C:Blindly rerunning a non-idempotent script against every tenant can duplicate data modifications can matter in a separate case, such as when a DBA needs to rerun only failed SQL elastic job targets after a network interruption. In this question, the principal consequence is that entering a local wall-clock hour as UTC can run database maintenance during peak traffic. That different risk does not best characterize the missing control in the given scenario.
Question 625
A database administrator selects "Run periodic restore drills with integrity checks and application validation" after observing "A database uses append-only financial tables but a failed restore would violate the recovery objective". What mechanism makes it appropriate?
- Recoverability requires demonstrating that retained backups can produce a usable database
- Managed Instance supports native SQL Server backup restoration from Azure storage for eligible cases
- Geo-redundant backup storage can support cross-region restoration when no live secondary is available
- Azure SQL LTR provides retention beyond normal point-in-time restore windows for eligible full backups
Explanation
Correct Answer
A:Recoverability requires demonstrating that retained backups can produce a usable database. This is the mechanism that makes the proposed change, run periodic restore drills with integrity checks and application validation, appropriate to the database environment described. The key limitation is that a green backup job that was never restored cannot prove recovery time or data integrity. A concrete confirmation is that a timed test restores the database and verifies critical financial rows and permissions.
Incorrect Answers
B:Managed Instance supports native SQL Server backup restoration from Azure storage for eligible cases is a valid distinction for a different database situation, for example when a SQL Managed Instance receives a native backup file in Azure Blob Storage for approved migration. Here the determining mechanism is that recoverability requires demonstrating that retained backups can produce a usable database. The alternative does not explain why the selected solution addresses this requirement.
C:Geo-redundant backup storage can support cross-region restoration when no live secondary is available is a valid distinction for a different database situation, for example when a company needs to restore an Azure SQL database after the primary Azure Region becomes inaccessible. Here the determining mechanism is that recoverability requires demonstrating that retained backups can produce a usable database. The alternative does not explain why the selected solution addresses this requirement.
D:Azure SQL LTR provides retention beyond normal point-in-time restore windows for eligible full backups is a valid distinction for a different database situation, for example when a regulator requires Azure SQL database backup copies retained for seven years. Here the determining mechanism is that recoverability requires demonstrating that retained backups can produce a usable database. The alternative does not explain why the selected solution addresses this requirement.
Question 626
Following an approved fix for "A SQL Agent job processes the same batch twice because the scheduler was accidentally duplicated", what observation BEST confirms that it works?
- A test event triggers the documented alert and response workflow
- Job history shows one controlled run and duplicate processing does not recur
- The new SQL instance contains the intended jobs and a scheduled test run passes
- The maintenance completes during its approved window with acceptable user latency
Explanation
Correct Answer
B:Job history shows one controlled run and duplicate processing does not recur. This observation tests the actual effect of review job schedules and enforce idempotent processing where appropriate instead of assuming that a configuration change alone was successful. The underlying database behavior is that scheduling frequency and job idempotency jointly determine safe repeated execution. The control matters because simply raising the job timeout cannot prevent overlapping duplicate batch updates.
Incorrect Answers
A:A test event triggers the documented alert and response workflow could validate a separate fix, for example when a DBA wants recurring alerts when a SQL Server Agent step exits with a defined error severity. Here the required proof is that job history shows one controlled run and duplicate processing does not recur. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
C:The new SQL instance contains the intended jobs and a scheduled test run passes could validate a separate fix, for example when a production SQL Server VM needs jobs transferred after an instance migration. Here the required proof is that job history shows one controlled run and duplicate processing does not recur. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
D:The maintenance completes during its approved window with acceptable user latency could validate a separate fix, for example when a database integrity-check job times out only when it overlaps high-traffic business hours. Here the required proof is that job history shows one controlled run and duplicate processing does not recur. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
Question 627
For the requirement "A mobile app needs a secure secret that rotates without changing its compiled SQL client library", the proposed remediation is "Use an authorized identity to retrieve secrets from Key Vault or supported identity-based access". Which result BEST demonstrates success?
- The database uses the approved protector and tested key-rotation access remains healthy
- Approved workloads connect privately and an unrelated network cannot reach the SQL service
- Rotation succeeds without redeployment and old credentials stop authenticating
- The authorized application decrypts the token while unprivileged queries cannot
Explanation
Correct Answer
C:Rotation succeeds without redeployment and old credentials stop authenticating. This observation tests the actual effect of use an authorized identity to retrieve secrets from Key Vault or supported identity-based access instead of assuming that a configuration change alone was successful. The underlying database behavior is that external key and credential management decouples secret lifecycle from application binaries. The control matters because embedding a SQL password in a mobile binary can expose it to extraction and reuse.
Incorrect Answers
A:The database uses the approved protector and tested key-rotation access remains healthy could validate a separate fix, for example when a payment database has a customer-managed TDE protector requirement. Here the required proof is that rotation succeeds without redeployment and old credentials stop authenticating. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
B:Approved workloads connect privately and an unrelated network cannot reach the SQL service could validate a separate fix, for example when a security team wants a database rule that allows only approved application subnets over Azure SQL private networking. Here the required proof is that rotation succeeds without redeployment and old credentials stop authenticating. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
D:The authorized application decrypts the token while unprivileged queries cannot could validate a separate fix, for example when a finance database stores a small API token column that requires SQL-side encryption using managed secrets. Here the required proof is that rotation succeeds without redeployment and old credentials stop authenticating. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
Question 628
After remediating "A platform team schedules one task across an elastic pool that gains new tenant databases weekly", which evidence BEST shows the intended outcome was achieved?
- A triggered run authenticates with managed identity and only the intended SQL operation succeeds
- A supported task scheduler performs the stored procedure and records execution status
- The agent reads its metadata from the configured job database and starts a test job
- The next scheduled run includes a newly created eligible tenant database
Explanation
Correct Answer
D:The next scheduled run includes a newly created eligible tenant database. This observation tests the actual effect of configure an elastic job target group to enumerate supported pool or server targets dynamically instead of assuming that a configuration change alone was successful. The underlying database behavior is that elastic jobs can resolve target databases when jobs run under a supported target group definition. The control matters because hard-coding every tenant database ID can leave newly provisioned tenants unmaintained.
Incorrect Answers
A:A triggered run authenticates with managed identity and only the intended SQL operation succeeds could validate a separate fix, for example when a small database estate runs SQL automation from Azure Functions using a managed identity. Here the required proof is that the next scheduled run includes a newly created eligible tenant database. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
B:A supported task scheduler performs the stored procedure and records execution status could validate a separate fix, for example when an Azure SQL Database deployment needs recurring processing but does not support SQL Server Agent. Here the required proof is that the next scheduled run includes a newly created eligible tenant database. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
C:The agent reads its metadata from the configured job database and starts a test job could validate a separate fix, for example when a new elastic job agent exists but cannot create jobs because no supporting job database is configured. Here the required proof is that the next scheduled run includes a newly created eligible tenant database. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.
Question 629
A database administrator selects "Validate the supported migration service consistency and controlled final cutover procedure" after observing "A transaction-heavy system needs data consistency during an online migration". What mechanism makes it appropriate?
- Change synchronization and a write freeze at cutover protect in-flight transaction consistency
- Migration connectivity authorization and target readiness are required before the data stream can succeed
- Azure SQL Database feature boundaries can require application-level data access redesign
- Offline migration can simplify movement when the business permits an interruption of writes
Explanation
Correct Answer
A:Change synchronization and a write freeze at cutover protect in-flight transaction consistency. This is the mechanism that makes the proposed change, validate the supported migration service consistency and controlled final cutover procedure, appropriate to the database environment described. The key limitation is that allowing concurrent writes on both endpoints without conflict handling risks divergence. A concrete confirmation is that source and target validation reconcile committed business transactions after the switchover.
Incorrect Answers
B:Migration connectivity authorization and target readiness are required before the data stream can succeed is a valid distinction for a different database situation, for example when a data center wants to migrate to Azure SQL Managed Instance via an approved online service. Here the determining mechanism is that change synchronization and a write freeze at cutover protect in-flight transaction consistency. The alternative does not explain why the selected solution addresses this requirement.
C:Azure SQL Database feature boundaries can require application-level data access redesign is a valid distinction for a different database situation, for example when an application moves from SQL Server on a VM to Azure SQL Database and uses three-part naming. Here the determining mechanism is that change synchronization and a write freeze at cutover protect in-flight transaction consistency. The alternative does not explain why the selected solution addresses this requirement.
D:Offline migration can simplify movement when the business permits an interruption of writes is a valid distinction for a different database situation, for example when a payroll database permits weekend downtime and requires a low-complexity transfer to Azure SQL. Here the determining mechanism is that change synchronization and a write freeze at cutover protect in-flight transaction consistency. The alternative does not explain why the selected solution addresses this requirement.
Question 630
Given the Azure SQL condition "A development team confuses a geo-redundant backup with a hot readable secondary in Azure SQL", the proposed change is "Differentiate geo-restore from active geo-replication or a failover group". Which explanation BEST supports the change?
- HA replicas replicate operational changes and might replicate accidental deletion or corruption
- Geo-redundant backups support restoration after disaster but are not continuously queryable replicas
- Managed Instance failover groups coordinate geo-secondary instances under platform restrictions
- Hybrid HA/DR depends on supported SQL topology authentication and network latency across sites
Explanation
Correct Answer
B:Geo-redundant backups support restoration after disaster but are not continuously queryable replicas. This is the mechanism that makes the proposed change, differentiate geo-restore from active geo-replication or a failover group, appropriate to the database environment described. The key limitation is that planning read-only reporting against backup storage rather than a replica will fail. A concrete confirmation is that the DR architecture explicitly identifies backup-restore versus live-secondary capabilities.
Incorrect Answers
A:HA replicas replicate operational changes and might replicate accidental deletion or corruption is a valid distinction for a different database situation, for example when a recovery strategy needs to protect against operator deletion as well as infrastructure outage. Here the determining mechanism is that geo-redundant backups support restoration after disaster but are not continuously queryable replicas. The alternative does not explain why the selected solution addresses this requirement.
C:Managed Instance failover groups coordinate geo-secondary instances under platform restrictions is a valid distinction for a different database situation, for example when an organization operates a mission-critical SQL Managed Instance and wants cross-region continuity. Here the determining mechanism is that geo-redundant backups support restoration after disaster but are not continuously queryable replicas. The alternative does not explain why the selected solution addresses this requirement.
D:Hybrid HA/DR depends on supported SQL topology authentication and network latency across sites is a valid distinction for a different database situation, for example when a bank operates on-premises SQL Server with an Azure virtual machine as disaster recovery. Here the determining mechanism is that geo-redundant backups support restoration after disaster but are not continuously queryable replicas. The alternative does not explain why the selected solution addresses this requirement.