OutSystems Mobile Developer Specialist exam-day guide
OutSystems Mobile Developer Specialist · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the same ID whose name matches your registration exactly (including middle names and accents). If you registered with a name variant, confirm with the provider before test day that it will be accepted.
Appointment confirmation and test-provider login
Have your confirmation email, registration number, and provider portal credentials accessible. For remote proctoring, install and test the required secure browser or lockdown software beforehand; confirm with the provider which browser version and OS builds are supported.
Quiet, private test space and reliable network
For remote delivery, use a room with a closed door, no other people, and a stable wired or strong Wi-Fi connection. Clear the desk of papers, phones, and second screens unless the provider explicitly permits them; confirm with the provider what materials are allowed.
OutSystems documentation familiarity (not open-book unless permitted)
Most vendor certifications are closed-book. Assume no documentation access during the exam and confirm with the provider whether any reference material or built-in help is allowed.
Mobile development mental model: screens, blocks, actions, and data
Be ready to reason about Reactive Web vs. Mobile app architecture, screen lifecycle events (OnInitialize, OnReady, OnRender, OnDestroy), client vs. server actions, and when to use local storage, aggregates, or server-side logic.
Offline and synchronization concepts
Review how offline apps cache data, how synchronization actions work, conflict handling, and the limits of local storage. Be able to choose an approach for a scenario rather than recite API names.
Plugin and native-capability awareness
Know when a mobile plugin (camera, geolocation, barcode, push notifications) is needed, how plugin actions are called from client actions, and how permissions are declared. If you are unsure of an exact plugin name, answer on the concept.
Security and role model basics
Review authentication flows, role-based screen access, server-side validation, and why client-side checks are insufficient. Expect scenario questions about exposing data through APIs.
Timing and question strategy
Note the number of questions and total time from the provider's exam guide, then set a per-question pace. Flag and skip long scenario items, returning after you have banked easier points; confirm with the provider whether you can review flagged questions before submitting.
Backup plan for technical failure
Save the provider's support phone number and know the policy for disconnections or crashes. If the session fails, stop and contact support immediately rather than restarting on your own; confirm with the provider how incidents are handled.
Rest, hydration, and a light meal
Schedule the exam when you are normally alert, sleep adequately the night before, and eat lightly beforehand. Avoid heavy caffeine if you are sensitive to it.
needs_review: Exam format specifics
The exact number of questions, time limit, passing score, question types, and whether the exam is proctored remotely or at a test center vary by provider and version. Confirm all of these with the provider or the official exam guide before test day.
Plan the day
Re-read the official exam guide and skill outline. Map each listed topic to your own experience and mark weak areas. Spend the remaining time on those areas rather than re-reading material you already know. Do one timed practice set to calibrate pace, then review every wrong answer for the underlying concept.
Do a focused pass on mobile-specific topics: offline data and synchronization, client vs. server actions, screen lifecycle, plugins, and security. For each, write a two-sentence explanation in your own words. If you cannot, that topic needs another hour.
Confirm logistics: test time in your local time zone, location or remote setup, ID, and provider login. Test your equipment and network if remote. Do a final light review of your own notes and error log only, not new material. Stop studying early enough to sleep well.
Eat a normal meal, hydrate, and avoid cramming new topics. Log in early as instructed by the provider. Close other applications, silence devices, and keep your ID and any permitted items within reach. Take a few slow breaths and set your pacing target before starting.
Read each scenario for the constraint that decides the answer, such as offline requirement, security boundary, or performance. Answer confident items first, flag uncertain ones, and return with remaining time. Watch the clock at the halfway point. If a technical problem occurs, pause and contact proctor or support rather than troubleshooting alone.
Rules to check
Bring identification that exactly matches your registration. Name mismatches are a common reason for being turned away; confirm with the provider in advance if your registered name differs from your ID.
Follow the provider's conduct rules on permitted materials, notes, second screens, phones, and other people in the room. When in doubt, ask before the exam rather than assume something is allowed.
Do not share, record, or reproduce exam questions or answers in any form. Treat the exam content as confidential and check the provider's confidentiality agreement for specifics.
Understand the break policy before you start. Some deliveries allow scheduled breaks and others do not, and leaving the view of the camera or room may be treated as a violation; confirm with the provider.
Know how scoring works: whether wrong answers are penalized, whether partial credit exists on multi-select items, and what score passes. If this is not stated in the exam guide, confirm with the provider.
If you are disconnected or the session crashes, stop and contact the provider's support line immediately. Do not attempt to restart or retake on your own, and keep any incident reference number.
Arrive or log in early per the provider's instructions, but do not expect to start before your scheduled window. Late arrival may forfeit your seat or session; confirm the grace period with the provider.
If you need an accommodation, request it well before test day through the provider's process. Do not assume it can be arranged on the day itself.