0 / 17 answered

1. 1. What is required for the permission_callback of a custom REST route?

   Choose the safest general rule.

   What is required for the permission_callback of a custom REST route?

   Always return true, including for destructive operations. Define it explicitly and check the capability required by the operation. Omit it because REST requests are automatically admin-only. Check only whether a nonce field exists, without verifying it.
   Hint

   Public and protected routes both need an explicit permission decision.

2. 2. Which hooks handle a custom WordPress AJAX action named save_note?

   The action may support both authenticated and unauthenticated visitors.

   Which hooks handle a custom WordPress AJAX action named save_note?

   rest_api_save_note wp_ajax_nopriv_save_note wp_ajax_save_note ajax_init_save_note
   Hint

   The unauthenticated variant has an extra suffix.

3. 3. On which hook should custom REST API routes be registered?

   On which hook should custom REST API routes be registered?

   rest_api_init wp_loaded init template_redirect
   Hint

   The hook is dedicated to REST route registration.

4. 4. What can a REST route argument definition provide?

   What can a REST route argument definition provide?

   Validation and sanitization callbacks plus schema information A database migration A JavaScript bundle A replacement for all permission checks
   Hint

   Separate input shape from authorization.

5. 5. Which helper sends a JSON success response and terminates a WordPress AJAX request?

   Which helper sends a JSON success response and terminates a WordPress AJAX request?

   wp_send_json_success() wp_die_json() esc_js() return_json()
   Hint

   WordPress provides paired success and error helpers.

6. 6. What is the recommended role of block.json in modern block development?

   What is the recommended role of block.json in modern block development?

   Store visitor answers Register a custom database table Replace every render callback Declare shared block metadata used by WordPress and tooling
   Hint

   It is a manifest for a block.

7. 7. When is a server-side render_callback particularly useful for a block?

   When is a server-side render_callback particularly useful for a block?

   When output depends on current server data or should update without resaving posts When JavaScript is forbidden in the editor Only when the block has no attributes To bypass escaping
   Hint

   Consider a latest-posts style block.

8. 8. What is a benefit of returning WP_REST_Response from a REST callback?

   What is a benefit of returning WP_REST_Response from a REST callback?

   It converts the route into GraphQL It disables authentication It provides explicit control over data, status and headers It automatically creates a nonce
   Hint

   It is the response object for the REST server.

9. 9. What problem does the WordPress Interactivity API address?

   What problem does the WordPress Interactivity API address?

   Consistent client-side interactions for block frontends SQL schema migrations Plugin update signing Theme screenshot generation
   Hint

   It concerns frontend behavior in blocks.

10. 10. Why should custom REST routes use a versioned namespace such as my-plugin/v1?

    Why should custom REST routes use a versioned namespace such as my-plugin/v1?

    It replaces permission_callback It authenticates every request It creates a database table It avoids collisions and allows future incompatible versions
    Hint

    Routes are public identifiers.

11. 11. How can a WP_Error returned by a REST callback specify an HTTP status?

    How can a WP_Error returned by a REST callback specify an HTTP status?

    Include status in the error data Put the status in the error code string Add a query parameter Call status_header() only
    Hint

    The REST server maps error data to the response.

12. 12. What does register_rest_field() add?

    What does register_rest_field() add?

    A field to REST responses for one or more object types An admin settings section A block editor panel automatically A database column
    Hint

    It extends the API representation.

13. 13. On the frontend, how should a plugin usually provide admin-ajax.php and nonce values to its script?

    On the frontend, how should a plugin usually provide admin-ajax.php and nonce values to its script?

    Read wp-config.php from the browser Pass server-generated data when enqueueing the script Hard-code the full domain in JavaScript Store them in localStorage at install time
    Hint

    The server knows the correct URL and current nonce.

14. 14. What do block attributes represent?

    What do block attributes represent?

    Database indexes Global PHP constants The structured state of a block that can be serialized or sourced from markup User capabilities
    Hint

    They connect editor state with saved or rendered output.

15. 15. What is the purpose of deprecated block versions in registerBlockType settings?

    What is the purpose of deprecated block versions in registerBlockType settings?

    Remove REST routes Disable the block permanently Translate PHP strings Migrate and recognize older saved block markup
    Hint

    Existing posts may contain old markup.

16. 16. What is a drawback of calling ServerSideRender for every small editor interaction?

    What is a drawback of calling ServerSideRender for every small editor interaction?

    It disables PHP It makes blocks private Repeated HTTP requests can make the editor slow It prevents attributes
    Hint

    Consider editor responsiveness.

17. 17. For cookie-authenticated REST requests from WordPress admin, which header commonly carries the REST nonce?

    For cookie-authenticated REST requests from WordPress admin, which header commonly carries the REST nonce?

    WP-Cookie-Hash X-WP-Nonce X-CSRF-WordPress-Admin Authorization-Nonce
    Hint

    wp.apiFetch middleware can supply it.