Python Institute PCEA glossary of automation, files, APIs, retries, idempotency, logging, scheduling, and reporting terms.
Use this glossary when PCEA-30-0x: Certified Entry-Level Automation Specialist with Python terms start to blur together. The goal is practical recognition: what the term means in an automation scenario and what answer it usually supports.
| Term | Exam meaning |
|---|---|
| Automation | A repeatable script or workflow that performs a task with less manual effort and fewer avoidable errors. |
| Command-line argument | A value passed to a script when it starts, often used for input paths, modes, or options. |
| Environment variable | Runtime configuration supplied outside source code, often used for paths, modes, or credentials. |
| Idempotency | Design property that lets a task rerun without repeating completed side effects. |
| Checkpoint | A record of completed work that helps a script resume or skip safely. |
| Timeout | A maximum wait time for an operation such as an API call or subprocess. |
| Bounded retry | Retry behavior with a limit, delay, and failure path instead of an infinite loop. |
| Pagination | API behavior where many records are split across multiple responses. |
| Rate limit | Service rule that restricts how many requests can be sent in a time window. |
| Log | A record of events, counts, errors, and outcomes from a script or job. |
| Run summary | Final job record showing processed, skipped, failed, retried, and completed work. |
| Report | Human-readable or machine-readable output that summarizes automation results. |
| Pair | How to separate them |
|---|---|
| Retry vs idempotency | Retry tries again; idempotency makes trying again safe. |
| Timeout vs retry | Timeout limits a single wait; retry decides whether to attempt again after failure. |
| Log vs report | Logs support troubleshooting; reports summarize useful results for a reader or system. |
| Configuration vs secret | Configuration changes behavior; a secret grants access and must be protected more strictly. |
| Validation vs transformation | Validation checks whether input is acceptable; transformation changes valid input into output. |
| Scheduling vs monitoring | Scheduling starts the job; monitoring proves what happened after it started. |
Do not memorize definitions alone. For each term, write one scenario where it is the best answer, one scenario where it is a distractor, and one failure signal that proves the wrong automation strategy was chosen.