A team needs a governed REST API over selected database entities without writing a complete custom service
Which SQL design or implementation decision most directly addresses this requirement?
DAB reads configuration to expose chosen database objects as endpoints, subject to role and permission controls.
DAB entity mapping and permissions limit accessible objects and operations, complementing SQL grants.
Log Analytics supports queryable cross-resource telemetry and Azure Monitor alerting.
Distributed trace correlation helps associate API failures, dependency latency and service operations.
An invoice table stores totals with binary float and cents sometimes differ after aggregation
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Approximate binary floating-point types cannot represent every decimal currency value exactly; fixed-precision decimal arithmetic avoids that category of rounding error.
Nullability is a core schema invariant and should not be delegated solely to an API form.
Partition elimination can narrow scans and partition switching can simplify retention when indexes align.
A 64-bit integer provides a much larger identifier range; relationships and clients must accept the chosen type.
A search screen needs a parameterized reusable result set from one SELECT statement
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Inline TVFs return tabular results and can be optimized into the calling query, unlike a procedure result set.
T-SQL user-defined functions have side-effect and statement restrictions that differ from stored procedures.
An explicit transaction and consistent failure policy enforce atomicity across multiple statements.
Multistatement TVFs can introduce estimation and optimization limitations, so an inline form is preferred when expressive enough.
An analyst estimates that an index seek is used but actual rows suggest most time is spent joining
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Actual plans reveal runtime statistics and costly operators that estimated plans alone may not expose.
Query Store retains plan and runtime history so regressions can be tied to specific plan choices.
DMVs expose current and cumulative SQL diagnostics that help distinguish contention from capacity or query-plan issues.
CPU, concurrency and IO constraints drive sizing decisions; indiscriminate upgrades may not solve a poor plan.
A high-concurrency database needs statement-level consistent reads without widespread shared read locks
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Versioned read-committed isolation reduces reader/writer blocking but changes consistency semantics and tempdb/version-store demand.
Latency symptoms may come from blocking, execution plans, throttling or network; one symptom cannot establish root cause.
Statistics provide distribution estimates that influence cardinality and join strategy choices.
Long transactions hold locks and version state, worsening throughput and blocking.
A support worker may inspect a masked phone number but not the full stored value
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Dynamic Data Masking changes query presentation for covered low-privilege principals but is not cryptographic encryption.
Network restrictions limit reachability while scoped credentials decide who can invoke supported operations.
TDE encrypts database files and backups at rest but does not prevent authorized SQL queries from reading plaintext.
TLS protects data in transit and endpoint verification reduces man-in-the-middle risk.
An appointment system must distinguish local wall time from actual instant across daylight-saving changes
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Persisting an offset or normalized instant helps prevent ambiguity that occurs with unqualified local DATETIME values.
Avoiding functions on the indexed search column can let the optimizer use an index seek.
Columnstore compression and batch execution are effective on broad aggregations; they are not universally best for singleton OLTP updates.
Checking JSON validity before promotion reduces malformed documents but does not replace application-level schema validation.
Mobile clients submit optional semi-structured settings while core account fields remain relational
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
JSON storage supports evolving attributes, but constraints and relational columns should still enforce critical business invariants.
Columnstore compression and batch execution are effective on broad aggregations; they are not universally best for singleton OLTP updates.
A 64-bit integer provides a much larger identifier range; relationships and clients must accept the chosen type.
In-Memory OLTP reduces certain latch and lock bottlenecks but has feature and capacity constraints that require workload testing.
A search function fails because input vectors use different model versions
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Distance calculation requires aligned dimensions and semantics, and metric choice affects ordering.
ANN reduces work compared with exhaustive distance scanning but may miss some exact nearest vectors.
Fast response alone is not sufficient; index parameters shift the speed-quality tradeoff.
Index freshness includes removal as well as addition and edits; stale documents can yield harmful answers.
A data-access function has several staged relational transformations and needs a table return
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Multistatement TVFs can introduce estimation and optimization limitations, so an inline form is preferred when expressive enough.
Scalar functions return one value and can encapsulate reusable calculation logic, but implementation choice may affect plan quality.
Inline TVFs return tabular results and can be optimized into the calling query, unlike a procedure result set.
DML triggers run per statement and inserted/deleted can contain multiple rows; singleton assumptions cause data loss.
A telemetry system can exceed the positive range of a 32-bit integer over its retention period
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
A 64-bit integer provides a much larger identifier range; relationships and clients must accept the chosen type.
Sequences generate values independently of an individual table, unlike a column-specific identity, and can still exhibit gaps.
Checking JSON validity before promotion reduces malformed documents but does not replace application-level schema validation.
In-Memory OLTP reduces certain latch and lock bottlenecks but has feature and capacity constraints that require workload testing.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
