0 / 20 answered

1. 1. Which endpoint receives traditional WordPress AJAX requests?

   Which endpoint receives traditional WordPress AJAX requests?

   wp-json/ajax wp-content/ajax.php wp-admin/admin-ajax.php index.html
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

2. 2. Which request value selects a traditional AJAX handler?

   Which request value selects a traditional AJAX handler?

   action hook_priority callback route
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

3. 3. Which hook handles authenticated AJAX action save_note?

   Which hook handles authenticated AJAX action save_note?

   wp_ajax_save_note wp_rest_save_note ajax_save_note admin_post_ajax_save_note
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

4. 4. Which additional hook is needed when guests may call save_note?

   Which additional hook is needed when guests may call save_note?

   wp_ajax_public_save_note wp_ajax_nopriv_save_note rest_save_note guest_ajax_save_note
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

5. 5. How should a frontend script receive the AJAX URL and nonce?

   How should a frontend script receive the AJAX URL and nonce?

   Hard-code the production domain Pass server-generated configuration when enqueueing the script Read wp-config.php in the browser Store a secret in CSS
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

6. 6. Which helper verifies an AJAX nonce and stops on failure by default?

   Which helper verifies an AJAX nonce and stops on failure by default?

   esc_js() check_ajax_referer() wp_nonce_field() current_filter()
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

7. 7. What must still happen after AJAX nonce verification for a privileged change?

   What must still happen after AJAX nonce verification for a privileged change?

   Trust the JavaScript button state Check the current user capability Make the response public Skip validation
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

8. 8. Which helper returns a standardized successful JSON response?

   Which helper returns a standardized successful JSON response?

   echo_json_ok() rest_ensure_response() only wp_send_json_success() wp_die_success()
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

9. 9. Which helper returns a standardized error JSON response?

   Which helper returns a standardized error JSON response?

   wp_error_json() wp_send_json_error() status_header_only() throw_ajax()
   Hint

   Consider lifecycle, authorization, failure and long-term maintenance.

10. 10. On which hook should REST routes be registered?

    On which hook should REST routes be registered?

    wp_footer rest_api_init init only admin_menu
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

11. 11. Why use a namespace such as my-plugin/v1?

    Why use a namespace such as my-plugin/v1?

    To create a database To avoid collisions and provide an API version boundary To authenticate every user To enqueue scripts
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

12. 12. What does the methods route argument define?

    What does the methods route argument define?

    User roles Response fields Database columns The accepted HTTP methods
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

13. 13. What is permission_callback responsible for?

    What is permission_callback responsible for?

    Authorizing whether the request may reach the main callback Sanitizing every response Registering JavaScript Creating the route namespace
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

14. 14. How should a deliberately public REST route express permission?

    How should a deliberately public REST route express permission?

    Omit permission_callback Use __return_true as an explicit permission callback Disable REST authentication globally Use current_user_can( administrator )
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

15. 15. What can REST route argument definitions provide?

    What can REST route argument definitions provide?

    Type/schema, required rules, validation and sanitization Plugin activation Cron schedules Theme templates
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

16. 16. What object is normally passed to a REST endpoint callback?

    What object is normally passed to a REST endpoint callback?

    WP_REST_Request WP_Query only WP_User_Query WP_Theme
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

17. 17. Why return WP_REST_Response?

    Why return WP_REST_Response?

    To create a nonce To control response data, status, headers and links To render a theme template To bypass permissions
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

18. 18. What can a REST callback return for an application error?

    What can a REST callback return for an application error?

    WP_Error with suitable code, message and status data Only an empty string A PHP fatal error A database password
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

19. 19. What header commonly carries the REST nonce for cookie-authenticated requests?

    What header commonly carries the REST nonce for cookie-authenticated requests?

    X-WP-Nonce Cookie-Nonce-Only Authorization-Theme X-Plugin-Password
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.

20. 20. When is a custom REST route generally preferable to admin-ajax?

    When is a custom REST route generally preferable to admin-ajax?

    Only when PHP is unavailable When permissions should be skipped When designing a resource-oriented, reusable HTTP API contract When no request validation is needed
    Hint

    Consider lifecycle, authorization, failure and long-term maintenance.