A DAB GraphQL consumer needs to constrain query results to authorized fields and predicates
Which SQL design or implementation decision most directly addresses this requirement?
API filtering reduces unnecessary result transfer but cannot replace server-side authorization.
CES can publish database changes into an event architecture, but supported platform and ordering guarantees must be checked.
CDC records changes from the transaction log for downstream consumption, but latency and retention need management.
GraphQL relationships make defined SQL relations traversable through the API without arbitrary client SQL.
A large historical transaction store supports mostly batch reporting rather than single-row updates
Which SQL design or implementation decision most directly addresses this requirement?
Columnstore compression and batch execution are effective on broad aggregations; they are not universally best for singleton OLTP updates.
Covering indexes can avoid residual lookups while keeping included attributes out of the search-key ordering.
Avoiding functions on the indexed search column can let the optimizer use an index seek.
Partition switching has schema and index-alignment prerequisites; an incompatible index can block the metadata operation.
A frontend wants to traverse an approved parent-child relationship using a typed GraphQL field
Which SQL design or implementation decision most directly addresses this requirement?
GraphQL relationships make defined SQL relations traversable through the API without arbitrary client SQL.
Distributed trace correlation helps associate API failures, dependency latency and service operations.
Caching reduces repeat database load but introduces staleness and must avoid exposing user-specific sensitive results.
Configuration separation allows consistent entities while credentials and endpoints differ securely across environments.
An application needs a stable SELECT interface without exposing underlying table complexity
Which SQL design or implementation decision most directly addresses this requirement?
Views centralize a logical query definition without storing an independent copy of rows by default.
Schema binding prevents incompatible changes to referenced object definitions until the dependency is handled.
Stored procedure execution can reduce direct table grants but still needs review of ownership, dynamic SQL, and execution context.
Views can serve as a restricted interface but must be combined with appropriate permissions and row filtering.
A report needs a transaction-wide stable snapshot despite concurrent writes
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
Snapshot transactions read a consistent row version as of transaction start without dirty reads, but writes may conflict.
Latency symptoms may come from blocking, execution plans, throttling or network; one symptom cannot establish root cause.
A cached plan based on one parameter distribution may be unsuitable for another; forced plans or hints need evidence.
DMVs expose current and cumulative SQL diagnostics that help distinguish contention from capacity or query-plan issues.
A document retrieval index has confidential columns that ordinary search users must not access
Which SQL design or implementation decision most directly addresses this requirement?
Index membership can make data discoverable; search permission cannot be inferred from index design.
Lexical retrieval is suited to exact symbols and keywords, while semantic vectors may miss exact identifiers.
Vector similarity can match related meaning beyond exact token overlap if embedding quality is adequate.
Near-duplicate chunks can crowd top-K slots and lower answer coverage even with accurate vector ranking.
Customer names include accents and scripts from several countries in a shared table
Which SQL design or implementation decision most directly addresses this requirement?
Unicode-capable character types retain characters outside a single legacy code page and require appropriate length planning.
Database check predicates reject invalid stored values regardless of which client sent the write.
In-Memory OLTP reduces certain latch and lock bottlenecks but has feature and capacity constraints that require workload testing.
Identity allocation can leave gaps after failures or caching, so it is inappropriate as a legal no-gap counter.
An API frequently filters a JSON payload by a customer tier nested inside a document
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
An indexed computed expression can make frequently queried JSON properties searchable instead of repeatedly parsing and scanning.
The selected range direction determines ownership of values equal to boundaries, which affects pruning and rollover.
Graph tables represent relationships explicitly and support pattern matching, though ordinary relational joins remain valid for simple cases.
System-versioned temporal tables maintain historical row versions so FOR SYSTEM_TIME queries can reconstruct earlier states.
An ETL bulk insert creates one audit record when it should record every inserted row
After the team applies the intended design, which observation would most directly verify that the specific requirement was met?
DML triggers run per statement and inserted/deleted can contain multiple rows; singleton assumptions cause data loss.
Views can serve as a restricted interface but must be combined with appropriate permissions and row filtering.
Scalar functions return one value and can encapsulate reusable calculation logic, but implementation choice may affect plan quality.
NOCOUNT suppresses DONEINPROC row-count chatter without changing @@ROWCOUNT semantics.
An application publishes Data API Builder GraphQL endpoints to external users with no permission check
Which SQL design or implementation decision most directly addresses this requirement?
Endpoint convenience does not replace user authentication and data access enforcement in API and SQL layers.
Separating audit custody from operational administrators reduces the risk of tampering and premature deletion.
Column-master and column-encryption key lifecycle must be managed carefully to prevent decryption outages.
Nonproduction environments should not inherit production exposure merely for test convenience.
A report needs all tags for each product returned as a JSON array
Which SQL design or implementation decision most directly addresses this requirement?
JSON_ARRAYAGG aggregates scalar or JSON values into an array, reducing custom string assembly.
REGEXP_LIKE evaluates a regex match, including anchors that constrain the whole input rather than just a substring.
RANK assigns tied rows the same rank and leaves gaps; DENSE_RANK does not leave gaps.
Jaro-Winkler style similarity rewards matching character patterns and helps with transpositions but cannot prove identity.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
