정답:

Explanation:
* Sales # A clustered columnstore index
* Products # A clustered rowstore index
For Sales , the correct choice is a clustered columnstore index . Microsoft identifies clustered columnstore indexes as the standard storage choice for large fact tables and analytical/data-warehouse workloads . The Sales table is 10 TB, loaded in nightly batches, and its reporting queries scan large portions of the table and perform aggregations such as SUM(TotalSale) . Those are exactly the workload characteristics that benefit from columnstore storage, batch-mode execution, aggregate pushdown, and high compression. Microsoft also notes that clustered columnstore indexes can provide substantial storage reduction compared with traditional uncompressed rowstore structures, which directly supports the requirement to minimize storage requirements .
For Products , the correct choice is a clustered rowstore index . Microsoft states that rowstore B-tree indexes perform best for point lookups, equality searches, and small-range retrieval , whereas columnstore is optimized for large analytical scans. Since Products is relatively small and primarily supports point lookups and joins to Sales , a rowstore structure is the better fit.
A nonclustered columnstore index would retain the underlying rowstore and add another compressed copy of selected columns, increasing storage. That is more appropriate for real-time analytics over an OLTP table, not for this dedicated large analytical fact table.

정답:

Explanation:

The first statement is No . GETDATE() is a nondeterministic built-in function, and SQL Server UDF guidance does not support using nondeterministic built-ins inside a T-SQL user-defined function for this purpose. Microsoft explicitly classifies GETDATE() as nondeterministic.
The second statement is Yes . Multi-statement TVFs are a common source of weak cardinality estimates and unstable plans because the optimizer has less information about their result sizes. Microsoft documents features such as interleaved execution for multi-statement TVFs , which exist specifically because MSTVFs have optimization challenges, and Microsoft also notes that scalar/UDF style constructs can lead to poorer optimization behavior than relationally inlined alternatives. Rewriting an MSTVF as an inline TVF generally gives the optimizer better visibility and more consistent plans.
The third statement is Yes . Scalar functions must be invoked using at least the two-part name < schema > .
< function > . Microsoft's documentation is explicit on that point for executing user-defined functions. So changing ufn_GetTaxMultiplier to dbo.ufn_GetTaxMultiplier resolves the naming error in the EXEC statement.

정답: D  🗳️

설명: (Fast2test 회원만 볼 수 있음)

정답:

Explanation:

For authentication , the correct choice is Enable a managed identity and use Microsoft Entra authentication . Azure App Service supports managed identity, and Microsoft documents this as the recommended way to connect to Azure SQL Database without passwords or secrets . This minimizes administrative effort because there are no SQL passwords to rotate, store, or manage.
For network access , the correct choice is Create a private endpoint and disable public network access .
Microsoft documents that when public network access is disabled , Azure SQL Database only accepts connections through private endpoints . That keeps the database traffic on Azure private networking rather than exposing it through the public endpoint. Microsoft also notes that simply adding a private endpoint does not disable public access by itself, so disabling public network access is part of the correct configuration.
The other options are weaker:
* Rotated SQL credentials or storing SQL logins in Key Vault still use passwords and create more admin overhead.
* Allowing Azure services, adding outbound IP firewall rules, or database firewall rules still rely on the public endpoint , so they do not best satisfy the requirement that database traffic remain within the subscription.