Nokia Services Architecture exam-day guide
Nokia Services Architecture · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the original ID whose name matches your registration exactly. Check the name spelling on your booking confirmation now; if it differs, contact the provider before test day to correct it. Confirm with the provider which ID types are accepted and whether a secondary ID is required.
Appointment confirmation and test-centre address
Save the confirmation email offline on your phone and print a copy. Verify the exact building, entrance, and room, since large conference-centre venues often have multiple halls. If testing online with a proctor, confirm the launch link and system-check time instead.
Know your exam code, version, and format
Write down the exam code, the number of questions, the time limit, and the passing score from your booking confirmation. Nokia certification exams are typically delivered through a Pearson VUE testing account, but confirm the exact code and current passing score with the provider because they can change between versions.
Services architecture domain map
Prepare a one-page sheet you can rebuild from memory: the layered view of Nokia's services architecture (access, aggregation, core transport, service layer, orchestration and management). Be able to place each product family and protocol on the map and explain the interfaces between layers.
Protocol and interface list
Revise the protocols that appear repeatedly in services architecture questions: IP/MPLS, segment routing, EVPN, BGP, OSPF/IS-IS, LDP, SRv6, NETCONF/YANG, gNMI, telemetry streaming, and timing (PTP/SyncE). For each, know the layer it belongs to and the problem it solves.
Calculation practice set
Rehearse the quantitative items: bandwidth and oversubscription ratios, MTU and encapsulation overhead, throughput versus line rate, and availability or redundancy arithmetic. Work them on paper without a calculator app you have not used before.
Scenario drill notes
Write five short design scenarios (for example, a mobile backhaul migration, a data-centre interconnect, a multi-service enterprise VPN, a slice-based 5G transport, and a greenfield segment-routing core). For each, note requirements, candidate architectures, trade-offs, and failure modes. This is the format most scenario questions use.
Error log review
Review only your own wrong-answer log from the last two weeks. For each entry, restate the correct reasoning in one sentence. Do not open new material in the final 24 hours.
Test-day logistics
Plan the route and arrive early; confirm parking or transit, and check local traffic. Bring water and a snack for before or after the exam if the provider permits items in the waiting area. Confirm with the provider what may be taken into the testing room.
On-screen tools familiarity
Know how to flag questions for review, how the review screen works, and whether a basic on-screen calculator or scratch materials are provided. Confirm with the provider which aids are allowed, since policies differ by delivery method.
Scratch materials plan
If the provider allows a whiteboard or paper, practise drawing your domain map on it in under two minutes. If only an on-screen notepad is available, practise typing the same map quickly.
Rest and focus plan
Protect sleep in the last two nights. A services architecture exam rewards steady reasoning over last-minute memorisation; fatigue costs more marks than one missed fact.
Plan the day
Confirm logistics: re-check the appointment time, venue or online-proctor requirements, ID rules, and the current exam code and passing score with the provider. Resolve any name mismatch now. Take one full-length timed practice run under exam conditions, then spend the rest of the day analysing errors by domain rather than re-reading notes.
Target your two weakest domains from the practice run. Rebuild your one-page architecture map and protocol list from memory, then check them against your notes. Redo the calculation drills you got wrong. Stop adding new topics.
Light review only: your error log, the domain map, and the scenario notes. Pack ID, confirmation, and any permitted materials. Do a final route or system check for online delivery. Set two alarms, eat properly, and go to bed at your normal time. Do not attempt a new mock exam the night before.
Eat a normal meal and skim only the one-page map. Leave with buffer time so arrival stress does not eat into your focus. At the test centre, follow check-in instructions; for online delivery, complete the system and ID check early and clear your desk as instructed.
Read the instructions and note the time limit and question count. On scratch material, write your architecture map and the protocol-to-layer list immediately, before question one. This externalises memory and gives you a reference for the whole session.
Work in two passes. First pass: answer what you know, flag anything needing more than roughly a minute, and never leave a question blank if the format has no penalty for guessing (confirm the scoring rule with the provider). Second pass: return to flagged items, eliminate options by layer and interface first, and check that scenario answers address every stated requirement. Reserve the last few minutes to confirm no question is unanswered.
Note which domains felt weak while memory is fresh. If a result is not shown on screen, confirm with the provider how and when it will be reported and what the retake policy is.
Rules to check
Bring the original government-issued photo ID whose name matches your registration exactly. Confirm accepted ID types and any secondary ID requirement with the provider; a mismatch can bar entry.
Arrive at or before the appointed time and follow all check-in and security instructions, including any bag, phone, or wearable restrictions. Late arrival may forfeit your seat, so confirm the provider's cut-off rule.
Do not bring unauthorised materials into the testing room: no notes, books, second devices, or smart watches. Use only scratch materials or on-screen tools the provider explicitly allows.
Breaks are generally not permitted during a timed certification exam, and the clock usually keeps running if one is granted. Confirm the break policy for your delivery method with the provider before test day.
Scoring is typically based on the number of correct answers against a passing score set for the exam version; some questions may be unscored trial items. Confirm the current passing score and whether wrong answers are penalised with the provider rather than assuming.
Keep exam content confidential. Do not record, photograph, reproduce, or discuss specific questions afterwards; doing so can invalidate your result and breach the candidate agreement.
If a technical failure occurs during an online-proctor session, stop and contact the proctor or provider support immediately rather than continuing, and note the incident for a possible reschedule.
Report any suspected error in a question only through the provider's official comment or support channel; do not let one doubtful item consume your time budget.