โ† All GMI Flashcard Decks

Automation & Scripting Flashcards

7 cards from real GMI practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Automation & Scripting flashcards as text
  1. In a prepress automation pipeline, which method is preferred for passing job parameters between scripts to maintain traceability?

    Answer: Using structured job ticket files such as JDF or XML

    Structured job ticket files like JDF or XML provide a documented, auditable record of all job parameters passed between scripts.

  2. Which Python library is most commonly used to automate PDF inspection tasks in a GMI scripting environment?

    Answer: PyPDF2 or pikepdf

    PyPDF2 and pikepdf are purpose-built Python libraries for reading, inspecting, and manipulating PDF files.

  3. A GMI script processes 500 files sequentially and takes 10 minutes. To reduce runtime, the best architectural change is:

    Answer: Refactor the script to process files in parallel using worker threads or multiprocessing

    Parallelizing file processing across multiple worker threads or processes leverages available CPU cores to reduce total runtime.

  4. In automation scripting, what does 'idempotency' mean in the context of GMI job reprocessing?

    Answer: Running the script multiple times on the same input produces the same result without side effects

    An idempotent script safely re-executes on the same input without duplicating outputs or corrupting data.

  5. When a GMI automation script needs to log processing results for later auditing, which logging level should be used for successful file completions?

    Answer: INFO

    INFO level is the standard logging level for recording normal, successful operational events.

  6. Which file format is the standard for exchanging job definitions and workflow instructions between GMI-compatible automation systems?

    Answer: JDF (Job Definition Format)

    JDF (Job Definition Format) is the ISO-standard XML-based format for describing print job parameters and workflow instructions.

  7. A automation script must exit with a non-zero exit code when a preflight check fails. Why is this important in a CI/CD-style pipeline?

    Answer: Downstream pipeline steps check the exit code to determine whether to continue or halt

    Non-zero exit codes signal failure to the orchestrating system, enabling conditional branching or automatic halting of dependent steps.