I85PREP
⌘ K
PMI CD-P study materials
PMI CD-P study resources

PMI CD-P: Citizen Development Platform and Tooling

PMI CD-P · Work through your exam, one topic at a time.

All guide sections

Citizen Development Platform and Tooling

Domain 2 - Citizen Development Platform and Tooling

This domain tests platform literacy: what low-code and no-code tools can and cannot do, how to match capability to problem type, and when platform limits mean the work belongs with professional developers. Questions tend to target connectors, environments, licensing, data limits and reuse.

Know the capability layers

  • Data store, form and UI, workflow and automation, business logic, reporting, integration and connectors, identity, ALM and governance controls such as DLP, audit and environment policies.
  • Compare candidate tools against the layers the problem actually needs, not against the longest feature list.

Match tool to problem

  • Form and approval workflow: a form builder plus an approval engine.
  • Analysis and reporting: a BI or spreadsheet-style tool, not a transactional app.
  • High-volume integration or complex UI: likely a pro-code or IT-owned platform.
  • Offline field use: confirm offline capability and sync conflict handling before committing.

Environments, connectors and limits

  • Separate development, test and production; promote packaged solutions rather than editing live apps.
  • Use environment variables and connection references so the app moves between environments without hardcoded URLs or credentials.
  • Check connector tier and licensing: a free-looking design that needs a premium connector creates an unbudgeted cost.
  • Verify delegation, row limits and request thresholds. Many low-code data services silently return only the first few hundred or thousand rows.

Worked example

A finance team wants a nightly reconciliation of 50,000 rows. A canvas app reading the full table will hit delegation and request limits and perform poorly. Better: a scheduled dataflow or pipeline into a managed data store, with the app showing only summarized exceptions. Platform choice changes because of volume, not features.

Traps that cost marks

  • Designing with personal credentials so the app breaks when the maker leaves.
  • Ignoring premium licensing, capacity or per-user costs.
  • Choosing a tool before confirming data volume, offline needs and integration requirements.
  • Rebuilding an existing sanctioned tool rather than reusing it.