Exam Bundle

A concurrency test constrains reporting resource consumption while the protected transactional group's latency stays within target. That result is evidence for another corrective change: Configure Resource Governor workload groups and classification appropriate to the instance edition and workload objectives. The alternative problem is: A shared SQL Server instance runs several resource-intensive reporting workloads with no protection for a latency-critical transactional group. The current Brookside Manufacturing issue is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. Its decisive acceptance evidence would be: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

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 large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. Its decisive acceptance evidence would be: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

The chosen index receives maintenance only when justified and application response times remain stable during the scheduled window. That result is evidence for another corrective change: Use measured fragmentation, page count, workload effects and supported maintenance guidance to choose a targeted index maintenance policy. The alternative problem is: A fragmented heavily updated index is rebuilt every hour regardless of its size or actual query benefit, causing unnecessary log and CPU activity. The current Brookside Manufacturing issue is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. Its decisive acceptance evidence would be: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

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 Granite SaaS requirement is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. That approach does not directly establish the required fix; the requested acceptance evidence is: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

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 Granite SaaS requirement is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. That approach does not directly establish the required fix; the requested acceptance evidence is: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

Schedule supported database integrity validation and define remediation and restore responses for corruption findings. That relates to a separate SQL administration problem: A production SQL Server has never run DBCC CHECKDB and a backup success email is treated as proof of database structural integrity. The Granite SaaS requirement is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. That approach does not directly establish the required fix; the requested acceptance evidence is: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

Estimated row counts more closely match actual results and the affected query plan improves after statistics maintenance. That result is evidence for another corrective change: Update relevant statistics using suitable sampling and schedule triggers based on data-change patterns and affected queries. The alternative problem is: A query optimizer chooses poor cardinality estimates because frequently modified key columns retain outdated statistics and no maintenance policy exists. The current Granite SaaS issue is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. Its decisive acceptance evidence would be: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression. That result is evidence for another corrective change: Evaluate supported intelligent query processing features such as memory grant feedback under a tested compatibility level. The alternative problem is: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. The current Granite SaaS issue is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. Its decisive acceptance evidence would be: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

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 Granite SaaS issue is instead: A large database is manually kept on expensive peak compute despite a predictable nightly analytics load and low daytime activity. Its decisive acceptance evidence would be: Planned scaling meets the overnight workload goal while daytime allocations and costs follow the documented capacity plan.

Plan selective index maintenance and log sizing with observed change volume and appropriate transaction log I/O capacity. That relates to a separate SQL administration problem: A database job performs frequent full-index rebuilds but the associated transaction log grows faster than its configured throughput can handle. The Granite SaaS requirement is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. That approach does not directly establish the required fix; the requested acceptance evidence is: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

Set proactive capacity alerts and governed scaling triggers based on CPU, I/O, storage and available tier capabilities. That relates to a separate SQL administration problem: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. The Granite SaaS requirement is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. That approach does not directly establish the required fix; the requested acceptance evidence is: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

Update relevant statistics using suitable sampling and schedule triggers based on data-change patterns and affected queries. That relates to a separate SQL administration problem: A query optimizer chooses poor cardinality estimates because frequently modified key columns retain outdated statistics and no maintenance policy exists. The Granite SaaS requirement is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. That approach does not directly establish the required fix; the requested acceptance evidence is: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

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 Granite SaaS issue is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. Its decisive acceptance evidence would be: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

A controlled demand increase triggers an alert before service limits are breached and the approved scaling action is auditable. That result is evidence for another corrective change: Set proactive capacity alerts and governed scaling triggers based on CPU, I/O, storage and available tier capabilities. The alternative problem is: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. The current Granite SaaS issue is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. Its decisive acceptance evidence would be: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

Estimated row counts more closely match actual results and the affected query plan improves after statistics maintenance. That result is evidence for another corrective change: Update relevant statistics using suitable sampling and schedule triggers based on data-change patterns and affected queries. The alternative problem is: A query optimizer chooses poor cardinality estimates because frequently modified key columns retain outdated statistics and no maintenance policy exists. The current Granite SaaS issue is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. Its decisive acceptance evidence would be: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

Plan selective index maintenance and log sizing with observed change volume and appropriate transaction log I/O capacity. That relates to a separate SQL administration problem: A database job performs frequent full-index rebuilds but the associated transaction log grows faster than its configured throughput can handle. The Northgate Telecom requirement is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. That approach does not directly establish the required fix; the requested acceptance evidence is: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

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 Northgate Telecom requirement is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. That approach does not directly establish the required fix; the requested acceptance evidence is: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

Reserve adequate operating-system and auxiliary-service memory and configure supported max server memory for the SQL instance. That relates to a separate SQL administration problem: An SQL Server VM uses default max server memory so database memory pressure causes the Windows host to page heavily under load. The Northgate Telecom requirement is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. That approach does not directly establish the required fix; the requested acceptance evidence is: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

The automatic recommendation reports implemented status and representative query performance improves without unacceptable write regression. That result is evidence for another corrective change: Evaluate and configure supported automatic tuning settings and monitor each action for workload benefit or rollback. The alternative problem is: An Azure SQL Database with supported automatic tuning is left unmanaged despite repeated regressions and validated index recommendations. The current Northgate Telecom issue is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. Its decisive acceptance evidence would be: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

The chosen index receives maintenance only when justified and application response times remain stable during the scheduled window. That result is evidence for another corrective change: Use measured fragmentation, page count, workload effects and supported maintenance guidance to choose a targeted index maintenance policy. The alternative problem is: A fragmented heavily updated index is rebuilt every hour regardless of its size or actual query benefit, causing unnecessary log and CPU activity. The current Northgate Telecom issue is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. Its decisive acceptance evidence would be: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

A concurrency test constrains reporting resource consumption while the protected transactional group's latency stays within target. That result is evidence for another corrective change: Configure Resource Governor workload groups and classification appropriate to the instance edition and workload objectives. The alternative problem is: A shared SQL Server instance runs several resource-intensive reporting workloads with no protection for a latency-critical transactional group. The current Northgate Telecom issue is instead: A query uses repeated scalar UDF calls and creates excessive row-by-row execution overhead even though intelligent query processing may help. Its decisive acceptance evidence would be: The test plan shows the supported inlining or refactor effect and CPU time falls without changing query results.

Evaluate supported database-scoped configuration or query-level hints rather than unnecessary global engine setting changes. That relates to a separate SQL administration problem: A database owner changes instance-wide optimizer settings to solve one compatibility-sensitive database problem that could be scoped locally. The Northgate Telecom requirement is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

Plan selective index maintenance and log sizing with observed change volume and appropriate transaction log I/O capacity. That relates to a separate SQL administration problem: A database job performs frequent full-index rebuilds but the associated transaction log grows faster than its configured throughput can handle. The Northgate Telecom requirement is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

Set proactive capacity alerts and governed scaling triggers based on CPU, I/O, storage and available tier capabilities. That relates to a separate SQL administration problem: A team configures database auto-scaling only after a critical application has begun failing because it did not set any workload thresholds. The Northgate Telecom requirement is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

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 Northgate Telecom issue is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. Its decisive acceptance evidence would be: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

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 Northgate Telecom issue is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. Its decisive acceptance evidence would be: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

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 Northgate Telecom issue is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. Its decisive acceptance evidence would be: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

Schedule supported database integrity validation and define remediation and restore responses for corruption findings. That relates to a separate SQL administration problem: A production SQL Server has never run DBCC CHECKDB and a backup success email is treated as proof of database structural integrity. The Lakeside Research requirement is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

Benchmark index effects against representative reads and writes and adopt only a change with acceptable total workload impact. That relates to a separate SQL administration problem: 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 Lakeside Research requirement is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

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 Lakeside Research requirement is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

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 Lakeside Research issue is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. Its decisive acceptance evidence would be: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

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 Lakeside Research issue is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. Its decisive acceptance evidence would be: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.

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 Lakeside Research issue is instead: A report repeatedly underestimates intermediate row counts and spills to tempdb because the database uses an older compatibility level unnecessarily. Its decisive acceptance evidence would be: A controlled repeated query workload shows fewer memory spills with correct results and no unacceptable regression.