Final quiz — Session 10: complete program evaluation
Program : Applied AI — Intermediate Level — Instructor: Yann Isola
Format: 12 MCQ (multiple choice questionnaire) — only one correct answer per question — recommended duration: 12 minutes.
Special feature: this final quiz covers all 10 sessions of the program. One question per session, in the order of the course.
Question 1 — [Session 1 — Foundations] Why might an LLM (Large Language Model) fail to count the letters of the word “unconstitutionally”?
Answer: B. The model manipulates tokens, not characters. “Unconstitutionally” becomes 3–6 tokens ⚠ depending on the tokenizer: asking to count your letters is like asking to count the bricks of a wall while only seeing whole sections. (Session 1 — this was the very first “surprise” of the course.)
Question 2 — [Session 2 — Prompting] Among these four prompts, which one best applies good professional practices?
Answer: C. Role + specific task + constraints (length, tone) + variables + examples (few-shot, learning by examples): the complete recipe. A is empty, B confuses politeness and context, D maximizes unpredictability where we want control. (Session 2.)
Question 3 — [Session 3 — Structured output & temperature] You build a pipeline that extracts invoice amounts into automatically processed JSON (JavaScript Object Notation, structured data format). Which setting is most suitable?
Answer: B. Automated pipeline = reproducibility and guaranteed format. “Creativity” (high temperature) is a fault here: an ambiguous invoice must be reported , not interpreted with imagination. (Session 3.)
Question 4 — [Session 4 — RAG] What is the principle of RAG (Retrieval-Augmented Generation)?
Answer: B. The RAG does not modify the model (unlike A): it enriches the prompt at the time of the request with the passages retrieved. This is why it is continuously updatable and traceable (sources can be cited). (Session 4.)
Question 5 — [Session 5 — Tool calling] When a model “calls a tool”, who actually executes the action (database query, sending an e-mail, etc.)?
Answer: C. The model request , your code has . This is the foundation of tool security: validation, permissions and logging remain on your side. (Session 5 — and this is also the basis of “responsibility” seen in Session 10.)
Question 6 — [Session 6 — Agentic loop] What fundamentally distinguishes an agent from a simple model call?
Answer: B. The observation → decision → action loop is the definition of the agent. Corollary: without limits (iterations, budget, human validation for irreversible actions), a loop can get out of control. (Session 6.)
Question 7 — [Session 7 — Multi-agents & MCP] What is Model Context Protocol (MCP) used for?
Answer: B. MCP standardizes the tool/data connection: “a universal port” instead of tailor-made integration by client-tool pair. (Session 7.)
Question 8 — [Session 8 — Production] Your AI application receives HTTP 429 errors from the provider. What is happening and what are you doing?
Answer: C. 429 = “Too Many Requests”, rate limit signal, no failure. Engineer response: retry with exponential backoff + load smoothing. Confusing 429 with server failure leads to poor architectural decisions. (Session 8.)
Question 9 — [Session 9 — Evaluation] Why is “it looks good on my 5 tests” not an acceptable evaluation before going into production?
Answer: B. An evaluation worthy of the name: representative case set, explicit metrics, go/no-go threshold, and — final lesson of Session 10 — segmentation by group to uncover the biases that the average hides. (Session 9.)
Question 10 — [Session 10 — Governance] Your company deploys an AI candidate pre-screening assistant. According to the AI Act (European regulation on artificial intelligence) ⚠, which category does this system fall into, and with what main consequence?
Answer: C. Recruitment is explicitly in the areas to be high risk of the AI Act ⚠: authorized, but subject to heavy obligations, including human supervision. Neither forbidden (D), nor harmless (A, B). The amounts of sanctions and the application timetable are changing ⚠: check the state of the law at the time of the project. (Session 10.)
Question 11 — [Institutional sovereignty] Why is model liquidity a governance objective?
Answer: A. Model liquidity is a strategic insurance: it transforms the supplier into a replaceable component. It requires stable input/output contracts, comparable evaluations and a model-agnostic application layer.
Question 12 — [Institutional Sovereignty] What asset becomes the company's true defensible advantage in a mature AI system?
Answer: C. Models are becoming commonplace; the business context accumulates. The ontology, permissions, workflows, audit trails and human corrections form the flywheel that the company must have.