0 / 20 answered

1. 1. Which boundary is healthiest?

   Which boundary is healthiest?

   Templates store secrets Core files own custom features Themes own every business rule Plugins own reusable behavior; themes own presentation
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

2. 2. What does single responsibility improve?

   What does single responsibility improve?

   Focused components have fewer reasons to change Hooks are unnecessary All code fits one file Every class becomes global
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

3. 3. What should a plugin bootstrap file mainly do?

   What should a plugin bootstrap file mainly do?

   Contain every feature implementation Render all templates Define identity, guard loading and compose required components Store generated data
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

4. 4. Which dependency direction is preferable?

   Which dependency direction is preferable?

   Every class reads globals directly Core logic depends on admin HTML Domain rules depend on one theme template Feature code depends on stable abstractions or services
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

5. 5. Why inject collaborators instead of constructing them everywhere?

   Why inject collaborators instead of constructing them everywhere?

   WordPress skips hooks Objects become global PHP uses less syntax Dependencies become explicit and replaceable
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

6. 6. Why minimize hidden global state?

   Why minimize hidden global state?

   It disables caching Globals cannot hold arrays It creates order-dependent behavior and difficult tests WordPress forbids globals
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

7. 7. Why centralize or structure hook registration?

   Why centralize or structure hook registration?

   Hooks run faster automatically Priorities disappear Lifecycle wiring becomes discoverable and avoids accidental duplicates Callbacks need no names
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

8. 8. What should be treated as a plugin public API?

   What should be treated as a plugin public API?

   Documented hooks, functions, classes, routes and stored contracts used externally Temporary local variables Only private methods Debug messages
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

9. 9. Why preserve backward compatibility?

   Why preserve backward compatibility?

   Updates cannot change files Existing sites and integrations depend on earlier contracts WordPress forbids versions Only themes need compatibility
   Hint

   Choose the solution with the clearest boundary and safest lifecycle behavior.

10. 10. What is a good deprecation strategy?

    What is a good deprecation strategy?

    Rename without notes Keep compatibility temporarily, signal replacement and document migration Delete behavior silently Trigger fatal errors immediately
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

11. 11. What makes a safe data migration?

    What makes a safe data migration?

    Depending on one browser session Running destructive SQL on every request Ignoring partial failure Versioned, idempotent, bounded and recoverable behavior
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

12. 12. Why define data schemas and validation at boundaries?

    Why define data schemas and validation at boundaries?

    It replaces authorization It removes backups It makes all values strings Inputs and stored values follow explicit contracts
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

13. 13. What should happen before a template receives data?

    What should happen before a template receives data?

    The template activates plugins The controller or service prepares a clear view model The template performs every database mutation The template reads raw request data
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

14. 14. Where should output escaping occur?

    Where should output escaping occur?

    Only when data enters the database During plugin activation At the final rendering context Inside SQL placeholders
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

15. 15. What is a risk of calling a global service locator everywhere?

    What is a risk of calling a global service locator everywhere?

    WordPress removes filters PHP stops autoloading Services cannot be objects Dependencies become hidden and components tightly coupled
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

16. 16. How should configuration and secrets differ?

    How should configuration and secrets differ?

    Defaults must be encrypted Both belong in public JSON Secrets belong in JavaScript Non-secret defaults may be versioned; secrets belong in protected runtime storage
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

17. 17. What is a feature flag useful for?

    What is a feature flag useful for?

    Replacing tests Storing content Controlling rollout or fallback without branching the whole codebase Authorizing users permanently
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

18. 18. What should diagnostic logging include?

    What should diagnostic logging include?

    Only generic failed HTML styling Actionable context without credentials or unnecessary personal data Every request body and secret
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

19. 19. Which test mix gives strong confidence?

    Which test mix gives strong confidence?

    Only syntax checks Only manual happy paths Focused unit tests plus integration and end-to-end coverage at risky boundaries No tests for generated code
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.

20. 20. How should generated/scaffolded code be maintained?

    How should generated/scaffolded code be maintained?

    Preserve generator conventions and improve templates when the pattern is reusable Edit outputs inconsistently Create parallel loaders Ignore regeneration drift
    Hint

    Choose the solution with the clearest boundary and safest lifecycle behavior.