Training mode
Time remaining:
0 / 50 answered
Identify the data-model or security responsibility before choosing the API.
Start with the everyday meaning of the WordPress term.
Treat names as input.
Place the concept in the WordPress request, content, or permission model.
Separate presentation responsibilities from reusable site functionality.
Identify the role of the WordPress function or extension point.
The parent theme directory is named lubinik-theme.
lubinik-theme
The value must match the parent directory name.
Consider lifecycle, authorization, failure and long-term maintenance.
A callback registered at priority 20 cannot be removed as though it used priority 10.
Client-provided names and MIME values are not enough.
Choose the conventional WordPress lifecycle hook.
It is the same common lifecycle point used for CPT registration.
They do not replace validation, escaping or authorization.
Activation is not guaranteed to run during every deployment pattern.
Choose the statement that correctly describes the contract expected by WordPress.
Ask yourself whether the received value must continue through the execution chain.
Escaping a string is not the same as validating a redirect destination.
Identify the WordPress API responsibility before considering implementation details.
Consider external object caches as well as the database implementation.
An expiration is a maximum lifetime, not a minimum lifetime.
Select all generally appropriate safeguards.
Consider request intent, autosaves, and authorization.
Prefer explicit inputs and APIs.
The query contains more than one metadata condition.
Think of boolean logic between clauses.
Broad instrumentation has a cost.
Select all correct answers.
A nonce verifies intent, not the user’s role or capabilities.
Intent and permission are separate questions.
A user may deactivate only to debug temporarily.
It is commonly used during versioned migrations.