Exam Bundle

A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss. That result is evidence for another corrective change: Evaluate explicit sharding with a stable tenant-to-shard routing strategy and independent databases instead of relying on intra-database partitions. The alternative problem is: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. The current Lakeside Research issue is instead: A database team assumes Azure Arc-enabled SQL Server creates an Azure SQL Database and automatically migrates all on-premises data. Its decisive acceptance evidence would be: The original instance remains in place, its governance metadata is visible through Azure Arc, and no unplanned data migration occurs.

A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable. That result is evidence for another corrective change: Design range-based table partitioning using a suitable partition function and scheme aligned with retention and query-access requirements. The alternative problem is: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. The current Lakeside Research issue is instead: A database team assumes Azure Arc-enabled SQL Server creates an Azure SQL Database and automatically migrates all on-premises data. Its decisive acceptance evidence would be: The original instance remains in place, its governance metadata is visible through Azure Arc, and no unplanned data migration occurs.

A test ERP workload runs with the required Windows and SQL Server instance features and its VM administration responsibilities are documented. That result is evidence for another corrective change: Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. The alternative problem is: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The current Lakeside Research issue is instead: A database team assumes Azure Arc-enabled SQL Server creates an Azure SQL Database and automatically migrates all on-premises data. Its decisive acceptance evidence would be: The original instance remains in place, its governance metadata is visible through Azure Arc, and no unplanned data migration occurs.

Evaluate explicit sharding with a stable tenant-to-shard routing strategy and independent databases instead of relying on intra-database partitions. That relates to a separate SQL administration problem: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. The Lakeside Research requirement is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. That approach does not directly establish the required fix; the requested acceptance evidence is: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. That relates to a separate SQL administration problem: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The Lakeside Research requirement is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. That approach does not directly establish the required fix; the requested acceptance evidence is: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

Compare Azure SQL Database, Managed Instance and SQL Server on Azure VMs against operational responsibility, feature parity, networking and performance needs. That relates to a separate SQL administration problem: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. The Lakeside Research requirement is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. That approach does not directly establish the required fix; the requested acceptance evidence is: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

The original instance remains in place, its governance metadata is visible through Azure Arc, and no unplanned data migration occurs. That result is evidence for another corrective change: Use Azure Arc-enabled SQL Server to inventory and manage eligible existing SQL Server instances while designing migration as a separate process. The alternative problem is: A database team assumes Azure Arc-enabled SQL Server creates an Azure SQL Database and automatically migrates all on-premises data. The current Lakeside Research issue is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. Its decisive acceptance evidence would be: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss. That result is evidence for another corrective change: Evaluate explicit sharding with a stable tenant-to-shard routing strategy and independent databases instead of relying on intra-database partitions. The alternative problem is: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. The current Lakeside Research issue is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. Its decisive acceptance evidence would be: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency. That result is evidence for another corrective change: Compare Azure SQL Database, Managed Instance and SQL Server on Azure VMs against operational responsibility, feature parity, networking and performance needs. The alternative problem is: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. The current Lakeside Research issue is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. Its decisive acceptance evidence would be: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

Compare Azure SQL Database, Managed Instance and SQL Server on Azure VMs against operational responsibility, feature parity, networking and performance needs. That relates to a separate SQL administration problem: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. The Silvercrest University requirement is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. That approach does not directly establish the required fix; the requested acceptance evidence is: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. That relates to a separate SQL administration problem: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The Silvercrest University requirement is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. That approach does not directly establish the required fix; the requested acceptance evidence is: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

Plan supported guest operating-system and SQL Server cumulative update maintenance with backups, rollback and a tested outage window. That relates to a separate SQL administration problem: An infrastructure team restores a SQL Server VM image but fails to patch SQL Server, assuming Azure host maintenance upgrades the guest software. The Silvercrest University requirement is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. That approach does not directly establish the required fix; the requested acceptance evidence is: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

A test ERP workload runs with the required Windows and SQL Server instance features and its VM administration responsibilities are documented. That result is evidence for another corrective change: Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. The alternative problem is: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The current Silvercrest University issue is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. Its decisive acceptance evidence would be: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable. That result is evidence for another corrective change: Design range-based table partitioning using a suitable partition function and scheme aligned with retention and query-access requirements. The alternative problem is: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. The current Silvercrest University issue is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. Its decisive acceptance evidence would be: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

The migrated test workload executes its scheduled Agent job on the managed instance and the dependency inventory has no unsupported features. That result is evidence for another corrective change: Select Azure SQL Managed Instance when instance compatibility and SQL Server Agent are required, after checking the feature and networking constraints. The alternative problem is: A startup deploys a small Azure SQL Database but requires instance-level SQL Server Agent jobs, which the chosen single database cannot host. The current Silvercrest University issue is instead: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. Its decisive acceptance evidence would be: The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path.

Use a governed deployment pipeline with parameterized templates, separate service identities and recorded change approvals. That relates to a separate SQL administration problem: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. The Silvercrest University requirement is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. That approach does not directly establish the required fix; the requested acceptance evidence is: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Evaluate explicit sharding with a stable tenant-to-shard routing strategy and independent databases instead of relying on intra-database partitions. That relates to a separate SQL administration problem: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. The Silvercrest University requirement is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. That approach does not directly establish the required fix; the requested acceptance evidence is: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. That relates to a separate SQL administration problem: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The Silvercrest University requirement is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. That approach does not directly establish the required fix; the requested acceptance evidence is: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Connectivity, collation-sensitive queries and required drivers pass controlled pre-production checks against the documented inventory. That result is evidence for another corrective change: Create a dependency and compatibility inventory for on-premises and cloud endpoints before deploying the hybrid SQL Server solution. The alternative problem is: A hybrid SQL Server estate is moved to Azure without checking collation, network latency or client drivers required by its linked workloads. The current Silvercrest University issue is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. Its decisive acceptance evidence would be: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path. That result is evidence for another corrective change: Identify the operational database and Microsoft Fabric integration roles separately, checking supported Azure SQL Database in Fabric capabilities for the use case. The alternative problem is: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. The current Silvercrest University issue is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. Its decisive acceptance evidence would be: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

The migrated test workload executes its scheduled Agent job on the managed instance and the dependency inventory has no unsupported features. That result is evidence for another corrective change: Select Azure SQL Managed Instance when instance compatibility and SQL Server Agent are required, after checking the feature and networking constraints. The alternative problem is: A startup deploys a small Azure SQL Database but requires instance-level SQL Server Agent jobs, which the chosen single database cannot host. The current Silvercrest University issue is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. Its decisive acceptance evidence would be: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Plan supported guest operating-system and SQL Server cumulative update maintenance with backups, rollback and a tested outage window. That relates to a separate SQL administration problem: An infrastructure team restores a SQL Server VM image but fails to patch SQL Server, assuming Azure host maintenance upgrades the guest software. The Westhaven Retail requirement is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. That approach does not directly establish the required fix; the requested acceptance evidence is: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. That relates to a separate SQL administration problem: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The Westhaven Retail requirement is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. That approach does not directly establish the required fix; the requested acceptance evidence is: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. That relates to a separate SQL administration problem: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The Westhaven Retail requirement is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. That approach does not directly establish the required fix; the requested acceptance evidence is: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Two clean deployments produce equivalent configuration for the shared policy while only approved environment parameters differ. That result is evidence for another corrective change: Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. The alternative problem is: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The current Westhaven Retail issue is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. Its decisive acceptance evidence would be: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

A test ERP workload runs with the required Windows and SQL Server instance features and its VM administration responsibilities are documented. That result is evidence for another corrective change: Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. The alternative problem is: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The current Westhaven Retail issue is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. Its decisive acceptance evidence would be: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

The restored environment reports the expected guest and engine patch levels and completes application regression and rollback checks. That result is evidence for another corrective change: Plan supported guest operating-system and SQL Server cumulative update maintenance with backups, rollback and a tested outage window. The alternative problem is: An infrastructure team restores a SQL Server VM image but fails to patch SQL Server, assuming Azure host maintenance upgrades the guest software. The current Westhaven Retail issue is instead: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. Its decisive acceptance evidence would be: A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable.

Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. That relates to a separate SQL administration problem: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The Westhaven Retail requirement is instead: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. That approach does not directly establish the required fix; the requested acceptance evidence is: A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss.

Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. That relates to a separate SQL administration problem: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The Westhaven Retail requirement is instead: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. That approach does not directly establish the required fix; the requested acceptance evidence is: A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss.

Select Azure SQL Managed Instance when instance compatibility and SQL Server Agent are required, after checking the feature and networking constraints. That relates to a separate SQL administration problem: A startup deploys a small Azure SQL Database but requires instance-level SQL Server Agent jobs, which the chosen single database cannot host. The Westhaven Retail requirement is instead: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. That approach does not directly establish the required fix; the requested acceptance evidence is: A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss.

Connectivity, collation-sensitive queries and required drivers pass controlled pre-production checks against the documented inventory. That result is evidence for another corrective change: Create a dependency and compatibility inventory for on-premises and cloud endpoints before deploying the hybrid SQL Server solution. The alternative problem is: A hybrid SQL Server estate is moved to Azure without checking collation, network latency or client drivers required by its linked workloads. The current Westhaven Retail issue is instead: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. Its decisive acceptance evidence would be: A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss.

A test ERP workload runs with the required Windows and SQL Server instance features and its VM administration responsibilities are documented. That result is evidence for another corrective change: Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. The alternative problem is: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The current Westhaven Retail issue is instead: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. Its decisive acceptance evidence would be: A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss.

A pilot database serves the application without guest operating-system maintenance and the validated SQL features remain available. That result is evidence for another corrective change: Use Azure SQL Database as the fully managed relational platform after confirming database-level compatibility, scale and feature requirements. The alternative problem is: A transactional web application is placed on a full SQL Server virtual machine even though it requires no operating system or instance administration. The current Westhaven Retail issue is instead: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. Its decisive acceptance evidence would be: A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss.