Pular para o conteúdo

Simulado · Databricks

Simulado Databricks Certified Data Engineer Associate

45
questões
90
minutos
70%
para passar no simulado
60
questões no banco

Resposta curta

O simulado de Databricks Certified Data Engineer Associate tem 45 questões em 90 minutos, com nota de corte de 70%, conforme configurado aqui. O jeito mais rápido de saber se você está pronto é fazer uma prova completa no relógio e ler a nota por domínio, não só o total.

Domínios cobrados

  • ELT with Spark SQL and Python
  • Data Governance
  • Databricks Lakehouse Platform
  • Incremental Data Processing
  • Production Pipelines

Questões de exemplo, com explicação

Três questões do banco, abertas para ler.

Questão 1 · ELT with Spark SQL and Python

An analyst reports that a nightly job intermittently reads a Delta table while a separate write job is mid-flight appending a large batch. On some nights the read returns a mix of old and new rows, and the analyst asks the engineer to add a manual lock to prevent this. Given how Delta Lake works, what should the engineer explain about what a reader actually sees during a concurrent write?

  1. Readers always see whatever Parquet files currently exist on disk, so a half-written batch can leak into results unless a manual lock is added.
  2. Concurrent reads and writes on the same Delta table are unsupported and require enabling a special serializable-read flag per query.
  3. Delta blocks all reads while any write is in progress, so the read job must be waiting and returning stale cached data.
  4. A reader sees a single consistent snapshot pinned to the latest committed table version, so it never observes a partially written batch — no manual lock is needed. ✓ (correta)
Por que esta é a correta

Delta Lake provides ACID snapshot isolation: a query reads the table at a specific committed version recorded in the transaction log, so files from an uncommitted/in-progress write are simply not yet referenced and cannot appear in results — the analyst's 'mix of old and new rows' from a single batch is not actually possible from a half-written commit. The 'readers see whatever files exist on disk' option reflects the classic data-lake misconception; Delta readers resolve files through the log snapshot, not by listing the directory. The 'Delta blocks all reads during writes' option is wrong because writers do not block readers in Delta's optimistic concurrency model. The 'concurrent reads/writes unsupported' option is false — this is a core Delta capability and needs no special per-query flag.

Questão 2 · Production Pipelines

A team must enforce that the 'order_total' column in a DLT silver table is never negative, and any record violating this must be discarded from the table while the violation is still counted in pipeline metrics. Which expectation should they apply?

  1. @dlt.expect with a constraint that order_total >= 0, which keeps the violating rows in the table.
  2. A CHECK constraint added with ALTER TABLE after the pipeline finishes, since DLT cannot drop rows.
  3. @dlt.expect_or_drop with a constraint that order_total >= 0, which drops violating rows while recording the count. ✓ (correta)
  4. @dlt.expect_or_fail with a constraint that order_total >= 0, which stops the pipeline on any negative value.
Por que esta é a correta

@dlt.expect_or_drop is correct because its action removes rows that violate the constraint from the target dataset while still recording the violation count in the pipeline metrics — precisely the discard-but-count requirement. @dlt.expect is wrong because its action retains violating rows, so negative order_total values would remain in the table. @dlt.expect_or_fail is wrong because it halts the entire pipeline run on a violation rather than dropping the offending row and continuing. Adding a CHECK constraint via ALTER TABLE after the run is wrong because it is a post-hoc table constraint applied outside the pipeline's quality flow, and the claim that DLT cannot drop rows is false — expect_or_drop does exactly that during the run.

Questão 3 · Production Pipelines

A Delta Live Tables pipeline ingests customer records. The team wants to keep rows that violate a data quality rule but track how many failed, without dropping or failing the pipeline. Which expectation configuration achieves this?

  1. Use @dlt.expect (the warn/retain action) so violating rows are kept and the violation count is recorded in the event log and metrics. ✓ (correta)
  2. Use a plain WHERE filter in the query, since DLT expectations always drop violating rows by default.
  3. Use @dlt.expect_or_fail so the pipeline stops on the first violation, then read the failure metrics afterward.
  4. Use @dlt.expect_or_drop so violating rows are removed from the target while a count is still tracked.
Por que esta é a correta

@dlt.expect is correct because its action is to retain violating rows in the dataset while still recording the number of violations in the pipeline's metrics and event log — exactly the 'keep but track' behavior requested. @dlt.expect_or_drop is wrong because its action is to remove violating rows from the target, which contradicts the requirement to keep them. @dlt.expect_or_fail is wrong because it halts the pipeline run when a record violates the constraint, which the team explicitly wants to avoid. A plain WHERE filter is wrong because it silently excludes rows without producing any quality metrics, and the claim that DLT expectations 'always drop by default' is false — the action depends on which expectation decorator you choose.

Faça o simulado completo

  • 45 questões sorteadas do banco, com cronômetro de 90 minutos
  • Nota por domínio e revisão de cada questão
  • Tutor de IA para conversar sobre cada questão que você errar
  • O que você errou alimenta seu plano de estudo
Começar simuladoEstudar a trilha antes

Simulado independente e não oficial. Databricks e o nome da prova são marcas de seus donos; o UpSkillScore não é afiliado a eles. Formato e nota de corte são a configuração do simulado no UpSkillScore, não uma declaração oficial.

Perguntas frequentes

Quantas questões tem o simulado de Databricks Certified Data Engineer Associate?

Tem 45 questões e limite de 90 minutos. A nota de corte do simulado é 70%.

Este é o exame oficial de Databricks Certified Data Engineer Associate?

Não. É um simulado independente, montado para espelhar a estrutura da prova real. Ele não substitui o exame oficial.

Preciso de conta para fazer?

Você lê a estrutura e as questões de exemplo sem conta. Fazer o simulado completo cronometrado, a nota por domínio e o tutor de IA exigem conta.