OutSystems Delivery Specialist study plan

Map the four exam domains into a personal tracker, weighting Domain 1 and Domain 2 at 60% of total study time because they carry the same 25% each but anchor the rest of the material.

Define OutSystems platform vocabulary in your own words: module types, reactive vs traditional web, entities, aggregates, server actions, client actions, screens, and blocks.

Build a one-page glossary of 20 platform terms with a concrete example of where each appears in a real project.

Set up a free OutSystems personal environment and confirm you can create, publish, and open a blank reactive app end to end.

Model a normalized data layer for a small case study (for example a course enrollment app) with at least four entities and correct relationship cardinalities.

Write aggregates that filter, sort, and join entities, and explain in writing why an aggregate beats a hand-written loop for each case.

Implement static and dynamic entity actions and describe when server-side logic must run instead of client-side logic.

Document three data-modeling mistakes you made or nearly made and the correction for each.

Build a multi-screen flow with input validation, a list screen, and a detail screen, wiring navigation parameters correctly.

Implement client variables, screen input parameters, and session variables, and record which scope you chose and why for each value.

Add reusable blocks and a layout, then refactor duplicated UI into those reusable elements.

Trace one user action from button click through screen action, server action, and aggregate, writing the call path in order.

Implement exception handling with explicit error flows and user-facing messages, then test the failure path deliberately.

Apply role-based access control: define roles, protect screens and server actions, and verify a lower-privilege user is actually blocked.

Add a REST API integration consuming an external endpoint, including error handling for timeout and non-200 responses.

Review your app against a self-made checklist of 15 platform best practices and log every violation found.

Explain the deployment lifecycle from development to quality to production, including what a solution and a deployment plan contain.

Describe how OutSystems handles application versions, and practice tagging and rolling back a version in your environment.

Write a checklist for promoting an app between environments that covers dependencies, timers, and site properties.

Identify which configuration values belong in site properties rather than hard-coded in logic, and move at least three values accordingly.

Instrument your app with logs and timers, then verify a scheduled timer executes and is visible in the monitoring view.

Diagnose one deliberately introduced performance problem using aggregate analysis and explain the root cause in writing.

Describe the roles and responsibilities across a delivery team and where code review, testing, and release approval sit.

Draft a test plan covering unit, integration, and user acceptance levels for your case-study app.

Complete a full timed practice set across all four domains and score it by domain to expose weak areas.

Re-study your two lowest-scoring domains using targeted notes rather than re-reading everything.

Teach two difficult concepts aloud or in writing as if explaining to a junior developer, and note where your explanation stalled.

Rebuild one feature from scratch without notes to confirm retention.

Close the five weakest topics from week 7, writing a short corrective note for each.

Run two full timed mock exams under exam conditions and compare domain scores between attempts.

Review your glossary, checklists, and error log once, converting anything still shaky into flashcards.

Finalize exam-day logistics: format, timing, allowed materials, and a pacing strategy per question.