quiz bu lëkkale ak tegtal · Diggante Niveau

Ni ñuy bindee ay CTE SQL ak ay laajte yu ndaw ak AI Quiz

Saytu CTE yaatuwaayu, EXISTS ak subqueries scalar, ak kaaraange laajte recursif jaaraleko ci rapoor kiliyaan yi ak misaali hierarchie yu ndaw.

Yooni njiit yu jëm ciSql Ctes ak ay sous-laaj ak IA
Laaj 1 de 8

TANN CTE bu tuddu kiliyaan_totals ñu ngi ko màndargaale ak AK. Ba ñaata fan la resultaa boobu ñuy woowe ordinaire di am?

Xoolaatal laaj bu nekk8 laaj

Sooy def quiz bi, tontu yi ak leeral yi dañuy feeñ.

  1. TANN CTE bu tuddu kiliyaan_totals ñu ngi ko màndargaale ak AK. Ba ñaata fan la resultaa boobu ñuy woowe ordinaire di am?
    • Until the database server next restarts
    • Within the larger statement that defines it
    • Until a separate DROP TABLE command removes it
    • Across every future query in the same application
  2. Kiliyaan bi amna ñatti komànd yu mu mëna am. naka la ko EXISTS mëna amee ci rang bi gëna biti ci kiliyaan bi?
    • It automatically creates three output copies
    • It adds three to every customer total
    • It fails because more than one inner row exists
    • It tests true without multiplying the row because of those matches
  3. Ab laajte bu ndaw bu PostgreSQL scalar dafay delloo ñaari liiñ ci anam wuñu ko xaarul. Ban tontu mooy tëye sàrtu tànneef bu am solo?
    • Clarify and implement which single value the query should return
    • Add an unordered LIMIT merely to suppress the error
    • Assume PostgreSQL will always choose the latest row
    • Change the output alias and leave the subquery unchanged
  4. Lan moo tax ñu wara saytu CTE_totals customer balaa ñu koy boole ci leerali kiliyaan bi?
    • The CTE name establishes that each customer key is unique
    • An aggregate inside a CTE cannot produce repeated customer keys
    • Unexpected repeated customer keys can multiply the later result
    • Checking only the final row count establishes each intermediate result's grain
  5. Benn IA dafa wax ni wecci bepp subquery ak benn CTE dafay gëna baaxal performance bi saa yu nekk. naka lañu wara jàngatee lii?
    • Accept it because named steps always execute once
    • Check the target engine's behavior and execution plan
    • Accept it because a shorter query always requires less work
    • Reject every CTE because it must always be materialized
  6. Why might UNION fail to stop a recursive cycle when a depth column changes at each visit?
    • UNION preserves every exact duplicate by definition
    • Depth columns prevent any recursive query from running
    • Cycles can occur only in queries using UNION ALL
    • Repeated visits can remain distinct result rows because their depths differ
  7. A correlated subquery refers to an outer value. Which performance claim would be premature without plan evidence?
    • It must physically rerun a full independent query for every outer row
    • Its result logically depends on an outer value
    • An optimizer may transform an eligible expression
    • Its behavior should be tested on representative data
  8. Why should null-containing fixtures be used when rewriting a NOT IN condition?
    • Nulls always behave like ordinary equal values
    • NOT IN ignores every null in its comparison set
    • Nulls can change the condition's truth result and the rewrite's behavior
    • Adding a CTE automatically removes null-related differences