Exam Bundle

Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan. That result is evidence for another corrective change: Choose appropriate compute or storage scaling rules and evaluate tier features and transition effects against the workload schedule. The alternative problem is: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. The current Westhaven Retail issue is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. Its decisive acceptance evidence would be: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

The host maintains acceptable available memory and paging while SQL workload throughput meets measured targets. That result is evidence for another corrective change: Reserve adequate operating-system and auxiliary-service memory and configure supported max server memory for the SQL instance. The alternative problem is: An SQL Server VM uses default max server memory so database memory pressure causes the Windows host to page heavily under load. The current Westhaven Retail issue is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. Its decisive acceptance evidence would be: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

The post-change workload meets read latency while insert, update and maintenance overhead remain inside agreed limits. That result is evidence for another corrective change: Benchmark index effects against representative reads and writes and adopt only a change with acceptable total workload impact. The alternative problem is: An automatic tuning advisor proposes an index that speeds one query but increases insert cost substantially, and the DBA accepts it without validating overall load. The current Westhaven Retail issue is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. Its decisive acceptance evidence would be: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

Check compatibility and eligibility for supported scalar UDF inlining or refactor the function to an efficient set-based expression. That relates to a separate SQL administration problem: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. The Brookside Manufacturing requirement is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

Evaluate and configure supported automatic tuning settings and monitor each action for workload benefit or rollback. That relates to a separate SQL administration problem: An Azure SQL Database with supported automatic tuning is left unmanaged despite repeated regressions and validated index recommendations. The Brookside Manufacturing requirement is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

Use measured fragmentation, page count, workload effects and supported maintenance guidance to choose a targeted index maintenance policy. That relates to a separate SQL administration problem: A fragmented heavily updated index is rebuilt every hour regardless of its size or actual query benefit, causing unnecessary log and CPU activity. The Brookside Manufacturing requirement is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

The target database uses the intended setting while an unrelated database retains its original optimizer behavior. That result is evidence for another corrective change: Evaluate supported database-scoped configuration or query-level hints rather than unnecessary global engine setting changes. The alternative problem is: A database owner changes instance-wide optimizer settings to solve one compatibility-sensitive database problem that could be scoped locally. The current Brookside Manufacturing issue is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. Its decisive acceptance evidence would be: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

After adjustment the maintenance operation completes without sustained log saturation and log growth is bounded. That result is evidence for another corrective change: Plan selective index maintenance and log sizing with observed change volume and appropriate transaction log I/O capacity. The alternative problem is: A database job performs frequent full-index rebuilds but the associated transaction log grows faster than its configured throughput can handle. The current Brookside Manufacturing issue is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. Its decisive acceptance evidence would be: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

A controlled integrity check completes with a documented clean result or produces an actionable corruption report. That result is evidence for another corrective change: Schedule supported database integrity validation and define remediation and restore responses for corruption findings. The alternative problem is: A production SQL Server has never run DBCC CHECKDB and a backup success email is treated as proof of database structural integrity. The current Brookside Manufacturing issue is instead: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. Its decisive acceptance evidence would be: A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable.

Choose a least-privilege job owner or supported proxy/credential configuration and scope each job step's required permissions. That relates to a separate SQL administration problem: A nightly Agent job uses a high-privilege SQL login for routine index maintenance even though a narrower execution context is possible. The Alpine Healthcare requirement is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. That approach does not directly establish the required fix; the requested acceptance evidence is: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

Identify SQL Server Agent dependencies and redesign suitable recurring tasks using supported elastic jobs or Azure automation services. That relates to a separate SQL administration problem: A migration from SQL Server to Azure SQL Database assumes every SQL Server Agent job will continue to run inside the single database service. The Alpine Healthcare requirement is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. That approach does not directly establish the required fix; the requested acceptance evidence is: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

Consolidate schedule definitions and implement idempotent task behavior or mutual exclusion for the recurring import. That relates to a separate SQL administration problem: An Agent job has multiple overlapping schedules and duplicate nightly imports, causing a unique key violation every morning. The Alpine Healthcare requirement is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. That approach does not directly establish the required fix; the requested acceptance evidence is: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

A simulated validation error marks the full job as failed and prevents dependent downstream steps from running. That result is evidence for another corrective change: Review the job step success and failure actions and fail the overall job when a required step does not complete successfully. The alternative problem is: An Agent job reports success because its final step runs despite an earlier failed data validation step in the workflow. The current Alpine Healthcare issue is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. Its decisive acceptance evidence would be: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

The Agent step completes the intended file task and an unrelated share remains inaccessible to that execution identity. That result is evidence for another corrective change: Configure a supported job execution credential or proxy with narrowly scoped share permissions and verify the host network access. The alternative problem is: A SQL Server on Azure VM Agent job executes a shell script but fails after migration because the service account cannot access a protected network share. The current Alpine Healthcare issue is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. Its decisive acceptance evidence would be: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator. That result is evidence for another corrective change: Configure Agent job failure alerts and notifications with the required Database Mail and operator settings where supported. The alternative problem is: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. The current Alpine Healthcare issue is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. Its decisive acceptance evidence would be: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

Choose a least-privilege job owner or supported proxy/credential configuration and scope each job step's required permissions. That relates to a separate SQL administration problem: A nightly Agent job uses a high-privilege SQL login for routine index maintenance even though a narrower execution context is possible. The Brookside Manufacturing requirement is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. That approach does not directly establish the required fix; the requested acceptance evidence is: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

Identify SQL Server Agent dependencies and redesign suitable recurring tasks using supported elastic jobs or Azure automation services. That relates to a separate SQL administration problem: A migration from SQL Server to Azure SQL Database assumes every SQL Server Agent job will continue to run inside the single database service. The Brookside Manufacturing requirement is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. That approach does not directly establish the required fix; the requested acceptance evidence is: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

Inspect the SQL Server Agent service, enabled status, schedules, step outputs and job history to isolate the actual failure. That relates to a separate SQL administration problem: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. The Brookside Manufacturing requirement is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. That approach does not directly establish the required fix; the requested acceptance evidence is: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

The incident identifies the missing execution trigger and the next approved run generates an expected logged completion. That result is evidence for another corrective change: Inspect the SQL Server Agent service, enabled status, schedules, step outputs and job history to isolate the actual failure. The alternative problem is: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. The current Brookside Manufacturing issue is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. Its decisive acceptance evidence would be: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

A simulated validation error marks the full job as failed and prevents dependent downstream steps from running. That result is evidence for another corrective change: Review the job step success and failure actions and fail the overall job when a required step does not complete successfully. The alternative problem is: An Agent job reports success because its final step runs despite an earlier failed data validation step in the workflow. The current Brookside Manufacturing issue is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. Its decisive acceptance evidence would be: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

An audit compares the deployed schedule to its reviewed script and an approved rollback restores the prior execution window. That result is evidence for another corrective change: Manage Agent job and schedule changes through controlled scripts and versioned configuration with documented approval. The alternative problem is: A team changes SQL Server Agent schedules through ad hoc T-SQL commands but never records who approved the change or its rollback. The current Brookside Manufacturing issue is instead: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. Its decisive acceptance evidence would be: The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods.

Manage Agent job and schedule changes through controlled scripts and versioned configuration with documented approval. That relates to a separate SQL administration problem: A team changes SQL Server Agent schedules through ad hoc T-SQL commands but never records who approved the change or its rollback. The Brookside Manufacturing requirement is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

Identify SQL Server Agent dependencies and redesign suitable recurring tasks using supported elastic jobs or Azure automation services. That relates to a separate SQL administration problem: A migration from SQL Server to Azure SQL Database assumes every SQL Server Agent job will continue to run inside the single database service. The Brookside Manufacturing requirement is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

Configure the SQL Server Agent schedule and maintenance window explicitly for the target environment and verify service-local time behavior. That relates to a separate SQL administration problem: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. The Brookside Manufacturing requirement is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

The overnight run produces one verified import result and no duplicate execution or repeated rows appear in the job history. That result is evidence for another corrective change: Consolidate schedule definitions and implement idempotent task behavior or mutual exclusion for the recurring import. The alternative problem is: An Agent job has multiple overlapping schedules and duplicate nightly imports, causing a unique key violation every morning. The current Brookside Manufacturing issue is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. Its decisive acceptance evidence would be: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

A simulated validation error marks the full job as failed and prevents dependent downstream steps from running. That result is evidence for another corrective change: Review the job step success and failure actions and fail the overall job when a required step does not complete successfully. The alternative problem is: An Agent job reports success because its final step runs despite an earlier failed data validation step in the workflow. The current Brookside Manufacturing issue is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. Its decisive acceptance evidence would be: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods. That result is evidence for another corrective change: Configure the SQL Server Agent schedule and maintenance window explicitly for the target environment and verify service-local time behavior. The alternative problem is: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. The current Brookside Manufacturing issue is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. Its decisive acceptance evidence would be: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

Configure a supported job execution credential or proxy with narrowly scoped share permissions and verify the host network access. That relates to a separate SQL administration problem: A SQL Server on Azure VM Agent job executes a shell script but fails after migration because the service account cannot access a protected network share. The Northgate Telecom requirement is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

Configure the SQL Server Agent schedule and maintenance window explicitly for the target environment and verify service-local time behavior. That relates to a separate SQL administration problem: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. The Northgate Telecom requirement is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

Identify SQL Server Agent dependencies and redesign suitable recurring tasks using supported elastic jobs or Azure automation services. That relates to a separate SQL administration problem: A migration from SQL Server to Azure SQL Database assumes every SQL Server Agent job will continue to run inside the single database service. The Northgate Telecom requirement is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

A simulated validation error marks the full job as failed and prevents dependent downstream steps from running. That result is evidence for another corrective change: Review the job step success and failure actions and fail the overall job when a required step does not complete successfully. The alternative problem is: An Agent job reports success because its final step runs despite an earlier failed data validation step in the workflow. The current Northgate Telecom issue is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. Its decisive acceptance evidence would be: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

The Agent execution history shows the task runs within the approved maintenance window without overlapping peak workload periods. That result is evidence for another corrective change: Configure the SQL Server Agent schedule and maintenance window explicitly for the target environment and verify service-local time behavior. The alternative problem is: A SQL Managed Instance maintenance job has been created but runs during peak sales traffic because its SQL Server Agent schedule was copied from a different time zone. The current Northgate Telecom issue is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. Its decisive acceptance evidence would be: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.

The overnight run produces one verified import result and no duplicate execution or repeated rows appear in the job history. That result is evidence for another corrective change: Consolidate schedule definitions and implement idempotent task behavior or mutual exclusion for the recurring import. The alternative problem is: An Agent job has multiple overlapping schedules and duplicate nightly imports, causing a unique key violation every morning. The current Northgate Telecom issue is instead: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. Its decisive acceptance evidence would be: A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator.