Use your own practice account and test data. Record an observation for each completion claim. You can print this worksheet or keep your answers in your own notes; this page does not submit them.
1. Know which value must stay private
Which value must stay off the visitor’s page, and what evidence will you ask the assistant to inspect?
Review your work
Identifies the provider key as secret and the practice access code as a separate lab boundary.
Names public files and browser requests as the places to inspect for accidental key exposure.
2. Start the supplied protected action
Did the action run, and what private-setup or provider stage is still blocked?
Review your work
Records the real local app address and one allowed action or an exact configuration/provider blocker.
Keeps the provider credential/model on the server and checks account usage terms before calling it.
3. Check privacy and failure together
What did the public-output check and the rejected attempt actually show?
Review your work
States which public output/requests were inspected without reproducing the provider secret.
Records a rejected access attempt and an unavailable-configuration attempt as failures.
4. Make one bounded change safely
Provide the changed action and the privacy/valid/invalid checks you actually ran.
Review your work
Changes the fixed response topic to DNS while preserving server-only key/model settings.
Retests the allowed and rejected calls and names remaining public-use cost/access controls.