Besu Certified Professional exam-day guide
Besu Certified Professional · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the same ID you registered with; the name must match your registration exactly. If your registration used a shortened or different name form, confirm with the provider how to reconcile it before test day.
Registration and appointment confirmation
Save the confirmation email and any scheduling-portal login offline on your phone. You may need the appointment ID or a link to launch the exam; confirm with the provider whether the launch link is emailed or shown in the portal.
Test your computer and network ahead of time
If the exam is remotely proctored, run the provider's system check (browser, webcam, microphone, bandwidth) at least 48 hours before. Confirm with the provider which browsers and operating systems are supported and whether a wired connection is recommended.
Quiet, private room with a clear desk
Remote proctoring typically requires a closed room, no other people, and a desk free of papers, phones, and second screens. Confirm with the provider what is allowed on the desk (for example, a whiteboard or scratch paper may be prohibited or may need to be shown and erased on camera).
Know whether notes, docs, or a second monitor are permitted
Besu questions are practical, so the urge to look things up is strong. Do not assume open-book rules. Confirm with the provider whether any reference material, browser tabs, or additional displays are allowed; if not, plan to answer from memory.
Stable power and a backup plan
Charge your laptop and phone, and know your reconnection procedure. If the session drops, note the time and contact the proctor or support channel immediately; confirm with the provider how interruptions are handled and whether time is restored.
Review the exam blueprint and weighting
Re-read the official objectives list and note the domains you are weakest in. Confirm with the provider the current blueprint, number of questions, and time limit, since these can change between versions.
Hands-on Besu refresher, not just reading
In the final days, practice the operations the exam is likely to test: starting a node with a config file, key and genesis setup, permissioning files, JSON-RPC calls, and reading logs. Practical recall beats memorizing prose.
Command and config cheat sheet in your head
Be able to write from memory the shapes of common commands and files: besu --help flags, genesis JSON structure, static-nodes.json, permissions config, and typical JSON-RPC request bodies. Do not rely on having a terminal open during the exam unless the provider confirms it is allowed.
Water, snack, and restroom plan for breaks
Confirm with the provider whether scheduled or unscheduled breaks are allowed and whether the clock stops. If breaks are not permitted, plan hydration and restroom use before the session.
Support contact and incident notes
Have the provider's support phone or chat ready and a pen and paper (if allowed) to note timestamps of any technical issue. Confirm with the provider where to report incidents and how to request a retake if a failure is not your fault.
Read the scoring and result policy
Know the passing score, whether results are immediate or delayed, and how retakes work. Confirm with the provider the current pass mark and retake window, because these are set by the certification body and can change.
Plan the day
Do a full timed practice run using the official blueprint: answer questions under the real time limit without notes, then review every miss and map it to a Besu topic (networking, privacy, permissioning, consensus, JSON-RPC, operations). Spend the remaining time only on weak domains.
Re-run the provider's system check and test your webcam, microphone, and network in the room you will actually use. Fix anything now rather than on test morning. Confirm with the provider the check tool and supported setup.
Do a hands-on lab: build a small network or single node from scratch, configure genesis, add a peer, and query it over JSON-RPC. Write the commands and file contents from memory afterward and compare against the docs.
Light review only: skim your own notes on flags, config files, and error messages. Do not start new topics. Confirm your appointment time and time zone, and re-read the provider's rules on permitted materials, breaks, and room requirements.
Prepare the room and equipment: clear the desk, close other apps, update the browser, charge devices, and locate your ID and confirmation. Get a full night of sleep; cramming the night before tends to hurt practical recall.
Eat, hydrate, and use the restroom before the session. Log in early to complete ID checks and the room scan. Close all other applications and notifications, and put your phone away unless the provider says it is needed for the launch step.
Read each question fully and watch for qualifiers such as 'default', 'first', and 'most likely'. For practical Besu questions, reason from how the node actually behaves (startup order, config precedence, log output) rather than from memorized trivia.
Budget time: if a question is taking too long, flag it and move on, then return. For scenario questions, eliminate options that describe a command or file that does not exist or a flag with the wrong effect. Keep an eye on the clock and leave a few minutes to review flagged items.
Note any questions or technical issues while fresh, and check the provider's process for results and appeals. If the session was interrupted, follow up with support promptly and keep your incident timestamps.
Rules to check
Bring valid government-issued photo ID whose name matches your registration; if it does not match, confirm with the provider before test day how to resolve it.
Follow the provider's rules on permitted materials exactly. Do not assume notes, documentation, a terminal, or a second monitor are allowed; confirm with the provider what is permitted for your delivery format.
Do not communicate with anyone other than the proctor during the exam, and do not let anyone enter your testing space. Remote proctoring typically records video and audio.
Confirm with the provider whether breaks are allowed, whether they are scheduled, and whether the clock stops during them, then plan accordingly.
Understand the scoring policy before you start: the passing score, whether partial credit exists, and whether results are immediate. Confirm with the provider the current pass mark and result timing.
If your session fails for technical reasons, stop, note the time, and contact the proctor or support immediately; confirm with the provider how to request a retake or time extension.
Do not attempt to record, screenshot, or share exam content. Question banks and exam content are confidential, and sharing them can void your result.
Confirm with the provider the retake policy, including any waiting period and fees, before relying on a second attempt.