Gids-gekoppelde quiz · Middelmatig Niveau

SQL-query's schrijven met AI Quiz

Test hoe goed u een AI uw schema kunt geven, join-fan-out en NULL-traps kunt opvangen en door AI gegenereerde SQL veilig kunt verifiëren voordat u de resultaten vertrouwt.

Vraag 1 van 8

Welke stap verbetert volgens de gids de nauwkeurigheid van door AI gegenereerde SQL het meest?

Bekijk elke vraag8 vragen

Antwoorden en uitleg verschijnen terwijl je de quiz doet.

  1. Welke stap verbetert volgens de gids de nauwkeurigheid van door AI gegenereerde SQL het meest?
    • Asking the model to be extra careful
    • Pasting your schema, such as CREATE TABLE statements and relationships
    • Writing your question entirely in uppercase
    • Always using the newest model available
  2. Waarom zou u de AI vertellen welk SQL-dialect u gebruikt?
    • Only PostgreSQL supports SELECT statements
    • AI models refuse to answer without a dialect
    • The dialect determines how much disk space a query uses
    • Dialects differ in details like date functions and LIMIT versus TOP
  3. U voegt bestellingen samen met order_items en berekent vervolgens SUM(orders.total). Wat is het waarschijnlijke probleem?
    • Revenue is inflated because each order total repeats once per item
    • The query will always fail with a syntax error
    • NULL values are converted to zero
    • The results come back sorted in the wrong order
  4. Waarom raadt de gids aan om de AI te vragen zijn vraag in gewone woorden uit te leggen?
    • It makes the query run faster
    • SQL engines require an explanation before executing
    • It exposes misunderstandings, such as counting rows instead of distinct customers
    • It reduces the cost of the AI request
  5. Welke uitspraak over COUNT(kolom) en COUNT(*) is juist?
    • They always return the same number
    • COUNT(column) skips NULLs, while COUNT(*) counts every row
    • COUNT(*) skips NULLs, while COUNT(column) counts every row
    • COUNT(column) counts only distinct values
  6. What is the safest way to experiment with AI-generated queries?
    • Run them directly on production during quiet hours
    • Ask the AI whether the query is safe and trust the answer
    • Use a read-only database user and wrap data changes in a transaction you can roll back
    • Remove the WHERE clause so the query is simpler
  7. When asking an AI to optimize a slow query, what should you provide besides the query?
    • A screenshot of the dashboard that uses it
    • The database password
    • A list of everyone who runs the report
    • The execution plan from EXPLAIN or EXPLAIN ANALYZE
  8. Which of these is a misconception the guide warns against?
    • A query that runs without errors must be returning the right answer
    • The schema alone is often enough context, without real customer data
    • An UPDATE without a WHERE clause affects every row
    • Business rules like amounts stored in cents should be stated