OutSystems Architecture Specialist (O11) exam-day guide
OutSystems Architecture Specialist (O11) · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact ID name that matches your registration. If your registered name differs even slightly (middle name, accent, married name), contact the provider before test day to correct it - mismatches are a common cause of denied entry. Confirm with the provider which ID forms are accepted for your delivery mode (test center vs. online proctored).
Appointment confirmation and exam code
Know your appointment time, time zone, and the exam/voucher code if one was issued to you. Keep the confirmation email accessible offline (screenshot or PDF) in case connectivity fails. Confirm with the provider whether the OutSystems Architecture Specialist exam is delivered through a Pearson VUE-style test center, an online proctor, or an OutSystems-authorized channel, since logistics differ.
Test-center vs. online-proctored logistics decided
Decide in advance whether you sit at a test center or take it online. For online delivery, run the provider's system test on the same machine and network you will use, close all other applications, and clear your desk of papers, phones, and second screens. For a test center, plan the route and arrive early. Confirm the exact requirements with the provider.
Review the official exam blueprint / objectives
Download the current exam guide from the OutSystems certification pages and map each listed domain (architecture design, data modeling, security, performance, deployment/lifecycle, integration) to your own project experience. The blueprint is the single best predictor of question emphasis; treat third-party summaries as secondary.
Hands-on refresher in Service Studio and LifeTime
Re-create or revisit a small multi-module app: layered modules (core, library, UI), server actions vs. client actions, entities and relationships, aggregates, roles and permissions, and deploying through LifeTime. Architecture questions reward knowing where each artifact lives and why.
Practice scenario-based reasoning, not memorization
The specialist exam tests judgment: choosing module decomposition, deciding between server and client logic, handling referential integrity, planning environment promotion, and diagnosing performance bottlenecks. Practice explaining trade-offs out loud for each design decision you make.
Personal one-page summary sheet (for study, not the exam)
Condense your weak areas onto one page - e.g., module layering rules, security model (roles, authentication, end-user vs. service accounts), caching, and deployment stages. Review it in the final 24 hours. Leave it at home; most providers prohibit notes in the testing room.
Confirm allowed materials and scratch provisions
Ask the provider whether any reference material, calculator, or scratch paper/whiteboard is permitted. Do not assume - policies vary by delivery mode. Confirm with the provider rather than relying on forum posts.
Comfort items for a multi-hour session
Water and a light snack for before/after (test-center rules on bringing items into the room vary), layers for variable room temperature, and any medication you may need. Confirm break and item policies with the provider in advance.
Backup plan for technology failure
For online delivery: a charged backup device, a phone hotspot as a network fallback, and the provider's support number saved offline. Know how to reach support if the proctor session drops mid-exam.
Rest and timing plan for the week
Protect sleep in the 48 hours before the exam; avoid cramming new topics the night before. A rested candidate reasons better on scenario questions than a sleep-deprived one who memorized trivia.
Plan the day
Do a final pass over the official exam blueprint and rate your confidence per domain (high/medium/low). Spend remaining study time only on low-confidence domains. Re-run the provider's system test if taking the exam online, and confirm your appointment time and time zone. Stop learning brand-new tools; consolidate what you already know through hands-on practice in Service Studio.
Complete one or two full-length practice sessions under timed conditions if you have access to legitimate practice material, then review every wrong answer for the underlying principle, not the specific question. Revisit architecture trade-offs: module decomposition, server vs. client logic, security roles, and deployment lifecycle. Write your one-page summary sheet.
Light review only: skim your summary sheet and the blueprint. Confirm logistics - ID ready, route or online setup checked, support number saved, device charged. Avoid heavy new material. Go to bed at a normal hour; do not study late into the night.
Eat a normal meal and arrive early (test center) or log in early (online proctored) per the provider's check-in window. Do a calm five-minute skim of your summary sheet, then put it away. Re-check your workspace for prohibited items if online. Take a few slow breaths before starting - first questions often feel hardest.
Read each scenario fully before looking at the options; architecture questions often hinge on a constraint buried in one sentence. Eliminate clearly wrong answers first. Flag uncertain questions and return to them if the platform allows review. Watch the clock: pace yourself so you leave time to revisit flagged items. Answer every question - unless the provider states there is a penalty for guessing (confirm with the provider), an unanswered question cannot earn points.
Note which domains felt weak while memory is fresh, whether you passed or not. If you did not pass, check the provider's retake policy and waiting period (confirm with the provider) and schedule the retake while your study notes are current.
Rules to check
Bring valid government-issued photo ID whose name exactly matches your registration. If it does not match, resolve it with the provider before test day; do not expect an exception at the door.
Follow the provider's rules on prohibited items and behavior. In most proctored settings phones, smartwatches, notes, and unauthorized materials are not allowed in the testing room; confirm the specific list with the provider for your delivery mode.
Breaks are governed by provider policy and may not stop the exam clock. Confirm in advance whether scheduled or unscheduled breaks are allowed and whether the timer pauses; do not assume.
Scoring: understand in advance whether the exam is pass/fail against a scaled cut score and whether any questions are unscored pilot items. Do not try to infer scoring from question difficulty. Confirm the current scoring and passing standard with the provider, as these can change.
Do not attempt to record, screenshot, or share exam content. Exam items are confidential; violating this can void your result and affect eligibility for future certifications.
If you need an accommodation (extra time, separate room, screen-reader adjustments), request it through the provider well before the exam date; accommodations are generally not arranged on the day.
If technical problems interrupt an online session, stop and contact provider support immediately rather than continuing unaided; follow their instructions on rescheduling or case documentation.
Keep your certification record current: after passing, verify how the credential is issued and tracked (e.g., via the OutSystems certification portal) and note any recertification or expiry terms with the provider.