0 / 20 answered

1. 1. What kind of data belongs in the Options API?

   What kind of data belongs in the Options API?

   Site-level configuration that is not tied to one post Every uploaded file Temporary request variables Theme template markup only
   Hint

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

2. 2. Why pass a default value to get_option()?

   Why pass a default value to get_option()?

   To create a database index To obtain predictable behavior before the option exists To force autoloading To bypass sanitization
   Hint

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

3. 3. What does update_option() do when an option does not exist?

   What does update_option() do when an option does not exist?

   It adds the option It silently discards the value It throws an exception It creates a post
   Hint

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

4. 4. Which option is a reasonable autoload candidate?

   Which option is a reasonable autoload candidate?

   A large remote API response A multi-megabyte report used monthly A small value needed on almost every request A temporary export archive
   Hint

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

5. 5. What is the risk of too much autoloaded option data?

   What is the risk of too much autoloaded option data?

   PHP cannot read arrays Every request may load unnecessary memory and database data Options become public automatically WordPress stops supporting plugins
   Hint

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

6. 6. When is one structured array option preferable to many scalar options?

   When is one structured array option preferable to many scalar options?

   When SQL joins are required When settings form one cohesive unit and are read together When each value is several megabytes When values have unrelated lifecycles
   Hint

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

7. 7. What does register_setting() define?

   What does register_setting() define?

   A setting, its group and sanitization/schema behavior A REST namespace only An admin menu page A cron event
   Hint

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

8. 8. What does settings_fields( $group ) print?

   What does settings_fields( $group ) print?

   The plugin stylesheet The option values as JSON Security and routing fields for the registered settings group Every input control automatically
   Hint

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

9. 9. What does do_settings_sections( $page ) render?

   What does do_settings_sections( $page ) render?

   Cron events The admin menu Registered sections and fields for a settings page REST routes
   Hint

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

10. 10. What should a setting sanitization callback return?

    What should a setting sanitization callback return?

    HTML output The database password The validated and normalized value to store A capability name only
    Hint

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

11. 11. Who normally submits forms through options.php?

    Who normally submits forms through options.php?

    Every anonymous visitor The active theme process Only WP-Cron A user with the capability required by the settings page
    Hint

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

12. 12. Why keep a stored plugin data version?

    Why keep a stored plugin data version?

    To run idempotent migrations when the schema or defaults evolve To clear every option daily To replace the plugin header To disable updates
    Hint

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

13. 13. What is a good use for a transient?

    What is a good use for a transient?

    Caching an expensive value that can be regenerated Permanent source-of-truth configuration A required audit log A user password
    Hint

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

14. 14. What does a transient expiration guarantee?

    What does a transient expiration guarantee?

    The value exists until the exact second The value will not be returned after that time; it may disappear earlier The value is stored outside the database The callback runs at expiration
    Hint

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

15. 15. Why can a WP-Cron event run later than scheduled?

    Why can a WP-Cron event run later than scheduled?

    WP-Cron is normally triggered by site requests WordPress uses browser time PHP cannot read timestamps Cron events run only in wp-admin
    Hint

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

16. 16. How should code avoid scheduling duplicate recurring events?

    How should code avoid scheduling duplicate recurring events?

    Delete the cron option directly Use a random hook name Schedule on every init request Check wp_next_scheduled() before calling wp_schedule_event()
    Hint

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

17. 17. What should a plugin do with its recurring events on deactivation?

    What should a plugin do with its recurring events on deactivation?

    Unschedule the events it owns when appropriate Leave unlimited duplicates Delete every WordPress cron event Disable the database
    Hint

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

18. 18. How does a scheduled WP-Cron event execute application code?

    How does a scheduled WP-Cron event execute application code?

    A browser opens the admin page The database executes PHP directly The theme template is copied WordPress fires the scheduled hook and registered callbacks run
    Hint

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

19. 19. Why may a long-running cron job need a lock or idempotency guard?

    Why may a long-running cron job need a lock or idempotency guard?

    Locks grant capabilities Cron cannot use PHP functions Concurrent or repeated executions must not duplicate side effects It makes URLs shorter
    Hint

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

20. 20. When is a real system scheduler preferable to traffic-driven WP-Cron?

    When is a real system scheduler preferable to traffic-driven WP-Cron?

    Only for CSS generation When execution timing and reliability are operationally important When WordPress has one user When no events exist
    Hint

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