Training mode
Time remaining:
0 / 60 answered
Select all correct answers.
A nonce verifies intent, not the user’s role or capabilities.
Choose the answer that reflects current WordPress engineering practice.
It describes callback input, not execution order.
Choose the solution with the clearest boundary and safest lifecycle behavior.
Routes are public identifiers.
Existing posts may contain old markup.
It is not the operating system cron daemon.
The hook is dedicated to REST route registration.
Identify the data-model or security responsibility before choosing the API.
Do not invent password storage.
Think schema and access rules.
Consider lifecycle, authorization, failure and long-term maintenance.
There is a dedicated filter for the generated class list.
Select all generally appropriate safeguards.
Consider request intent, autosaves, and authorization.
The query contains values supplied at runtime.
Do not concatenate untrusted values into the SQL string.
Avoid caching a literal false when you must distinguish it.
The hook name describes theme initialization.
Stylesheet and template can mean child and parent.
Combine internationalization with context-appropriate output escaping.
The return value must distinguish priorities.
Identify the WordPress API responsibility before considering implementation details.
The server knows the correct URL and current nonce.
Several plugins share the same runtime.
Useful when one callback handles several hooks.
It is commonly used during versioned migrations.
Actions may ignore return values; filters may not.
Think of template-parts/content-single.php.
It can avoid loading block CSS where it is not needed.
Administrators need a recoverable state.
Choose the most accurate statement for WordPress development.
Think about when data enters the system and when it leaves for the browser.