Question 50
An Azure SQL operations team investigates: A developer asks whether SQL database in Fabric is designed for application transactions rather than only batch lakehouse storage. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A developer asks whether SQL database in Fabric is designed for application transactions rather than only batch lakehouse storage.) is: A controlled application writes transactions and approved Fabric analytics views obtain the intended replicated data. It directly tests whether the remediation (Evaluate SQL database in Microsoft Fabric for integrated operational SQL workloads whose data should also be available through Fabric and OneLake analytics.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A developer asks whether SQL database in Fabric is designed for application transactions rather than only batch lakehouse storage. The specific supported administrative response is: Evaluate SQL database in Microsoft Fabric for integrated operational SQL workloads whose data should also be available through Fabric and OneLake analytics. The technical risk is: Assuming Fabric SQL database is simply a SQL Server VM can lead to wrong instance-management and integration expectations. Confirm the correction with: A controlled application writes transactions and approved Fabric analytics views obtain the intended replicated data.
Incorrect Answers
SQL server on azure virtual machines (1.1) addresses another technical failure: Moving an OS-dependent SQL workload to PaaS may remove administrative capabilities it requires. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A controlled application writes transactions and approved Fabric analytics views obtain the intended replicated data.
Table partitioning for large tables (1.2) addresses another technical failure: Partitioning without a matching access pattern or maintenance plan can complicate administration without improving queries. This choice can be useful for that problem, but it does not establish the SQL database in microsoft fabric (1.1) control being assessed here.
Columnstore and row compression decisions (1.2) would demonstrate or implement: Before-and-after size, CPU and representative query tests establish the net benefit of the selected compression. The paired-answer requirement concerns SQL database in microsoft fabric (1.1); this alternative does not provide the matching intervention and separate acceptance evidence.