Llm Prompt Formulation Sql Transformation Quality Rules

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A data engineering team is designing an automated data preparation pipeline in Google Cloud. They are using Vertex AI to prompt a Large Language Model (LLM) to extract structured business entities from semi-structured source specifications, generate BigQuery SQL transformation scripts, and produce Dataform data quality assertion rules.

The automated pipeline requires deterministic, production-grade output. It must eliminate hallucinations, strictly enforce dialect-specific query optimizations (such as rewriting multiple-reference CTEs into temporary tables), output code in an easily parseable format, and ensure no semantic drift or unverified business assumptions are introduced into the transformation logic.

Which prompt engineering strategy should the team implement to formulate the most effective and reliable system prompt for the LLM?

Use zero-shot, open-ended conversational prompts that instruct the LLM to freely infer missing business rules, generate standard ANSI SQL, and summarize potential data anomalies in natural language.

Provide a high-level system prompt focused solely on setting an analytical persona, while delegating query optimization and schema enforcement entirely to client-side Python regex parsing scripts.

Configure the prompt to require chain-of-thought verbose reasoning before the SQL code, while avoiding any explicit negative constraints so the model can optimize creatively.

Structure the prompt with explicit role definition, granular task specifications, strict negative constraints against inferring or interpreting unstated logic, exact output schema requirements, and explicit optimization directives.

Professional Cloud Data Engineer

Llm Prompt Formulation Sql Transformation Quality Rules

Related questions