HubSpot CMS for Developers exam-day guide
HubSpot CMS for Developers · Prepare for the day ahead.
Your checklist
Confirm exam delivery format and proctoring requirements
HubSpot CMS for Developers is delivered as a proctored certification exam. Before exam day, log in to your HubSpot academy/certification account and confirm whether your sitting is remote-proctored or at a test center, which browser or lockdown software is required, and any system check you must run. Policies can change between sittings, so confirm with the provider rather than relying on older forum posts.
Government-issued photo ID
Bring the exact ID name that matches your registration. For remote proctoring, have it ready to show on camera; for a test center, bring the physical document. Confirm with the provider which ID types are accepted and whether the name must match your HubSpot account exactly.
Stable internet connection and a backup plan
Remote proctoring depends on a reliable connection. Test your upload/download speed and run the provider's system check in advance. Have a phone hotspot or a second network available as a fallback, and know the provider's procedure for a dropped connection.
Working webcam, microphone, and speakers/headset
Proctoring typically requires a camera and mic for identity verification and room scan. Use a wired or well-charged headset if permitted; confirm with the provider whether headphones are allowed or banned during the exam.
Clean, private testing space
Clear your desk of notes, books, second monitors, and phones unless the provider allows a phone for check-in only. Tell household members you cannot be interrupted. A room scan is commonly required at the start.
Review the official exam blueprint and topic weights
Pull the current exam objectives from the official HubSpot certification page and map each topic to your notes. Focus on HubL templating, modules and fields, the Design Manager, local development with the CMS CLI, HubDB, dynamic pages, and CMS APIs. Confirm the current format and topic weighting with the provider.
Rehearse HubL and module syntax from memory
Practice writing HubL tags for variables, loops, conditionals, macros, and filters; module and field JSON for common field types; and require/extends patterns for templates. Be able to read a snippet and predict its rendered output without an editor.
Know the local development workflow
Be able to describe installing and authenticating the CMS CLI, creating a project, uploading and fetching changes, and watching files. Know how local files map to Design Manager paths and how environment/portal selection works.
Practice HubDB and dynamic page concepts
Review creating tables and columns, publishing rows, querying rows in HubL, and wiring a dynamic page to a HubDB table by URL slug. Understand how dynamic pages resolve content and how to handle a missing row.
Skim the CMS APIs you are likely to be asked about
Know the purpose of the CMS content, HubDB, and blog APIs, how API keys/private app tokens are used, and basic request/response patterns. You do not need to memorize every endpoint, but know what each API family is for.
Prepare scratch materials allowed by the provider
If the provider permits blank paper and a pen or a whiteboard, have them ready. Confirm with the provider what is allowed; many proctored exams prohibit notes and additional screens.
Plan logistics: time zone, start time, and buffer
Convert the exam start time to your local time zone, set two alarms, and block the full appointment window plus check-in time. Confirm with the provider how early to log in and what happens if you are late.
Plan the day
Do a final pass over the official objectives and mark any weak areas. Spend the remaining time on hands-on practice in a sandbox portal: build a template with a custom module, add HubDB-backed dynamic pages, and push changes with the CMS CLI. Avoid starting brand-new topics you cannot finish.
Run the provider's system check and complete any registration or identity-verification steps. Confirm your appointment time, delivery format, and ID requirements with the provider. Reschedule now if something is wrong rather than on exam day.
Do light review only: HubL filters and control flow, module field JSON, and dynamic page URL rules. Stop studying early enough to sleep well. Charge your laptop, test your webcam and mic, and clear your desk. Prepare your ID and any allowed materials.
Eat, hydrate, and avoid cramming new material. Re-test your connection and camera, close unnecessary apps, silence your phone, and log in at the time the provider specifies. Have your ID and registration details within reach.
Read each question fully and watch for negatives such as 'NOT' and 'EXCEPT'. For code questions, trace the HubL or JSON line by line before choosing. Flag uncertain items and return to them if the platform allows. Budget time so you can review flagged questions before the clock ends.
Rules to check
Follow the provider's identity-verification process exactly. Present your government-issued photo ID when asked and keep your face in camera view if remotely proctored; confirm accepted ID types with the provider.
Do not use unauthorized notes, second screens, phones, smart watches, or AI assistants during the exam. Assume the session is monitored and recorded; confirm with the provider what materials and devices are permitted.
Stay in the testing environment for the duration unless the provider's rules allow a break. Many proctored exams do not permit breaks once the timer starts; confirm the break policy and whether the clock pauses.
Treat all exam content as confidential. Do not copy, screenshot, record, or share questions or answers, and do not discuss specific items in public forums afterward.
Understand the scoring model before you sit. Confirm with the provider the passing score, whether questions are weighted, whether there is a penalty for guessing, and how long results take and how they are delivered.
Know the retake and recertification policy in advance. Confirm with the provider how many attempts are allowed, any waiting period between attempts, and the validity period of the credential.
If a technical problem occurs, stop and contact the proctor or provider support immediately through the official channel rather than troubleshooting alone, and note the time and nature of the issue in case you need to request a reset.
Keep your registration details and confirmation email accessible in case support needs to verify your appointment.