What if I don’t know an answer — should I skip?

Yes — skip honestly. The scoring is built around it: any skipped question is excluded from both the earned and the possible total for that category. Skipping doesn’t hurt your grade, and guessing “Yes” when you don’t actually know just gives you a falsely-confident result that hides real risk.

The pattern I see most often: operators answer 35–45 questions confidently in 5 minutes, then have 5–10 they need to ask their dev team about. Those 5–10 become a written follow-up email (“is question seo-3 actually true on our store?”) and a fresh re-take a week later with proper answers.

The honest skip-strategy:

• If you’re an operator without dev access: skip anything starting with “does app/etc/env.php…” or “is the slow-query log…”. Take the visible-from-the-storefront questions, then circulate the rest.
• If you’re a senior dev: very few skips needed. If you’re skipping more than 10 of the 50, your team probably needs more visibility into the production environment.
• If you’re skipping more than 25: your team isn’t close enough to the store. That alone is a finding.