Salesforce MuleSoft Developer exam-day guide
Salesforce MuleSoft Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the original (not a photocopy) of a valid government-issued photo ID. The first and last name on it must match your exam registration exactly - if it does not, contact the provider before exam day to correct the registration, because mismatches can bar you from sitting the exam.
Appointment confirmation and exam code
Have your scheduling confirmation email accessible, including the exam name/code (Salesforce Certified MuleSoft Developer I), date, time, and time zone of your appointment. Double-check the time zone conversion the day before - a wrong conversion is the most common cause of missed appointments.
Platform account credentials
Know the username and password for the testing platform account used to register (MuleSoft exams are typically delivered through a proctored testing vendor). Verify you can log in at least 24 hours ahead so a password reset does not eat into exam time.
System / equipment check completed
For remote-proctored delivery, run the vendor's system readiness test on the exact machine and network you will use: webcam, microphone, browser version, and bandwidth. Confirm which browsers and any required secure-browser lockdown client are supported with the provider.
Quiet, private, well-lit room
Use a room with a closed door, no other people, and a desk cleared of papers, books, notes, phones, and secondary monitors. Proctors commonly ask for a 360-degree room and desk scan, so remove anything you would not want inspected.
Close all other applications and tabs
Shut down chat, email, screen-sharing, VPNs, and anything that could pop up a notification. Prohibited-software lists and lockdown behavior vary by vendor - confirm the current list with the provider rather than assuming.
Power and connectivity backup
Plug in your laptop and have a fallback connection (e.g., a phone hotspot) plus a phone number for the proctor/support desk, in case the primary connection drops mid-exam.
Know what materials are allowed
Scratch paper, pens, calculators, and water are usually restricted or require pre-approval in a proctored exam. Ask the provider in advance what, if anything, is permitted, and do not bring unapproved items to the desk.
Arrival / check-in buffer
Plan to start the check-in process well before your appointment slot so identity verification and the room scan are not rushed. The exact early-arrival window and late-arrival cutoff are vendor policies - confirm them with the provider.
One-page personal review sheet (study, not exam material)
In the final hours, review only your own summary of weak areas (e.g., error handling and scopes, DataWeave transformations, connectors, deployment/API-led topics, batch processing). Do not try to learn brand-new topics on exam day.
Plan the day
Take one full-length timed practice set under exam conditions, then spend the remaining time only on the two or three domains where you scored weakest. Stop expanding into new material.
Re-confirm the appointment details: exam name/code, date, start time, time zone, delivery mode (onsite test center vs. remote proctored), and any ID or system requirements. Fix registration-name issues now, not on exam day.
Run the vendor's system test on your final machine, and if you are testing remotely, decide exactly which room you will use and clear it in advance.
Do a light review of your own summary sheet and a handful of missed practice questions. No new topics, no marathon sessions. Confirm the passing score and question count/time limit from your appointment confirmation so you know the pace to keep.
Prepare logistics: ID out and ready, login credentials verified, charger packed, room cleared, backup internet arranged, and a calendar reminder set for the appointment in your local time.
Sleep a full night. Fatigue costs more points on a scenario-based multiple-choice exam than one extra hour of review gains.
Eat, hydrate, and avoid heavy cramming. Skim only your summary sheet. Log in early with ID and credentials in hand; complete the room scan and any proctor checks calmly.
Read each scenario fully and identify what is actually being asked (config vs. DataWeave vs. error handling vs. deployment) before looking at options. Budget roughly two minutes per question, flag long ones, and return to them - never leave a question blank if the platform does not penalize guessing.
Watch for absolute words (always, never) that usually signal a wrong option, and prefer answers that solve the stated problem with the least complexity. If a question is ambiguous, choose the option consistent with the platform's standard behavior rather than an edge case.
Before submitting, confirm no questions remain unanswered or flagged that you meant to revisit. Note your provisional result if the platform displays one, and keep the score report email for your records.
Rules to check
Bring an original government-issued photo ID whose name matches your registration exactly; a mismatch can result in being turned away, and the accepted ID list is set by the provider - confirm it in advance.
Follow the proctor's instructions at all times. Refusing a room scan, desk scan, or identity re-check can end the session, and repeated violations can be reported as misconduct.
Do not communicate with anyone, read notes aloud for assistance, or use unauthorized devices, second screens, or AI tools during the exam. Assume the session is recorded and reviewed.
Breaks and test-center amenities (water, restroom, leaving the room) are governed by provider and proctor policy. Raise your hand or use the proctor chat rather than leaving the view of the camera; confirm the rules before you start.
Scoring is criterion-based against a passing standard, not curved against other candidates, so aim to clear the published passing score rather than to 'beat the average'. The exact passing score and number of scored questions should be confirmed on the official exam guide.
Some exams include unscored pretest items mixed in with scored ones; treat every question with equal care rather than trying to guess which items count.
Do not attempt to reproduce, screenshot, or share exam content afterwards - doing so breaches the candidate agreement and can void your certification and result in a ban.
If technical problems interrupt your session, stop and contact the proctor/support immediately and get the incident documented; unresolved incidents are handled through the provider's case process, so keep the reference number.