cert-bank

Exams

PLTR-DE Palantir Data Engineer – Associate

Vendor
Palantir
Level
Associate
Questions
95
Time
180 min
Domains
8
In the bank
535

Practice 535 questionsTake a timed mock examDay-by-day study plan

Guides for this exam

The exam at a glance

LevelAssociate
Questions95
Time180 minutes (about 1.9 minutes per question)
Passing mark70% of the questions

Domains and weights

The vendor does not publish domain weights for this exam, so the shares below are equal by assumption. Treat every domain as roughly the same size.

DomainWeightPractice questions here
D1 · Data Connectivity and Ingestion12.5%67
D2 · Data Transformation and Pipeline Authoring12.5%66
D3 · Pipeline Processing Modes12.5%67
D4 · Pipeline Operations and Scheduling12.5%67
D5 · Data Quality and Health Monitoring12.5%67
D6 · Security, Projects, and Governance12.5%66
D7 · Ontology Data Modeling12.5%68
D8 · AI-Assisted Data Engineering12.5%67

D1 · Data Connectivity and Ingestion 12.5%

Ingestion scenarios describe a source (where it sits on the network, how it delivers data, whether it has a reliable change column) and ask for the connection and sync pattern that fits. Some also concern virtual tables or a standard way to onboard many sources. Wrong options force a source into a pattern it does not support, such as an incremental sync with nothing reliable to key on.

What to watch for

Tasks in the official exam guide (4)
  • 1.1 Connectors and connection architecture
  • 1.2 Snapshot, append, update and CDC ingestion
  • 1.3 Agents, egress, virtual tables and exports
  • 1.4 Diagnosing stale or failing ingestion

D2 · Data Transformation and Pipeline Authoring 12.5%

Transform questions focus on correctness and maintainability more than syntax. Situations include business definitions that must not drift, missing values in aggregates, cleanup rules that change over time, and small jobs on a heavy engine. The best options make the logic testable and visible (unit tests, expectations, branch comparisons, reference datasets) and keep the engine sized to the data.

What to watch for

Tasks in the official exam guide (4)
  • 2.1 Pipeline Builder, Code Workspaces or Code Repositories
  • 2.2 Joins, aggregations, expressions and enrichment
  • 2.3 Choosing a compute engine
  • 2.4 Testing, debugging and refactoring transforms

D3 · Pipeline Processing Modes 12.5%

This domain turns on how data moves through a pipeline: batch, incremental or streaming, and what each transaction type does to a dataset. Scenarios mix freshness needs, unexpected full recomputes and streaming jobs that stall while still running. You choose the mode, explain the behaviour or pick what to check first, and precise knowledge of the transaction types often decides the answer.

What to watch for

Tasks in the official exam guide (4)
  • 3.1 Batch, incremental, streaming or lightweight
  • 3.2 SNAPSHOT, APPEND, UPDATE and DELETE semantics
  • 3.3 Incremental fallback to snapshot
  • 3.4 State, backlogs, small files, replay and schema evolution

D4 · Pipeline Operations and Scheduling 12.5%

Running pipelines day to day is the subject: schedules, slow builds, chains of failures and compute cost. Scenarios give symptoms (a doubled runtime, many red builds, a high bill, a source that skips holidays) and ask for the likely cause or the next step. Answers that use evidence such as Job Comparison and lineage, and that remove unneeded work first, beat simply adding resources.

What to watch for

Tasks in the official exam guide (4)
  • 4.1 Schedules and event-based triggers
  • 4.2 Diagnostic evidence: builds, logs, lineage, Spark details
  • 4.3 Classifying slowdowns and failures
  • 4.4 Branches, releases, resources and cost

D5 · Data Quality and Health Monitoring 12.5%

Data quality scenarios ask which control fits a risk and what to do when an alert fires. You weigh build-blocking expectations against health checks, isolate bad input files, trace schema changes and define what a new dataset needs before it ships. The key distinction is between a rule that must never be broken and a shift that might be genuine business change.

What to watch for

Tasks in the official exam guide (3)
  • 5.1 Expectations versus health checks
  • 5.2 Blocking invalid transactions
  • 5.3 Monitoring, alerts and investigation

D6 · Security, Projects, and Governance 12.5%

Most security scenarios here are puzzles about why one person sees less than expected, or how to grant exactly the right access. You reason across project roles, markings, organizations, restricted views and Ontology policies. The trap is assuming a higher role fixes everything; correct answers find the specific missing control and enforce restrictions in the data layer so they hold on every path.

What to watch for

Tasks in the official exam guide (4)
  • 6.1 Organizations, markings and project roles
  • 6.2 Project structure and boundaries
  • 6.3 Restricted views for row-level access
  • 6.4 Diagnosing access failures

D7 · Ontology Data Modeling 12.5%

Ontology modeling questions ask how real-world things and relationships become object types, links and keys, and how to change a live model safely. Scenarios cover cardinality, relationships that change over time, attributes in the wrong place and retiring old types. Wrong options often store entity facts on pair or summary objects, or skip the migration of user edits.

What to watch for

Tasks in the official exam guide (5)
  • 7.1 Object types, properties, links and interfaces
  • 7.2 Primary keys and link cardinality
  • 7.3 Normalization and modeling anti-patterns
  • 7.4 Evolving live Ontology resources
  • 7.5 Computation north or south of the Ontology

D8 · AI-Assisted Data Engineering 12.5%

AI shows up here in two roles: as a helper for engineers and as a step that enriches data. Scenarios ask which AI capability fits, where it should run, how to keep repeated runs affordable, and how to review AI-written transforms. Sound answers keep deterministic logic first, verify AI output and code against lineage and contracts, and record versions so results can be traced and refreshed.

What to watch for

Tasks in the official exam guide (4)
  • 8.1 AI FDE, AIP Assist, Continue and LLM transforms
  • 8.2 Structured outputs, caching and quality checks
  • 8.3 Pipeline-layer versus Ontology-layer AI
  • 8.4 Reviewing AI-generated code and outputs

A study order that works

The 17-day study plan for PLTR-DE takes the domains in this order. Each day has a short reading, key terms and a quiz from the bank.

  1. Days 1–2: D1 · Data Connectivity and Ingestion
  2. Days 3–4: D2 · Data Transformation and Pipeline Authoring
  3. Days 5–6: D3 · Pipeline Processing Modes
  4. Days 7–8: D4 · Pipeline Operations and Scheduling
  5. Days 9–10: D5 · Data Quality and Health Monitoring
  6. Days 11–12: D6 · Security, Projects, and Governance
  7. Days 13–14: D7 · Ontology Data Modeling
  8. Days 15–16: D8 · AI-Assisted Data Engineering
  9. Day 17: Final Review: Cross-Domain Judgement and Exam Readiness

Recent changes to these questions

About these questions

Every question is original, written from the public exam guide and checked against the vendor's own documentation. None comes from a real exam. Each one has an explanation of why the answer is right and why the other options are wrong. How the questions are written.