PMLE Architecting Low-Code ML Solutions Practice Question
An organisation wants to use Document AI to process contracts but requires human review for high-risk clauses. Which feature should they enable?
⚠ Common exam trap
Many candidates confuse HITL with AutoML Training, thinking that training a model with human-labeled data is the same as having a human review live predictions, but HITL is a runtime workflow, not a training process.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Human-in-the-Loop (HITL)
Human-in-the-Loop (HITL) is the correct feature because it allows Document AI to automatically process contracts while routing high-risk clauses to human reviewers for validation. This balances automation efficiency with the need for expert oversight on sensitive content, which is a core requirement for compliance-driven document processing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Human-in-the-Loop (HITL)
Why this is correct
Human-in-the-Loop routes low-confidence or high-risk clause extractions to human reviewers before finalising results, satisfying the stem's requirement for mandatory human review of high-risk clauses. Document AI's confidence thresholds trigger this escalation automatically, so contracts proceed without manual intervention except where risk demands it.
- ✗
Batch Processing
Why it's wrong here
Batch Processing only controls how documents are submitted asynchronously; it provides no human-in-the-loop review capability for high-risk clauses. It is tempting because it suits large document volumes, but it would be correct when throughput and cost matter, not when human validation of risky clauses is required.
- ✗
Online Prediction
Why it's wrong here
Online Prediction returns synchronous inferences from a deployed model but provides no human-in-the-loop workflow, so high-risk clauses cannot be routed for review. It is tempting because it is the standard serving mode for real-time Document AI requests, and would be correct when low-latency automated extraction is required without manual verification.
- ✗
AutoML Training
Why it's wrong here
AutoML Training builds a custom processor from labelled documents; it produces a model, not a review queue, so high-risk clauses still pass unreviewed. It is tempting because custom extraction of contract-specific fields genuinely needs AutoML, and it would be correct when the pre-trained processor's schema cannot recognise the required entities.
Go deeper
Related to this question
About these practice questions
One of 775 original PMLE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
4 more ways this is tested on PMLE
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A financial institution needs to extract structured data from scanned PDFs of loan applications, including text fields and tables. They require a human review step for high-risk applications. Which Google Cloud service and configuration should they use?
hard- ✓ A.Document AI with a form parser processor and enable Human-in-the-Loop for high-risk applications
- B.Document AI with a custom extractor processor and use Cloud Functions for human review
- C.Cloud Vision API to detect text and tables, then send to Cloud Dataflow for processing
- D.Vertex AI AutoML Vision to train a custom model for document parsing
Why A: Document AI's Form Parser processor is purpose-built to extract structured key-value pairs and tables from forms like loan applications, and it natively integrates with Human-in-the-Loop (HITL) to route low-confidence or high-risk documents to human reviewers. This combination directly satisfies both the extraction and human review requirements without custom code.
Variation 2. A company is building a document processing pipeline for invoices. They need to extract key fields (invoice number, date, total amount) and allow human review for invoices over $10,000. Which TWO Google Cloud services/features should they combine?
hard- A.Cloud Vision API for OCR
- ✓ B.Human-in-the-Loop (HITL) on Document AI
- C.AutoML Tables to predict missing fields
- ✓ D.Document AI with invoice parser processor
- E.Cloud Translation API to translate invoices
Why B: Option D is correct because Document AI's specialized Invoice parser processor is purpose-built to extract structured fields such as invoice number, invoice date, and total amount from invoice documents, which is exactly the extraction requirement in this pipeline. Option B is correct because Document AI's Human-in-the-Loop (HITL) feature lets you define confidence thresholds and route documents for manual review, which directly satisfies the requirement to have humans review invoices over $10,000 before downstream processing. Together, the Invoice parser handles automated field extraction while HITL provides the human verification step for high-value invoices. Option A is not the best fit because Cloud Vision API provides generic OCR without invoice-specific field extraction or built-in human review workflows. Option C is incorrect because AutoML Tables is a tabular ML service for structured data prediction, not for predicting missing fields in parsed documents. Option E is incorrect because Cloud Translation API only translates text and does not extract invoice fields or support human review.
Variation 3. A company needs to extract key fields from scanned invoices, such as invoice number and total amount, with high accuracy. They want a managed service and plan to use human review for low-confidence results. Which combination of services should they use?
medium- A.Vision API and Natural Language API
- ✓ B.Document AI and Human-in-the-Loop
- C.Translation API and AutoML Vision
- D.BigQuery ML and Vertex AI Prediction
Why B: Document AI is Google Cloud's managed document understanding service with specialized parsers (Invoice, Expense, Form) that extract structured fields like invoice number and total amount with high accuracy. Human-in-the-Loop (HITL) integrates directly with Document AI to route low-confidence predictions to human reviewers, whose corrections feed back to improve the processor. Together they satisfy the managed-service and human-review requirements in one pipeline.
Variation 4. A financial services company uses Document AI to process loan applications. They want to ensure that any documents the model cannot process with high confidence are reviewed by a human before finalizing the decision. Which Document AI feature should they enable?
hard- A.AutoML Tables model retraining
- B.Cloud DLP for data inspection
- C.Increase the number of processors
- ✓ D.Human-in-the-Loop (HITL)
Why D: Human-in-the-Loop (HITL) in Document AI allows you to route documents that the model processes with low confidence to human reviewers for validation or correction before finalizing. This directly matches the requirement to have a human review any documents the model cannot process with high confidence.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMLE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMLE exam.