cert-bank

Exams

PLTR-APD Palantir Application Developer – Associate

Vendor
Palantir
Level
Associate
Questions
85
Time
180 min
Domains
8
In the bank
485

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

Guides for this exam

The exam at a glance

LevelAssociate
Questions85
Time180 minutes (about 2.1 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 · Ontology Schema Design and Workflow Assembly12.5%60
D2 · Action Types and Write-Back Patterns12.5%61
D3 · Ontology Functions12.5%61
D4 · Workshop Application Development12.5%60
D5 · OSDK, APIs, and External Applications12.5%62
D6 · Automate and Operational Workflows12.5%61
D7 · AIP Logic and AI-Powered Applications12.5%60
D8 · Application Security, Governance, and Operations12.5%60

D1 · Ontology Schema Design and Workflow Assembly 12.5%

A business process or a schema change is described, and you choose how to model it in the Ontology or assemble it from Workshop, Action Types and Automate. Typical traps include reading cardinality the wrong way round, changing a live link without knowing its consumers, and storing team-specific labels as data. Good answers keep stored values and identifiers stable and place each step in the component built for it.

What to watch for

Tasks in the official exam guide (4)
  • 1.1 Object types, properties, links, interfaces, shared properties and value types
  • 1.2 Stable identity, cardinality and meaningful relationships
  • 1.3 Assembling end-to-end workflows across Ontology, Workshop, Functions, Actions and Automate
  • 1.4 Workflow Lineage for impact, access troubleshooting and safe change

D2 · Action Types and Write-Back Patterns 12.5%

Questions about Action Types cover how changes are made, checked and secured. Scenarios include rules about who may act on what, concurrent users competing for the same record, external systems that need to hear about a change, and buttons that work for one user but not another. You pick the Action design or the first thing to check, and the answer usually depends on current state at execution time.

What to watch for

Tasks in the official exam guide (4)
  • 2.1 Declarative edit rules versus function-backed Actions
  • 2.2 Parameters, validation, submission criteria, forms, side effects and webhooks
  • 2.3 Independent security layers for action execution
  • 2.4 Testing and troubleshooting Actions

D3 · Ontology Functions 12.5%

Functions are judged on efficiency, safety and maintenance, in situations with large linked datasets, bulk edits, a language the team no longer knows, and consumers that still run old logic after a publish. You choose how to query, test or version the function. Right answers push filtering and aggregation to the server and treat each published version as a contract; wrong ones load everything into memory or change things in place.

What to watch for

Tasks in the official exam guide (4)
  • 3.1 Choosing TypeScript v2, Python v2 or AIP Logic
  • 3.2 Querying, aggregating, traversing links and editing safely
  • 3.3 Function-backed Actions, provenance, versioning and SDK bindings
  • 3.4 Testing and diagnosing function failures

D4 · Workshop Application Development 12.5%

Scenarios come from real Workshop modules: users who get lost, missing filter values, warnings that should appear, status changes, and an outside audience that needs a reduced view. The task is to pick the widget, variable, layout or deployment pattern that fixes the problem. Most correct answers connect widgets through variables and route every change through Actions instead of custom one-off logic.

What to watch for

Tasks in the official exam guide (4)
  • 4.1 Pages, sections, widgets, variables, events and modules
  • 4.2 Connecting Workshop to Ontology data, Actions, Functions and AIP
  • 4.3 Variable dependencies, asynchronous events and performance
  • 4.4 Deployment channels and preserving module interfaces

D5 · OSDK, APIs, and External Applications 12.5%

External applications built on the OSDK and REST APIs are the topic. The scenarios ask when to build outside Workshop, which identity a call should use, why totals disagree between apps, and how to handle credentials and failures. Strong answers match authentication to whether a user is present, compute numbers on the server, and fix a specific cause instead of widening permissions.

What to watch for

Tasks in the official exam guide (4)
  • 5.1 Application registration, OAuth, scopes and OSDK generation
  • 5.2 User-based versus service-based authentication
  • 5.3 Fetching, paginating, aggregating and invoking Actions via OSDK and REST
  • 5.4 Diagnosing scope, authentication, stale SDK, rate limit and deployment issues

D6 · Automate and Operational Workflows 12.5%

Automate questions present an automation that misbehaves or is about to go live: double effects, failures nobody sees, the wrong trigger type, or a risky first run. You decide on triggers, conditions, ownership and rollout steps. The intended answers assume an event can arrive more than once and plan for safe testing and a quick stop, rather than hoping everything runs exactly once.

What to watch for

Tasks in the official exam guide (4)
  • 6.1 Triggers, conditions, evaluation modes and effects
  • 6.2 Retries, backoff, fallbacks, notifications and ownership
  • 6.3 At-least-once execution, duplicates, races and live changes
  • 6.4 Testing automations and diagnosing failures

D7 · AIP Logic and AI-Powered Applications 12.5%

AI features inside applications are tested on where AI fits, how much access it gets and how its work is checked. Scenarios include AI-backed Actions, prompt updates, summaries with broad access and Functions written by AI FDE. Correct choices keep the AI to drafting or interpretation with the smallest set of inputs and tools, and require evidence (evaluation, review, tests) before release.

What to watch for

Tasks in the official exam guide (4)
  • 7.1 Prompts, typed I/O, tools, retrieval, agents and AI-backed Actions
  • 7.2 Minimum data and capabilities for AI workflows
  • 7.3 Evaluation, traces and execution history for AI features
  • 7.4 Reviewing AI FDE-generated Function code

D8 · Application Security, Governance, and Operations 12.5%

Security and operations questions usually separate two things that look alike: opening an app versus reading its data, user-scoped execution versus a service identity, or a UI filter versus a real data control. You pick the control or signal that fits the exact need. Good answers change only the failing control, enforce rules at the data level, and give operations leads health signals per component.

What to watch for

Tasks in the official exam guide (4)
  • 8.1 Roles, organizations, markings, restricted views, action permissions and branch protection
  • 8.2 Separating application access from data access
  • 8.3 User-scoped versus project-scoped execution and service identities
  • 8.4 Monitoring application, Ontology, automation and AIP health

A study order that works

The 17-day study plan for PLTR-APD 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 · Ontology Schema Design and Workflow Assembly
  2. Days 3–4: D2 · Action Types and Write-Back Patterns
  3. Days 5–6: D3 · Ontology Functions
  4. Days 7–8: D4 · Workshop Application Development
  5. Days 9–10: D5 · OSDK, APIs, and External Applications
  6. Days 11–12: D6 · Automate and Operational Workflows
  7. Days 13–14: D7 · AIP Logic and AI-Powered Applications
  8. Days 15–16: D8 · Application Security, Governance, and Operations
  9. Day 17: Final Review: Exam Strategy and Cross-Domain Judgement

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.