Advanced Generative AI Developer

Generative AI engineering at production scale. Preparing for the Generative AI Developer certification.

Exam Room · Advanced Generative AI Developer

Picking a Bedrock Model for High-Volume RAG

A million LLM requests a day, peaking at thirty per second, split across US and EU customers, with a P99 first-token target under 1.5 seconds and real reasoning over retrieved context. Bedrock lists models from more than a dozen providers across four service tiers. Most of the catalogue falls away once you name what decides it, and the harder work starts *after* you have picked the model.

Read article

Exam Room · Advanced Generative AI Developer

How to Build a Citations-Required RAG Over 50K Internal Documents

Fifty thousand internal documents, five gigabytes of text, weekly churn, a three-second latency budget, per-user access control, and a citation in every single answer. The RAG landscape on Bedrock is bigger than one product and the interesting part of the design is what falls away once you name the five things that actually decide it.

Read article

Exam Room · Advanced Generative AI Developer

Combining RAG and Fine-Tuning for a Legal Contract Assistant

A legal-tech team wants a contract review assistant that covers two hundred thousand past matters, writes in the firm's voice with clause-by-section citations, and returns a structured decline for anything off-domain. AUD$100,000, three months. Retrieval and fine-tuning each answer half of that sentence, and the third lever people reach for, continued pre-training, is no longer something Bedrock will run.

Read article

Exam Room · Advanced Generative AI Developer

Designing Short-Term and Long-Term Memory for a Bedrock Chat Assistant

A customer-support assistant where the average conversation runs fifteen turns before it resolves, and returning users pick up two weeks later expecting the bot to remember they've been waiting on a refund. Two memory problems in one product (what's live in the current conversation and what persists across visits) and four plausible ways to build it. Managed memory on Bedrock AgentCore handles both halves; the trap is the half where teams reach for DynamoDB or a knowledge base and get it wrong.

Read article

Exam Room · Advanced Generative AI Developer

Configuring Bedrock Guardrails for PII, Topics, and Grounding

A consumer-facing chatbot on Bedrock has passed every red-team round on the obvious harms (no weapons, no hate, no CSAM) and is still shipping embarrassments: a card number pasted by one user echoing back in a reply, the bot comparing the company's product with a named competitor, and a hallucinated policy line that nobody in the building wrote. Six different filter jobs wrap the same Bedrock invocation, and Guardrails is the one surface that does all six without six Lambdas.

Read article

Exam Room · Advanced Generative AI Developer

Spreading Bedrock Load with Cross-Region Inference Profiles

A Bedrock-backed SaaS serving US, EU and APAC customers sends every call through one US inference profile from one Region, and peak-hour throttling lands on that single token quota. A prefix on the model ID moves the traffic, provided the model publishes a profile for the geography you need and the residency boundary is the one you think it is.

Read article

Exam Room · Advanced Generative AI Developer

Building RAG When the Source Documents Change Daily

A support assistant that has to answer from a product manual which the product team edits weekly, a pricing sheet that changes at month-end, and an operational runbook that mutates hourly. No base model has seen any of it, and fine-tuning won't keep up. Retrieval is the answer, and what is left to decide is how much of the retrieval plumbing we want to own: Bedrock Knowledge Bases, a LangChain stack, and a hand-rolled pipeline each put the lines in different places.

Read article

Exam Room · Advanced Generative AI Developer

How to Wire an LLM to Side-Effecting Actions with Bedrock AgentCore

An assistant that has to look up a customer's subscription, pause it, refund a charge, and email confirmation. Not just answer, act. The glue between a language model and the rest of our systems comes down to one question: when the model asks to move money, what physically stops it until a human says yes? Bedrock AgentCore, a framework agent on our own infrastructure, and a hand-written tool router all put that gate in different places.

Read article

Exam Room · Advanced Generative AI Developer

Picking a Vector Store for Bedrock RAG

Twelve million embedding vectors, a 50ms retrieval budget, hybrid queries that mix keyword and semantic, and a bill that should not double the Bedrock spend on its own. OpenSearch Serverless, Aurora with pgvector, and Pinecone Serverless all serve the same shape of query, but their pricing curves, operational shapes, and query surfaces diverge the moment the corpus grows beyond demo scale.

Read article

Exam Room · Advanced Generative AI Developer

How to Manage Prompts Across Thirty Services on Bedrock

One prompt scattered across thirty services, no versioning, no tests, drift between the copy in the code and the copy in the docs, a silent regression when somebody changed 'concise' to 'brief' and retention on one response tanked. Prompt engineering across thirty services is a configuration-management problem. Bedrock Prompt Management, Git-backed templates, and parameterised prompts each solve a slice of it.

Read article

Exam Room · Advanced Generative AI Developer

Evaluating LLM Output With Bedrock Eval Jobs

Two thousand historical support tickets, a summarisation prompt, a cheaper model candidate, and a product manager asking whether switching would hurt quality. Amazon Bedrock evaluations offer programmatic scoring, a judge model, and human review by a work team you bring. Each answers a different question under different limits, starting with a thousand prompts per job.

Read article

Exam Room · Advanced Generative AI Developer

How to Build a Multi-Modal Bedrock Assistant for Insurance Claims

A claims-processing assistant that reads a scanned invoice, listens to a voicemail, answers the customer's question in plain text, and, if asked, reads it back. Four modalities, one conversation. The model choice, the orchestration shape, and the ways different inputs fail each push the architecture in different directions, and the naive 'just use a multi-modal model' misses half of where the real work is.

Read article

Exam Room · Advanced Generative AI Developer

How to Cut a Bedrock Bill Without Hurting Quality

A Bedrock bill that doubled in two months, a product team pointing at the retrieval service, a finance partner who would like a straight answer. Model routing, prompt caching, shorter outputs and tighter retrieval each take a different slice out of the token bill. Which of them work at all is decided by the model card, not by the architecture.

Read article

Exam Room · Advanced Generative AI Developer

Importing Custom Weights into Bedrock

A research team has fine-tuned an open-weights model for medical-notes summarisation on a private SageMaker cluster. The resulting weights live in S3; the production runtime needs Bedrock's ergonomics. Custom Model Import covers that gap, but only for a listed set of architectures, only in four Regions, and on a per-minute billing model rather than a per-token one.

Read article

Exam Room · Advanced Generative AI Developer

Streaming Responses to Cut First-Token Latency

A chat interface where users wait four seconds for any response on long generations, abandonment creeping up, product asking why we can't do the typing-animation thing every other assistant does. Streaming changes how the entire response path has to work, from the SDK call through the front door to the browser, and each hop has its own way of getting it wrong.

Read article

Exam Room · Advanced Generative AI Developer

When a Document Won't Fit the Context Window

A 400-page contract, a 200-page policy manual, and a legal team asking 'what clauses govern refund disputes across both?' Both documents fit inside a million-token window, which is not the same as getting good answers out of them. Chunking, map-reduce, hierarchical summarisation, and sliding context windows each answer a different question, and getting the boundaries correct is most of the battle.

Read article

Exam Room · Advanced Generative AI Developer

Picking an Embedding Model for Retrieval

An index with 20 million chunks, queries that have to work in English, Spanish, Portuguese and Japanese, and a team that cannot re-embed the corpus twice a year. The embedding model sets the ceiling on what a retrieval system can return. Titan, Cohere and a self-hosted model differ on language coverage, chunk size and how the backfill runs, and the documented differences are not the ones the marketing pages lead with.

Read article

Exam Room · Advanced Generative AI Developer

Making a Bedrock App Audit-Ready

A support assistant built on Bedrock has run cleanly for months, and now a compliance review has landed on it. The auditors want to know who invoked the model, what prompts and completions flowed through it, which model version answered, who approved the deployment, and proof that no customer PII leaked into the logs. The app works. It just can't answer a single one of those questions yet.

Read article

Exam Room · Advanced Generative AI Developer

Checking a Bedrock Feature for Bias and Explainability

A Bedrock-powered feature drafts summaries of job applicants and triages people-facing cases, so its outputs shape decisions about real people, and it is up for a responsible-AI review before launch. The team already knows how to stop the model saying toxic or off-topic things; now they are being asked to show the feature is fair across groups and that any given output can be explained and justified. Content safety was the easy part; 'is it fair, and can you explain it?' is a different set of jobs.

Read article

Exam Room · Advanced Generative AI Developer

How to Match Bedrock Pricing to Workload Rhythm

Standard on-demand Bedrock is priced per token and throttled per minute, and the throttling counts output tokens at several times their billed weight. Priority costs 75% more per token for faster handling, Flex takes 50% off for work that can wait, batch takes the same 50% off asynchronously, and the Reserved tier fixes tokens-per-minute at a monthly price. Which of those a model offers is set per model, and the right pick changes with the shape of the workload.

Read article

Exam Room · Advanced Generative AI Developer

Keeping PII Out of LLM Prompts and Logs

A claims assistant that has to answer questions about a customer's claim while keeping the customer's name, address, policy number, and medical details out of training data, out of logs, and out of anything a subpoena could touch later. PII redaction isn't one knob, it's four or five, in different places, each covering a different leak path. Comprehend, Bedrock Guardrails, custom redaction, and the prompt itself each handle a different shape of the problem.

Read article

Exam Room · Advanced Generative AI Developer

Evaluating a RAG Pipeline End to End

A citations-required assistant over internal documents answers most questions well and a few of them wrong, and the team cannot tell why. Was the right passage never retrieved, or was it retrieved and then ignored? Those are two different failures with two different fixes, and an evaluation that reports one score for the whole pipeline does not say which one you have. This walks through separating the retrieval half from the generation half so the regression harness points at the part that actually broke.

Read article

Exam Room · Advanced Generative AI Developer

Hybrid Search and Reranking for Bedrock RAG

A support assistant on Bedrock retrieves by pure semantic search and keeps whiffing on exact-term queries: product codes, error codes, part numbers, acronyms, proper names. The embedding of 'ERR-4021' sits close to a hundred other error codes, so a plausible-but-wrong chunk outranks the one document that actually names it. The fix is two levers, hybrid retrieval and a reranker, and knowing which one the precision problem actually needs.

Read article

Exam Room · Advanced Generative AI Developer

Prompt Engineering Techniques That Move the Needle

A dozen prompt-engineering tricks are supposed to improve output, but half of them cost tokens without moving quality and a couple widen a security hole. Zero-shot, few-shot, chain-of-thought, ReAct, schema prompting, system framing, and delimiters each work on a specific task shape and hurt on the wrong one. The job is matching the technique to the task rather than stacking all of them and hoping.

Read article

Exam Room · Advanced Generative AI Developer

Choosing a Model From the Bedrock Catalogue

The Bedrock catalogue lists models from more than a dozen providers across text, images, video, and embeddings, and the reflex is to reach for the biggest, cleverest one for everything. That reflex triples the bill and slows every call, because most workloads never needed the flagship. The job is matching the model class to the shape of the work, then picking the smallest model that clears the quality bar.

Read article

Exam Room · Advanced Generative AI Developer

Choosing an Inference Option for a GenAI Workload

A support assistant with a human waiting, a nightly re-scoring job, and an internal tool that wakes up once a day all need to serve a model, but they have nothing else in common. One needs low latency on steady traffic, one runs offline overnight on millions of records, and one spikes at odd hours and sits idle the rest of the time. Bedrock and SageMaker hosting each offer several ways to serve inference, and the right one falls out of the traffic shape and the cost model more than the model itself.

Read article

Exam Room · Advanced Generative AI Developer

Fine-Tuning, Continued Pre-Training, or Distillation

Prompting stopped closing the gap and retrieval only goes so far, so the model itself has to change. But the same word covers three training routes: fine-tuning on labelled pairs, continued pre-training on raw domain text, and distillation into a smaller student. They need different data, aim at different outcomes, run in different places, and differ enormously in what they cost to run and to serve.

Read article

Exam Room · Advanced Generative AI Developer

Managing Prompts With Bedrock Prompt Management

The prompt is the product, and yet it usually lives as a string literal glued together in application code, edited by whoever last touched the deploy, with no version and no way to roll back a bad wording change. Amazon Bedrock Prompt Management makes the prompt a Bedrock resource with input variables, an attached model and inference configuration, and numbered versions an application invokes by ARN. The decision is whether that managed store is a better home than a prompt kept in your own source control, and it turns on how many services share the wording, who edits it, and whether prompts feed Bedrock Flows.

Read article

Exam Room · Advanced Generative AI Developer

Prompt Caching Versus Response Caching on Bedrock

Two things called caching sit in front of a Bedrock app and they are not the same lever. Prompt caching still calls the model but you pay a fraction for a shared prefix; response caching may skip the model entirely and risks serving a stale or wrong-match answer. Knowing which repeated part you are actually paying for, the input prefix or the whole request, decides which one you reach for, and whether you stack both.

Read article

Exam Room · Advanced Generative AI Developer

Getting Documents Into a Bedrock Knowledge Base

A Bedrock Knowledge Base can only answer from what its ingestion pipeline put in the index. Documents pass through a data source, a parser, a chunker, and an embedding model before they reach the vector store, and each stage limits what the next one can do. The job is picking the data source, the parser, and the metadata that fit the documents you actually have.

Read article

Exam Room · Advanced Generative AI Developer

Choosing a Chunking Strategy for Bedrock Knowledge Bases

A mixed corpus is going into an Amazon Bedrock Knowledge Base: hundred-page PDFs, structured policy documents with numbered sections and tables, and a pile of short FAQ entries. Default chunking, roughly 300 tokens a chunk, retrieves badly because answers land across a chunk boundary or a single chunk sweeps up three unrelated ideas, and the team needs a chunking strategy that follows the shape of the documents rather than cutting across it.

Read article

Exam Room · Advanced Generative AI Developer

Which AWS Store Can Do Vector Search

A team already runs OpenSearch for logs, Aurora for the transactional data, DynamoDB for the session store, and a Mongo-compatible cluster for the catalogue. Now a knowledge base needs vector search. Nearly every one of those engines can answer a nearest-neighbour query once the right feature is switched on, so the useful question is which switch each one takes, which of them a Bedrock Knowledge Base can drive for you, and where each query surface runs out.

Read article

Exam Room · Advanced Generative AI Developer

Picking the Right Tool to Check and Govern GenAI Data

Every night a knowledge base pulls in support tickets, product docs, and a database export, and every night some fraction of that arrives malformed, half-empty, duplicated, or carrying customer PII into a place it should never reach. The model is only as trustworthy as the corpus behind it, so the pipeline needs a gate: something that ingests the raw data, checks it against rules, and governs who can see what before any of it reaches an embedding. AWS offers at least five tools that each cover a piece of that job, and they are easy to mix up.

Read article

Exam Room · Advanced Generative AI Developer

Retrieval Over Structured Data With Text-to-SQL

A finance team wants natural-language answers to questions like total revenue by region last quarter, and the obvious move is to embed every row and reach for vector search. It falls apart the moment the answer is a sum instead of a sentence. The right pattern turns the question into SQL, runs it against a known schema, and returns the computed result. This walks the axes that decide when retrieval belongs in a query engine, not a vector index, and how to run generated SQL safely.

Read article

Exam Room · Advanced Generative AI Developer

Defending a Bedrock App Against Prompt Injection

A support assistant on Bedrock reads user questions, pulls answers from a knowledge base, and can raise refunds through a tool. Every one of those surfaces is a way in for an attacker who wants to override the instructions, jailbreak the guardrails, or turn the refund tool against the business. No single control stops all of it, so the real question is how the layers stack.

Read article

Exam Room · Advanced Generative AI Developer

Securing a Bedrock App: IAM, PrivateLink, and Keys

A production assistant on Amazon Bedrock has four separate ways to leak, and each one is a different control plane. Who is allowed to call the model, how the traffic reaches Bedrock, who holds the encryption keys, and where the data lives are four questions, not one. Getting one right does nothing for the other three; they are layers you stack, not options you pick between.

Read article

Exam Room · Advanced Generative AI Developer

Tuning Fine-Tuning: Epochs, Learning Rate, and Batch Size

A fine-tuning job on Amazon Bedrock exposes a short list of hyperparameters, and the two failure modes sit at opposite ends of the same dial. Too little training and the custom model still sounds like the base; too much and it reproduces the training examples and degrades on the work it used to handle. Epochs, learning rate and batch size are the knobs, and the training and validation loss curves are how you read whether you have turned them too far. The permitted ranges are tighter than most people expect, and the stopping point is read off the validation curve rather than predicted from a row count.

Read article

Exam Room · Advanced Generative AI Developer

Orchestrating Multiple Bedrock Agents

A support assistant that once answered one kind of question now has to look up billing, check delivery windows, raise a ticket, and draft a reply, and each of those needs different tools and different judgement. One agent can reason its way through all of it, a supervisor agent can farm the pieces out to specialists, and a Flow can run the whole thing as a fixed pipeline. The trade is flexibility against predictability, cost, and latency, and the right shape depends on whether the order of steps comes from the model at run time or from the designer ahead of time.

Read article

Exam Room · Advanced Generative AI Developer

Running Agents in Production With Bedrock AgentCore

A prototype agent built on an open-source framework works on a laptop, then has to become something real subscribers hit all day, with sessions that must not bleed into each other, memory that survives a reconnect, credentials that let it touch internal systems without over-granting, and traces you can read when a run goes wrong. Bedrock AgentCore is the set of building blocks for that operational layer, framework-agnostic and model-agnostic, so the decision is which pieces you actually need and where the managed line should sit. The trade is control against operational burden, and it turns on how much of the runtime, memory, identity, and observability you want to own yourself.

Read article

Exam Room · Advanced Generative AI Developer

Buy or Build: Amazon Quick Versus a Custom RAG App

An enterprise wants a chat assistant over its own documents, and the choice is Amazon Quick off the shelf or a retrieval app built on Bedrock Knowledge Bases. Quick connects to six common document stores, signs staff in through IAM Identity Center, and checks permissions per document. Bedrock Managed Knowledge Bases now do ACL-aware retrieval across the same sources, so the deciding question has shifted to who owns the sign-in, the front end, and the retrieval internals.

Read article

Exam Room · Advanced Generative AI Developer

When a Purpose-Built AI Service Beats a Foundation Model

Reaching for a foundation model on every AI task gets expensive fast, because much of what teams build is a well-defined single-purpose job that a managed AWS service already does faster, cheaper and the same way every time. Textract, Comprehend, Transcribe, Translate, Rekognition, Polly, Lex and Personalize each cover one task shape. The harder skill is spotting the pipelines where a purpose-built service feeds a foundation model rather than competing with it.

Read article

Exam Room · Advanced Generative AI Developer

Proving Where AI Content Came From

A generative feature raises four different questions at once: can you prove an output came from your model, can a reader see what the service is and is not meant to do, can you stop bad behaviour as it happens, and can you show how the model was built and evaluated. Each one has a different AWS control, and reaching for the wrong one leaves the real question unanswered. The job is matching the responsibility to the artefact that actually discharges it.

Read article

Exam Room · Advanced Generative AI Developer

Where Humans Belong in a GenAI Pipeline

A generative-AI system needs human judgement in three different places, and it is easy to muddle them because all three sound like putting a person in the loop. Labelling training data, reviewing live predictions, and judging model quality are separate jobs with separate shapes, and with AWS's managed labelling and review services now in maintenance, two of them are loops a new build assembles itself. Getting the placement right keeps people on the decisions only people can make and keeps them off the ones a threshold or a metric already handles.

Read article

Exam Room · Advanced Generative AI Developer

Searching Images and Text With Multimodal Embeddings

Searching a product catalogue by typing a description, or by dropping in a lookalike photo, sounds like a job for a vision model, but a chat model that reads an image reasons about it rather than retrieving against a library. The tool that powers cross-modal search is a multimodal embedding model, which places images and text in one shared vector space so nearest-neighbour finds matches whichever modality the query arrived in. Getting it right means separating retrieval from reasoning, and keeping the distance metric matched to the model.

Read article

Exam Room · Advanced Generative AI Developer

Tuning How a Model Samples: Temperature, Top-P, and Top-K

Temperature, top-p, and top-k all change how a model picks its next token, and reaching for the wrong one turns a crisp classifier into a coin flip or a brainstorm into a monotone. Each parameter acts on the distribution in a different place, they interact in ways that surprise people who turn all three dials at once, and the right setting is a property of the task rather than a house style. The job is knowing which knob does what and leaving the rest alone.

Read article

Exam Room · Advanced Generative AI Developer

Budgeting Tokens for a Long-Document Workload

A workload that reads long documents keeps hitting the context window and the bill keeps climbing, and the instinct is to reach for the model with the biggest window and stuff whole files into it. That instinct is expensive, slower, and can lower answer quality with nothing in the response to show for it, as the relevant facts get buried. The real job is reasoning about tokens: what fits, what it costs on the way in and on the way out, and how to shrink the input without losing the part that matters.

Read article

Exam Room · Advanced Generative AI Developer

SageMaker JumpStart or Bedrock for the Same Model

A team that wants Llama 3.3 70B in production can take it through SageMaker JumpStart, deploying onto an endpoint they own, or through Bedrock's model catalog with per-token pricing and no infrastructure. Same model, same base weights, two quite different operational shapes. The choice turns on how much of the serving layer you want to run.

Read article

Exam Room · Advanced Generative AI Developer

Making an LLM Output Reproducible

Two people run the same prompt through the same model and get two different answers, and now a compliance reviewer wants to know which one the system actually produced. Temperature zero helps, pinning the model version helps more, and only a cache in front of the model gives you byte-identical repeats. The real question is how much determinism the use case genuinely needs, and how much machinery each level takes.

Read article

Exam Room · Advanced Generative AI Developer

Why Your RAG Returns the Wrong Chunk

A retrieval system answers with confidence and cites the wrong passage, and the reasons are frustratingly varied: an index configured for something other than what the embedding model emits, chunks too big or too small, a query phrased nothing like the documents, an SKU that semantic search cannot match, a missing tenant filter, no reranking, or an index that never re-synced. This walks each symptom back to its cause and lands it on a fix.

Read article

Exam Room · Advanced Generative AI Developer

Metadata Filtering for Multi-Tenant Retrieval

One retrieval index serves every tenant, so the question that decides everything is whether a query can ever surface a document its asker was never meant to see. Metadata filters keyed on verified identity are the boundary; a prompt that asks the model to stay in its lane is not. This walks through attaching tenant and access metadata at ingestion, filtering at query time, and why pre-filtering beats filtering the results afterwards.

Read article

Exam Room · Advanced Generative AI Developer

Parent-Document Retrieval: Small Chunks, Big Context

The chunk size that retrieves precisely and the chunk size that gives the model enough context pull in opposite directions: small chunks embed cleanly and match the query but hand the model a fragment, while large chunks carry the surrounding context but blur the embedding and match worse. The fix is to stop treating them as one number and decouple the unit you search from the unit you return, which is what parent-document retrieval, hierarchical chunking, and sentence-window retrieval each do.

Read article

Exam Room · Advanced Generative AI Developer

Agentic RAG: When Retrieval Needs to Reason

A support assistant that answered one kind of question from one knowledge base now gets questions that need two lookups, a reformulated search, and a second retrieval once the first one comes back thin. Plain RAG runs a fixed pipeline: embed the query, fetch the top matches once, generate. Agentic RAG moves the retrieval decisions to the model, which can skip the search, pick the source, rewrite the query, and go back for more. The first is cheap and predictable; the second is right when one pass genuinely cannot get there, and wasted model calls when it can.

Read article

Exam Room · Advanced Generative AI Developer

Designing Safe Tool Schemas for an AgentCore Gateway

A gateway turns your Lambda functions and REST APIs into tools a foundation model can call directly, and every tool you publish is a capability you are granting. The arguments arrive already shaped by a model that can be steered by whatever text reached the prompt, so a tool that takes a free-form instruction lets one coaxed call reach much further than you meant. How much the schema can rule out varies with how the tool is attached, the caller's identity does not travel with the call unless you arrange it, and the confirmation gate is code you own rather than a flag you set.

Read article

Exam Room · Advanced Generative AI Developer

Surviving a Model Deprecation on Bedrock

A foundation model you pinned two quarters ago will not live forever. Bedrock marks a version Legacy, sets an end-of-life date, and then removes it from every Region. Pinning holds behaviour steady and puts the migration on someone else's calendar. Floating to the newest version swaps that for silent drift. The way through is rehearsed: pin, watch the notices, score the successor against a saved eval set, and cut over behind a flag with a rollback still reachable.

Read article

Exam Room · Advanced Generative AI Developer

Measuring Hallucination in a RAG System

A retrieval-augmented assistant that answers confidently and wrong is failing in one of two very different places, and the fix depends on which. A hallucination can come from retrieval, where the context never held the answer, or from generation, where the model ran past what the context said, and a single quality number hides both. Measuring it well means separating faithfulness to the retrieved passages from whether the answer is even the right one, then attributing each miss to the stage that caused it.

Read article

Exam Room · Advanced Generative AI Developer

Choosing an Embedding Model for a Multilingual Corpus

A support knowledge base written in English, French and Japanese needs semantic search, and running an English-optimised embedding model over the lot fails without raising an error: a French question never finds the English answer that solves it. Cross-lingual retrieval needs a model trained to put every language into one shared vector space, and on Bedrock that list is shorter than a "supports 100+ languages" line implies. The choice turns on documented alignment, input limit, and embedding dimension.

Read article

Exam Room · Advanced Generative AI Developer

LLM-as-a-Judge: Designing a Rubric You Can Trust

Handing evaluation to a second model is fast and it scales, but a judge with a vague rubric scores on its own priors and returns a number you then trust anyway. Pointwise scoring against explicit criteria and pairwise comparison answer different questions, and both carry position, verbosity and self-preference bias unless you design against them. The work is writing a concrete rubric, controlling the known biases, and calibrating the judge against human labels before you let it grade at scale.

Read article

Exam Room · Advanced Generative AI Developer

Monitoring a Production Bedrock App

A generative-AI feature on Amazon Bedrock breaks in three directions: the bill climbs, the responses slow down, and the answers get worse without anyone noticing. Bedrock publishes metrics for the first two, and a grounding check that catches part of the third. The rest of quality is a scoring pass you build on top of the logs.

Read article

Exam Room · Advanced Generative AI Developer

Building Deterministic Pipelines With Bedrock Flows

When a generative workflow has a sequence you already know, letting the model produce the order at run time is the wrong trade: nondeterministic, harder to test, and an extra model call at every decision point. Amazon Bedrock Flows lets you draw the sequence as a fixed graph of nodes wired together with data links, so a designer owns the control flow and the model does the work inside a step. This walks the space between a Flow, a model-driven agent, and Step Functions, and lands on when the drawn graph is the right home.

Read article

Exam Room · Advanced Generative AI Developer

Encrypting a Bedrock App End to End With KMS

Everything a Bedrock app stores is encrypted at rest by default, so what matters is not whether the data is encrypted but who holds the key that decrypts it. Bedrock's own defaults are AWS owned keys, which you cannot view, police or audit. A customer-managed KMS key gives you the key policy, a CloudTrail record of every use, and a way to cut access without deleting a byte. This walks the persistent artefacts one by one and asks, for each, whose key it is.

Read article

Exam Room · Advanced Generative AI Developer

Event-Driven GenAI: Processing Documents Asynchronously

Summarising a 200-page report or enriching a batch of records is a job that takes minutes, so wiring it behind a synchronous HTTP request guarantees timeouts, retries that re-run expensive work, and a bill that scales with impatience. The fix is to make the upload an event and let the work happen in the background. S3 notifications, SQS buffering, Lambda workers, Step Functions pipelines, and Bedrock batch inference each fit a different point on the volume-and-latency curve, and picking the wrong one shows up as either idle capacity or dropped documents.

Read article

Exam Room · Advanced Generative AI Developer

Caching LLM Responses Without Stale Answers

Thirty percent of the support assistant's queries are paraphrases of each other, 'how do I cancel?' 'can I cancel?' 'where's the cancel button?', and every one costs full model price. Caching LLM responses isn't as simple as hashing a prompt: exact-match, semantic, and prefix caching answer different questions, and getting the boundary wrong serves yesterday's answer to today's question.

Read article

Exam Room · Advanced Generative AI Developer

A/B Testing Prompts and Models in Production

A new prompt scores better on the test set, a newer model is cheaper per token, and both look like obvious upgrades until they meet real traffic and regress a slice of it without anyone noticing. Offline scores tell you a variant is plausible; only live traffic tells you it is better. The job is deciding how much risk each change deserves, shadowing or splitting accordingly, measuring quality and latency and cost together, and rolling the winner out in a way you can undo without a deploy.

Read article

Exam Room · Advanced Generative AI Developer

Right-Sizing Provisioned Throughput for a Custom Model

Fine-tune Llama 3.1 8B on Amazon Bedrock and there is no on-demand path for the result: Provisioned Throughput is the only way to serve it, purchased in model units you are billed for hourly whether traffic fills them or not. Size the unit count from peak tokens per minute with headroom, then choose a commitment term, because the six-month rate is the lowest per unit and the reservation cannot be resized or deleted inside the term. Over-provision and idle units bill around the clock; under-provision and the mid-morning peak throttles real requests.

Read article

Exam Room · Advanced Generative AI Developer

Defending Against Indirect Prompt Injection in RAG

A retrieval-augmented assistant answers from a knowledge base you built over your own documents, so the retrieved context feels trusted. It is not. The moment a document can be edited by a partner, crawled from the web, or fed in from user-generated content, an attacker can plant instructions that ride into the model alongside the genuine text, and nothing in the assembled prompt marks that sentence as data rather than a command.

Read article

Exam Room · Advanced Generative AI Developer

Cost Attribution and Tagging for GenAI Workloads

A single Bedrock bill arrives as one on-demand line, and the finance team wants to know which team, feature, and customer spent it. Application inference profiles, IAM principal attribution, cost allocation tags, request metadata in the invocation logs, Cost Explorer, and Budgets each pin the spend at a different grain, from whole account down to a single request. The job is choosing the grain that answers the chargeback question, then wiring the alert that closes the loop before the next bill lands.

Read article

Exam Room · Advanced Generative AI Developer

Building a Voice Assistant: Transcribe, Bedrock, and Polly

A voice assistant is four pieces bolted together: speech becomes text, a model reasons over the text, the reply becomes speech, and something manages the back-and-forth. Pick each piece in isolation and you find out at integration time that the latency has stacked up past what a caller will tolerate, or that a spoken card number has landed in a model prompt the compliance rules say it should never have reached. The fix is a latency budget across the whole chain, and safety on the text stage, where the words actually live.

Read article

Exam Room · Advanced Generative AI Developer

Handling Throttling and Rate Limits Gracefully

A Bedrock feature that ran clean in testing starts returning ThrottlingException the week traffic doubles, and the temptation is to bolt on a retry loop and move on. Retries smooth a transient spike, but they add no capacity, so a genuinely undersized workload just retries its way into a slower failure. The real work is telling a transient limit from a structural one, then reaching for backoff, a quota increase, cross-Region inference, a capacity reservation, or a queue depending on which one the traffic actually needs.

Read article

Exam Room · Advanced Generative AI Developer

Cutting Ingestion Cost by Caching and Batching Embeddings

A retrieval system re-embeds its whole corpus on every update, and the bill scales with a knowledge base that barely changes. Embedding is a per-token cost paid on every chunk you send, so re-embedding text that has not changed is money spent to arrive at the vector you already had. Incremental sync, content-hash caching, de-duplication, request batching, and a smaller embedding dimension each cut a different slice of that waste, and each adds bookkeeping worth naming before you reach for it.

Read article

Exam Room · Advanced Generative AI Developer

Choosing Between Kiro, Amazon Quick, and Bedrock

AWS sells finished AI assistants and it sells the platform to build your own, and most bad decisions in this corner come from confusing the two. Kiro is the assistant developers adopt; Amazon Quick is the assistant staff use over enterprise data; Bedrock is the platform a customer-facing feature gets built on. Sort by who the output is for and the choice mostly makes itself.

Read article

Exam Room · Advanced Generative AI Developer

Keeping a Knowledge Base Fresh Without Re-Embedding Everything

A retrieval assistant is only as good as the documents behind it, and those documents keep changing while the embedding bill for re-processing them keeps climbing. A support team on Amazon Bedrock has a knowledge base over forty thousand policy and product files, and their nightly full re-sync costs more than the queries it serves. The fix is knowing what actually needs re-embedding, when to trigger the work, and when retrieval is the wrong tool for the fact entirely.

Read article

Exam Room · Advanced Generative AI Developer

How to Wire Function Calling Through Bedrock

An assistant that can only answer questions is half a tool. Function calling lets the model emit a request to run a tool we declared, with arguments it fills in, and the caller runs it. Bedrock's Converse API has native tool-use support; so does Anthropic's Messages API through Bedrock; so does the AgentCore harness, which runs the loop for you. Each exposes function calling through a different surface, and picking wrong makes the simple case hard.

Read article

Exam Room · Advanced Generative AI Developer

When to Orchestrate With Step Functions Instead of an Agent

A multi-step GenAI job can be run three ways: a Bedrock agent that lets the model decide the sequence, a Bedrock Flow that draws the sequence as a fixed graph, or a Step Functions state machine that runs the sequence as a durable workflow with the model as one step among many. The deciding line is whether the control flow is known ahead of time and how much durability, retry, and cross-service reach the job needs. This walks the space and lands on when the state machine is the right home.

Read article

Exam Room · Advanced Generative AI Developer

Building a Golden Dataset for LLM Evaluation

Every prompt tweak, model swap, and RAG change gets judged against something, and if that something is a handful of screenshots in a chat thread, the judgement is noise. A golden dataset is the fixed yardstick: representative inputs paired with accepted answers, covering the easy middle, the known-hard cases, and the questions the system should refuse. Building one that stays trustworthy and reusable is the work that makes every later evaluation mean something.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Model Selection and Inference

A condensed revision sheet for choosing a model on Amazon Bedrock and picking how it runs: the provider catalogue, the Nova family, selection axes, and every inference mode from on-demand service tiers to Provisioned Throughput to SageMaker hosting.

Read article

Exam Room · Advanced Generative AI Developer

Red-Teaming a Bedrock Application

A team ships a generative-AI assistant on Bedrock and waits to see what breaks. Red-teaming flips that around: you attack your own application on purpose, before an outsider does, probing for jailbreaks, injected instructions, leaked data, and side-effecting tools reachable through crafted input. The work that lasts is not the single afternoon of creative attacks; it is turning every finding into a test that runs on every change.

Read article

Exam Room · Advanced Generative AI Developer

Content Moderation With Rekognition, Comprehend, and Guardrails

A single generative app now takes uploaded photos, voice notes, and free text, and it also emits model output that has to be safe to show. One moderation service cannot cover all of that, because the right tool is decided by the media and by the stage of the pipeline. Rekognition reads images and video, Comprehend reads text, Transcribe bridges audio into text, and Bedrock Guardrails sits on the model prompt and completion. The job is routing each piece of content to the service built for it rather than forcing one tool to do everything.

Read article

Exam Room · Advanced Generative AI Developer

Cost Guardrails: Budgets, Quotas, and Model Choice

A generative-AI feature can double its own bill between two invoices, and the first anyone hears of it is the invoice. Per-token pricing, model tier, replayed context, call volume, and Provisioned Throughput commitments are the dials that set the number, and every one of them can be bounded in advance. The job is to design the limits in up front, budgets and quotas and model choice together, so an overrun trips an alert on day two instead of arriving on the statement.

Read article

Exam Room · Advanced Generative AI Developer

Routing Requests Between a Cheap and a Capable Model

Most traffic to an LLM feature is easy: a label, a short extraction, a one-line answer that a small cheap model handles as well as the flagship. A minority needs the big model to reason through several steps. Paying flagship prices on every request treats the whole workload as if it were the hard tail, so the money and the latency go where they are not needed. Routing splits the stream, and the risk is a misroute that sends a hard request to the weak model and gets a confident wrong answer.

Read article

Exam Room · Advanced Generative AI Developer

Summarising Long Conversations to Fit the Context Window

A support copilot on Bedrock works fine for the first dozen turns, then the transcript it replays on every call grows until the bill climbs and the oldest messages fall off the edge of the context window. Replaying every turn is the simple thing, and it is the thing that breaks first. Sliding windows, running summaries, and extracted facts each trade history for room in a different way, and the split between a recent transcript and a durable store is the line between short-term and long-term memory.

Read article

Exam Room · Advanced Generative AI Developer

Choosing an Embedding Dimension and Its Storage Cost

Embedding dimension looks like a knob where higher is simply better, but every extra dimension multiplies across every vector in the index, and storage plus search cost climb in lockstep. Amazon Titan Text Embeddings v2 lets you ask for 1024, 512, or 256 dimensions, so the choice is a real trade of retrieval quality against footprint and latency. The job is to size the corpus, set a quality bar, and measure what each dimension is actually worth on your own data.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Prompt Engineering

A condensed revision sheet for prompt engineering on Bedrock: techniques, decision rules, traps, and one-line facts for the AIP-C01 Generative AI Developer track.

Read article

Exam Room · Advanced Generative AI Developer

Tracing an Agent's Decisions in Production

An agent told a subscriber they were owed the wrong refund, and the final answer says nothing about why. To debug it you have to reconstruct the run: which tool it called, with what arguments, what came back, and how it reasoned from one step to the next. AgentCore emits metrics for that out of the box but not the spans, model invocation logging captures the prompts and completions, and distributed tracing ties the tool Lambdas into one picture. None of it is retroactive, which makes the setup a decision you make before the run you will need it for.

Read article

Exam Room · Advanced Generative AI Developer

Multi-Region Resilience for a GenAI Service

A Bedrock assistant runs fine until on-demand throttling bites at peak, or until its Region has a bad hour. Cross-Region inference profiles raise the throughput ceiling, but the geographic and global variants differ on exactly the residency rule that matters, and a warm second Region only works if the guardrail, prompts and knowledge base are already rebuilt there. The decision comes down to the recovery objectives, where the data may be processed, and what a second Region costs to keep warm.

Read article

Exam Room · Advanced Generative AI Developer

Delivering Responses: Sync, Async, or Streaming

Every generative feature needs a way to get the answer to the user: one synchronous reply, a stream of tokens as they are generated, or an asynchronous job that finishes in the background. The wrong choice shows up as a spinner that stalls for thirty seconds, a gateway timeout on a long completion, or a batch of ten thousand documents jammed through a real-time endpoint one at a time. The deciding factors are how interactive the moment is, how long the output runs, and how long the caller can wait.

Read article

Exam Room · Advanced Generative AI Developer

Preparing a Dataset for Fine-Tuning

Fine-tuning a foundation model lives or dies on the data you feed it, and most teams reach for volume when they should be reaching for consistency. A few thousand clean, representative, identically formatted examples will out-teach a scraped heap of forty thousand, and Bedrock caps most fine-tuning jobs at ten thousand records anyway. The work is shaping that set: the JSONL schema the model expects, a train and validation split with no leakage, PII and duplicates stripped, and a held-out set to judge the result. Get the data right and the job is almost a formality.

Read article

Exam Room · Advanced Generative AI Developer

Finding the Documents That Never Reached the Knowledge Base

A Knowledge Base sync reports success and the assistant still cannot answer a question whose answer is sitting in one of the source buckets. The job-level view says forty thousand documents scanned and reports no failure at all, because a document that was skipped, ignored, or failed to embed leaves no trace at that altitude. Ingestion observability is a separate feature from the invocation logging most teams have already turned on, and it is the one that names the file and the reason.

Read article

Exam Room · Advanced Generative AI Developer

Building Permission-Safe Retrieval on a Bedrock Knowledge Base

For years the easy answer for a permission-sensitive corpus was Amazon Kendra, which crawled document ACLs alongside document content. Kendra closed to new customers on 30 July 2026. A Bedrock managed knowledge base now crawls those permissions too, on the connectors that have one, and filters retrieval against an identity the application supplies; where a source falls outside that list, enforcement goes back to metadata filters the team designs. This is what each path involves, and where the line between them falls.

Read article

Exam Room · Advanced Generative AI Developer

Extracting Structured Data From Documents at Scale

A pile of invoices, forms, and scanned contracts has to become clean database rows, and the tool choice decides everything downstream. Amazon Textract reads layout and text at a fixed per-page price; a foundation model on Bedrock extracts meaning but needs its output constrained and checked; Bedrock Data Automation runs the whole pipeline against a blueprint; and the reliable pattern for most real documents combines them. The job is matching the tool to whether the work is reading pixels or reading meaning.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: RAG and Vector Stores

A condensed revision sheet for retrieval-augmented generation on AWS: how documents get chunked and embedded, where the vectors live, how retrieval and reranking are tuned, and which managed service does the plumbing for you.

Read article

Exam Room · Advanced Generative AI Developer

Choosing a Model for Code Generation

A team wants a code-generation feature: complete a function, explain a stack trace, translate a service between languages, review a diff. On AWS that splits into two very different projects, driving a general foundation model on Amazon Bedrock yourself, or adopting Kiro, the managed agentic development environment. The pick turns on whether you are building a feature or adopting a product, how closely the output has to match your own codebase, and how the generated code gets checked before anyone runs it.

Read article

Exam Room · Advanced Generative AI Developer

Building a Feedback Loop From Users to Model Improvement

A thumbs-down button is easy to add and easy to waste. The reactions users leave, explicit ratings and corrections plus the quieter signals of an edit, a retry, or an abandoned session, only matter if they flow somewhere that changes model behaviour. This scenario builds the loop from raw reaction to measured, validated improvement, and keeps the feedback data governed the whole way through.

Read article

Exam Room · Advanced Generative AI Developer

Open-Weight or Proprietary: Choosing How You Host a Model

A managed proprietary model on Amazon Bedrock is running in an afternoon and bills by the token. An open-weight model you host yourself gives you the weights, deep customisation, and a per-hour cost curve that only works out once traffic is steady. The choice is about control against managed simplicity, and about which cost curve fits the load. Bedrock, SageMaker AI, and Custom Model Import stake out the ground in between, so the pick turns on how much of the stack the team is prepared to own.

Read article

Exam Room · Advanced Generative AI Developer

How Many Chunks to Retrieve: Tuning Top-K

Amazon Bedrock Knowledge Bases returns up to five source chunks per query by default, and five is almost never the right number for a given corpus. Set top-k too low and the passage holding the answer never reaches the model, so the response is a refusal or an answer nothing retrieved supports. Set it too high and the input-token bill rises, latency rises, and the good chunk sits among distractors. The number that works depends on chunk size, corpus, and question shape, and the only way to find it is to measure on your own eval set.

Read article

Exam Room · Advanced Generative AI Developer

Grounding on Fresh Data: Tools or RAG

A model that answers from its own weights is answering from a frozen snapshot, so anything that has changed since training is a guess. Two grounding patterns fix that in different ways: retrieval pulls passages from an indexed corpus, and a live tool call fetches the exact current value at request time. They solve different problems, and the wrong one gives you a fluent answer built on stale data. The deciding questions are how fast the data moves, whether the answer is a passage or a precise number, and whether it is shared or per-user.

Read article

Exam Room · Advanced Generative AI Developer

Designing a Bot-to-Human Escalation Path

A generative assistant that never hands off will one day answer the single question it should have escalated, in the same even tone it uses for everything else, and that is where the real damage lands. The signals that a bot has hit its limit are knowable: low confidence, a guardrail intervention, an out-of-scope or high-stakes request, a frustrated customer, or an action beyond its authority. Each of those maps to a clean route out. The design job is deciding what the bot must never settle alone, then wiring the handoff so a human inherits the full context instead of a cold start.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Agents and Orchestration

A one-page revision sheet for agents, tool use, and orchestration on Bedrock: when the flow comes out of the model, when it comes out of your code, and which service owns each shape of workflow.

Read article

Exam Room · Advanced Generative AI Developer

Reducing End-to-End Latency in a GenAI App

A generative-AI feature that feels slow is rarely slow in one place; the seconds are spread across retrieval, the model, tool calls, and the network, and teams routinely tune the part that is easiest to see rather than the part that costs the most. The move that works is to measure each stage as p50 and p99, find the biggest contributor, and attack that one with the lever it responds to. Streaming, prompt caching, a smaller model, and parallel retrieval each help a different stage, so picking the wrong lever puts the work where the clock is not.

Read article

Exam Room · Advanced Generative AI Developer

Governing Model Access Across Many Teams

Fifty engineers across a dozen teams all want to build on Amazon Bedrock, and the platform team has to decide who can use which models, keep the whole organisation inside a shared policy, and still tell finance what each team actually spent. Foundation models are reachable by default, so governance starts from a deny rather than a switch. Scoping an IAM role, writing a service control policy, enforcing one guardrail from the organisation, and tagging an inference profile are four different levers, and they have to be pulled together.

Read article

Exam Room · Advanced Generative AI Developer

Versioning and Rolling Back Prompts and Models

A team ships a prompt tweak on Friday and by Monday quality has dropped, but nobody can say what changed because the prompt, the model reference, and the guardrail were all edited in place. The fix is to treat every piece of a generative feature as a versioned release artefact: a pinned model id, a numbered prompt version, a numbered guardrail version, a flow alias, all rolled out together and reversible together. Then a change is deliberate, a rollback is one repointed alias, and you always know exactly what moved.

Read article

Exam Room · Advanced Generative AI Developer

Choosing a Vector Index: HNSW, IVF, and the Trade-Offs

A retrieval feature slows to a crawl as the corpus grows, and the fix is almost never a bigger box; it is the index. Exact search returns perfect recall and slows in proportion to the corpus, HNSW answers fast at high recall from a graph that has to sit in RAM, and IVF gives up a little recall for a much faster build. The parameters that tune each one, m and ef_search and nprobe, all pull on the same three-way trade between recall, latency, and cost, and the only honest way to set them is to measure on your own data.

Read article

Exam Room · Advanced Generative AI Developer

Dense, Sparse, or Hybrid Retrieval

Dense embeddings capture what a query means; sparse keyword search catches the exact token a query names. Pick the wrong one and a RAG system either cannot find a paraphrase or cannot find a part number, and which failure you hit depends entirely on the shape of your corpus and the shape of your queries. Hybrid runs both and fuses the scores, which makes it the safe default for a mixed corpus, though it means running a second retriever and tuning a fusion step.

Read article

Exam Room · Advanced Generative AI Developer

Handling Ambiguous Questions With Clarification

A user asks a vague question and the model answers it as if it were perfectly clear, confidently and often wrongly. A bigger model does not fix that. The design has to test whether the request is answerable before it answers, then route to a clarifying question, a short list of likely readings, or a resolution drawn from account data and prior turns. Over-asking annoys, over-assuming misleads, and the balance moves with how much damage a wrong answer does.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Model Customisation

A revision sheet for customising a foundation model on Bedrock and SageMaker: the escalation ladder from prompting to fine-tuning to continued pre-training, dataset prep, hyperparameters, and how the custom model actually gets served.

Read article

Exam Room · Advanced Generative AI Developer

Preventing Data Exfiltration Through an LLM

A generative-AI assistant sits on top of an internal knowledge base and a set of tools, and every one of those connections is a way for data to leave. Retrieval can surface a document the user should never see; a tool can return more rows than the user is entitled to; the model can repeat a secret someone put in its context. The uncomfortable part is that you cannot fix any of it by telling the model to keep quiet, because access control belongs in retrieval and tools, not in the prompt.

Read article

Exam Room · Advanced Generative AI Developer

Deciding Whether to Use GenAI at All

A generative model is the most flexible tool in the box, and the least predictable and hardest to validate, billed per token rather than at a published rate per unit. Plenty of tasks that get handed to an LLM are better served by a rule, a lookup, a classic classifier, or a purpose-built AWS service that is cheaper, faster, and deterministic. The job is matching the tool to the task rather than defaulting to a model because it is the exciting one.

Read article

Exam Room · Advanced Generative AI Developer

Choosing Where to Store Conversation State

A chat assistant makes stateless model calls, so the transcript and session data have to live somewhere between turns, and the somewhere decides latency, cost, and how much of the assistant you end up building yourself. DynamoDB, ElastiCache, MemoryDB, and AgentCore Memory each fit a different mix of durability, turn rate, and how much of it you run yourself. The job is matching the store to the conversation shape rather than reaching for the one you used last time.

Read article

Exam Room · Advanced Generative AI Developer

Choosing a Distance Metric for Embeddings

A retrieval system can look completely healthy, index built, queries fast, no errors in the logs, and still return the wrong neighbours because the distance metric does not match what the embedding model produces. Cosine, dot product, and Euclidean each measure closeness differently, and a vector index is created with exactly one of them. The job is matching that choice to the model that generated the vectors, because the wrong metric degrades recall without raising an alarm.

Read article

Exam Room · Advanced Generative AI Developer

Cutting Cost per Query in a RAG System

A retrieval-augmented query looks cheap until the monthly bill arrives, and most of the money sits in a place nobody profiles: the retrieved context, which rides along as input tokens on every single call. Cutting cost per query is less about a cheaper model and more about returning fewer and better chunks, caching what repeats, and sizing the vector store to real traffic. This walks the money through one RAG query and trims each part in turn.

Read article

Exam Room · Advanced Generative AI Developer

Writing a System Prompt for a Production Assistant

A production assistant needs standing instructions that hold steady while every request changes underneath them, and the system prompt is where they live. It sets the role, the tone, the refusals, the output shape, and the rules for using retrieved context. What it cannot do is survive a request carrying contrary instructions, so the design work is deciding which jobs belong in the prompt and which need Guardrails, least-privilege tools, and delimiters behind it.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Evaluation, Cost, and Operations

A condensed revision sheet for running a generative AI app on AWS: how to evaluate quality, watch it in production, keep the bill sane, hold latency down, and ship without breaking things.

Read article

Exam Room · Advanced Generative AI Developer

Choosing a Guardrail Strategy: Managed, Custom, or Both

A generative-AI app needs safety controls, and the instinct is to reach for one tool and call it done. Amazon Bedrock Guardrails covers a lot out of the box: denied topics, content filters, PII redaction, grounding checks, prompt-attack detection. But some of the rules a business actually cares about are bespoke, and the managed policies only reach part of them. The real design decision is which risks belong to the managed layer, which need custom code, and how the two stack.

Read article

Exam Room · Advanced Generative AI Developer

Taking a GenAI Feature From Proof of Concept to Production

A demo that works in a notebook is not a feature that survives production. The gap is a set of dimensions a proof of concept gets to skip: evaluation, safety, security, reliability, cost, observability, governance, and operations. A demo proves the feature is feasible; production proves it is safe, affordable, reliable, and measurable, and closing that gap is a checklist, not a rewrite.

Read article

Exam Room · Advanced Generative AI Developer

Chunking Code, Tables, and Mixed Content

Chunking by token count is fine for prose and ruinous for everything else. It splits a function halfway through its body, tears a table away from its header row, and floats a figure loose from the caption that explains it. Every one of those breaks lowers the odds the right passage ever comes back from retrieval. The fix is to cut on the structure the content already has, rather than on a token count taken over flattened text.

Read article

Exam Room · Advanced Generative AI Developer

Generating and Understanding Images, Audio, and Video on Bedrock

Non-text work on Bedrock splits into two jobs that keep getting filed as one: making pixels and audio with a foundation model, and pulling structure out of media somebody else made. The generation half is in trouble. Every model in the catalogue that makes a still or a clip from a prompt is marked Legacy, and Nova Canvas and Nova Reel both reach end of life on 30 September 2026. Understanding is in far better shape, through Bedrock Data Automation, the purpose-built services, or a multimodal model reading the file in a prompt. This walks the split, then routes by modality and by the shape you need out.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Security and Responsible AI

A final-review sheet for securing and governing generative AI on AWS: identity, network, encryption, data boundary, Bedrock Guardrails, injection defence, and the responsible-AI dimensions, condensed to what you need on the morning.

Read article

Exam Room · Advanced Generative AI Developer

How to Pay for Serving a Model on Bedrock

Three models are heading for production: a hosted foundation model, a fine-tune halfway through training, and a set of open weights from a research spike. Finance wants one forecast. Each bills on a different unit, and for two of them the unit was settled the moment somebody picked a base model. Serving cost is less a lever you pull afterwards than a constraint you inherit from where the weights came from.

Read article

Exam Room · Advanced Generative AI Developer

Choosing an Agent Framework for the AgentCore Runtime

Deciding to own the reasoning loop settles where the agent runs and leaves open what you write it in. AgentCore takes any framework, so the choice is not about compatibility; it is about how much of the runtime each one already implements, whether the traces arrive without you building them, and what happens when one agent becomes four. Frameworks that already emit OpenTelemetry with the GenAI conventions make observability a dependency rather than a project, and that separates the field more than the loop syntax does.

Read article

Exam Room · Advanced Generative AI Developer

Giving an Agent Credentials Without a Standing Key

An agent that reaches real systems needs credentials, and the quickest way to give it some is the one that ages worst: a long-lived key in the environment that every request shares. The alternative splits into two questions that get conflated. Establishing who is asking is inbound authorisation and happens before your code runs; obtaining something to call a downstream service with is outbound, and which flow you can use depends on whether the call is machine-to-machine, delegated by a user, or exchanged from a token you were already handed.

Read article

Exam Room · Advanced Generative AI Developer

Picking an Evaluation Metric From the Cost of Being Wrong

A support assistant reports 97% accuracy every week while one of its two classifiers keeps approving fraudulent refunds. Both flag rare events, both look healthy on a single quality number, and the expensive error runs in opposite directions: silencing a real customer on one, paying out fraud on the other. Choosing a metric starts by naming the positive class and the error that costs, then reading the answer off the four cells of a confusion matrix rather than off the wording of the problem.

Read article

Exam Room · Advanced Generative AI Developer

Reviewing a GenAI Workload Against the Generative AI Lens

Two weeks before a subscriber-facing assistant goes live, the platform group asks for a written architecture review. A general one will find real problems and still never ask whether the model was chosen against an evaluation set, whether retrieved text can carry instructions, or what happens when the model version is retired. Those questions come from a lens, and the lens has somewhere to put the answers.

Read article

Exam Room · Advanced Generative AI Developer

Switching Foundation Models Without Shipping Code

Eight services call Amazon Bedrock and every one of them has the model id compiled into it. A cheaper model lands, and moving to it takes eight pull requests, eight reviews and eight release trains. The values that change fastest are trapped in the artefact that changes slowest, and getting them out is a design decision with more options than it first looks.

Read article

Exam Room · Advanced Generative AI Developer

Promoting a Fine-Tuned Model into Production

The training job finished and the eval numbers beat the base model. That was the easy half. The artefact now has to serve real traffic, stay identifiable two years later, and come back out inside ten minutes when it misbehaves, and the four places a customised model can live answer those three demands very differently.

Read article

Exam Room · Advanced Generative AI Developer

One Vector Index or Many

Forty million chunks, six business domains, eleven tenants, one OpenSearch index, and a p99 that has drifted past the budget. Splitting the index is the obvious move, and it is a memory decision, a rebuild-blast-radius decision and a tenancy decision at the same time. Index topology decides more here than another round of graph-parameter tuning.

Read article

Exam Room · Advanced Generative AI Developer

Building a Deployment Pipeline for a GenAI Feature

A generative feature is not one deployable binary. It is a prompt version, a guardrail version, an agent alias, a knowledge base sync and an inference profile ARN, and they have to promote together or a rollback returns half a release. Building the pipeline means deciding what a release is, then finding a gate that can fail on a score instead of an assertion.

Read article

Exam Room · Advanced Generative AI Developer

Putting a GenAI Gateway in Front of Bedrock

Eleven services call Amazon Bedrock directly, and the platform team can answer none of the questions it keeps being asked: who spent what, who is about to exhaust the account quota, and which callers skipped the guardrail. Routing every request through platform-owned compute answers all three. It also adds a hop of latency, a new tier-one dependency, and the loss of the caller identity that used to arrive at Bedrock intact.

Read article

Exam Room · Advanced Generative AI Developer

Choosing Where an MCP Server Runs

Three tools to publish to one agent, all speaking the same protocol: a subscriber lookup that reads a single row, an analytics query that answers out of a 400MB index it holds in memory, and a route optimiser that shells out to a licensed binary. MCP settles how the agent calls them and says nothing about where any of them runs. What each server keeps between calls decides that.

Read article

Exam Room · Advanced Generative AI Developer

Putting Brakes on an Autonomous Agent

An invoice-reconciliation agent looped forty times against a supplier API that was returning 500s, spent a night's token budget getting nowhere, and did it under a tool role that could read every object in the bucket. None of that is a model failure. It is a loop whose length nobody decided, running with permissions nobody scoped, and the fix is a set of bounds enforced outside the model, by code that counts.

Read article

Exam Room · Advanced Generative AI Developer

Wiring a GenAI Assistant Into Systems You Cannot Change

The order system is fifteen years old, speaks SOAP, falls over above a handful of requests a second, and goes dark for three hours every night. Nobody is allowed to change it. The assistant still has to answer questions about what is in it, which makes the design question how the data gets across the gap rather than what the model does with it once it arrives.

Read article

Exam Room · Advanced Generative AI Developer

Serving a GenAI Feature When the Data Cannot Leave

A regulator says the plant's maintenance records never leave the site, and a technician on the factory floor wants an answer before their thumb comes off the button. Neither requirement moves. The design job is to work out which bytes are actually pinned, which milliseconds are actually felt, and what is left over that can safely be sent to a foundation model in a Region.

Read article

Exam Room · Advanced Generative AI Developer

Detecting Misuse of a Public GenAI Assistant

The assistant has logging. What it does not have is detection, or any answer to what happens automatically once a pattern turns up. Three identities are already misbehaving in three different ways, and each one shows up in a different control. Choosing where the signal comes from is half the work; choosing how far the automated response may go is the half that gets skipped.

Read article

Exam Room · Advanced Generative AI Developer

Deleting a Subscriber's Data From a RAG System

One subscriber asks to be deleted, and the record turns out to sit in nine places at once: source documents, a vector index, conversation state, two sets of logs, a response cache, an evaluation set, a tuning dataset, and the weights of the model currently answering traffic. Three strategies cover that ground, and which one you can use was decided long before the request arrived.

Read article

Exam Room · Advanced Generative AI Developer

Keeping a Vector Store Healthy in Production

Retrieval p99 has tripled in three months, the answers have got worse, and the store has not logged a single error the whole time. Three different failures produce that same symptom: the collection is saturated, the index no longer fits the corpus it was built for, or the data in it is wrong. They need three different remedies, and the wrong one uses up a maintenance window and leaves the latency where it was.

Read article

Exam Room · Advanced Generative AI Developer

Auto-Scaling a Model Endpoint for Bursty GenAI Traffic

An internal assistant runs an open-weight model on a SageMaker real-time endpoint, and every weekday brings the same shape: a wall of traffic between 08:15 and 09:30, then near-silence until the next morning. Scale-out lands ten minutes after the burst starts, so the fleet has been pinned at peak size around the clock to hide the lag. Getting that money back means scaling on a signal that tracks what the accelerators are actually holding, and giving the burst somewhere to wait while capacity arrives.

Read article

Exam Room · Advanced Generative AI Developer

Dashboards for a GenAI Feature: Operations, Quality, and Business

Three people ask for a dashboard for the same generative-AI assistant in the same week, and they mean three different things. The on-call engineer wants a number that moves in seconds and can raise an alarm. The product owner wants yesterday's figures joined to the bill. The compliance reviewer wants a record they can query, and a chart will not do. One screen serving all three is how a team ends up with a screen nobody watches.

Read article

Exam Room · Advanced Generative AI Developer

Evaluating an Agent's Run, Not Just Its Answer

A refund agent gets the number right about four times in five, and nobody can say what happened in the other one. Answer-correctness scores a string. An agent produces a trajectory: a sequence of tool choices, arguments, results and retries, any step of which can be the thing that broke. Scoring the run instead of the reply is what turns "it fails sometimes" into a defect you can name.

Read article

Exam Room · Advanced Generative AI Developer

Turning a Golden-Set Score Into a Deployment Gate

A team has 400 golden examples, a working Bedrock evaluation job, and a habit of merging prompt changes because whoever wrote them read a dozen answers and liked what they saw. The last two regressions were found by customers. Turning that score into something that can stop a release means deciding what runs where, what a failure costs, and what happens when the number lands close to the line.

Read article

Exam Room · Advanced Generative AI Developer

Catching a Regression After the Deploy, Not From the Complaints

Latency was flat, the error rate was zero, and the bill had not moved. The answers had still got worse, and nobody noticed for three days. Deployment validation for a generative feature has to assert on the content of an answer, on a schedule, against production, because the changes that ruin quality often arrive without a deploy at all.

Read article

Exam Room · Advanced Generative AI Developer

Which Bedrock Errors to Retry and Which to Surface

A Bedrock feature fails about two percent of its calls, the application log says 'model call failed' and nothing else, and every invocation is wrapped in a retry-three-times loop. Amazon Bedrock names every failure, and the name separates the ones worth retrying from the ones that will fail identically forever; a wrapper that treats them the same turns a permanent error into a slow permanent error and turns a quota ceiling into an outage the team caused itself.

Read article

Exam Room · Advanced Generative AI Developer

Finding Out Why a Prompt Stopped Behaving

A summariser that reliably returned JSON starts returning prose about one call in six, nobody has touched the template, and the console reproduces the good behaviour every single time. The template is only part of the prompt. The rest is variables, retrieved passages and conversation history, assembled at request time and written down nowhere. Until those bytes are recorded there is nothing to debug.

Read article

Exam Room · Advanced Generative AI Developer

Getting Evaluation Results in Front of the People Who Decide

Three model comparisons in a quarter, each one answered in a chat thread with a pasted table, and the person paying for the work still cannot say which model the feature runs on. Results that live in the team's scrollback have been produced but never delivered. Where they should land depends on who is reading them and what that person is about to decide.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Integration and Deployment

A revision sheet for the half of Domain 2 that is not agents: where a model actually runs, how the answer reaches the caller, how a generative feature bolts onto systems nobody will rewrite for it, and what keeps the whole thing standing once the quota runs out.

Read article

Exam Room · Advanced Generative AI Developer

Cheat Sheet: Evaluation Metrics

A condensed revision sheet for every evaluation metric across a generative AI system: classification, ranking, regression, and text metrics, sorted by the output shape they score and the question that picks one over another.

Read article

Exam Room · Advanced Generative AI Developer

Deciding Which GenAI Security Controls Are Yours to Own

Four generative-AI uses inside one retailer, and every security conversation about them stalls on the same question: which controls do we run, and which are we trusting somebody else to run? That answer is not a property of the vendor or the service tier. It follows from how much of the stack you built, which is what the Generative AI Security Scoping Matrix is for.

Read article

Exam Room · Advanced Generative AI Developer

The Demo That Had to Justify Itself

A developer spent a week wiring a demo that reads a mine-site callout and proposes the parts to load on the truck. Thirty inputs, twenty-seven that looked right, one impressed executive, and a funding proposal for AUD$310,000. What the demo has not produced is a number anyone could have failed, a sample nobody chose, or a measured token cost. Turning it into a defensible go or no-go is a week of different work.

Read article

Exam Room · Advanced Generative AI Developer

Getting a GenAI Feature to the People Who Use It

One Bedrock-backed summariser, two teams, two different asks. One needs a chat interface in front of depot staff inside a fortnight and has no backend capacity. The other needs the request and response contract settled before either side writes a handler, because the engineers building against it work for another company. AWS Amplify answers the first and an OpenAPI document answers the second, and using either one for both jobs is how a fortnight becomes a quarter.

Read article

Flash cards

One subject a card: the five things that matter, when to pick it over the alternative, and why it is the wrong answer when it is.

Pop quizzes

Exam-style multiple choice, one question a card, with the reasoning behind the tempting wrong answer.

Exam Room · Advanced Generative AI Developer

Pop Quiz: OpenSearch Serverless's Hidden Floor

A Bedrock Knowledge Base needs a vector store, and on OpenSearch Serverless the idle bill depends on which collection generation you land on.

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: When Aurora pgvector Wins

When is Aurora PostgreSQL with pgvector the better vector store for RAG?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: The Silent Distance-Metric Bug

Retrieval quality collapses after an embedding model swap, and nothing errors anywhere. What config is worth checking first?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: S3 Vectors and the Latency Budget

You have a huge, rarely-queried vector archive and a wait of a second or two is acceptable. Cheapest fit?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Why Hybrid Search Finds ERR-4021

Semantic search keeps missing exact tokens like an error code. What retrieval change fixes it?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: What a Reranker Actually Fixes

The right chunk is retrieved but ranks twelfth, below the cutoff. What promotes it?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Hierarchical Chunking in One Line

Answers get cut across chunk boundaries in a long structured PDF. Best Bedrock KB chunking?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Freshness and Access Are Metadata

Retrieval must respect access control and document freshness. What enforces both without a second index?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: The Prompt-and-Completion Record

An auditor asks to see every prompt this assistant received last Tuesday. What produces it?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Who Changed It vs What It Said

Who turned off the PII filter, and when? Which log, and why not invocation logging?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Turning Logs Into an Audit

The reviewer wants a control-mapped report and a statement of what the model is approved for. Two artefacts?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: The Eight Responsible-AI Dimensions

AWS names its responsible-AI dimensions. Roughly, what are they?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Packing Many Models Onto One Endpoint

How do you serve dozens or hundreds of models without an endpoint each?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Measuring Bias With fmeval

You must measure a GenAI feature for bias and toxicity before launch. Which tool?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: What Guardrails Enforce

What does Bedrock Guardrails actually enforce at runtime?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: LLM Explainability Is Traceability

Someone asks you to explain a RAG answer. What is the realistic form of FM explainability?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Faithful but Wrong

A RAG answer scores high on faithfulness but is still wrong. How?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Evaluating Both Halves of RAG

You cannot tell if a wrong RAG answer is a retrieval or a generation problem. What evaluates each half?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: LLM-as-a-Judge, and the Catch

You need to score thousands of outputs on quality without a human reading each. Approach and caveat?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Letting an LLM Take Actions

Answering questions is one thing; calling an internal API is another. What wires an agent for real actions on Bedrock?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Turning Down the Randomness

Outputs are too random for a structured extraction task. Which inference parameters, and which way?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Provisioned Throughput vs On-Demand

Steady high-volume Bedrock traffic with a latency commitment. Reserve capacity or stay on-demand?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Prompts Are Versioned Assets

Thirty services share prompts and you need versioning and reuse. What on Bedrock?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Cutting the Bill Without Losing Quality

Your Bedrock bill is high but quality must hold. First levers?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Seeing Into a Production Bedrock App

What gives you operational visibility into a production Bedrock app?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Keeping PII Out of Prompts and Logs

Keep customer PII out of prompts and logs. What is the built-in control?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Backoff or Breaker

Nine calls in ten are failing and every request waits out the whole retry ladder before giving up. More backoff, or a breaker?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: What Model Registry Versions

Bedrock versions prompts, guardrails and agents. None of those describes a training artefact. What does a model package version actually hold?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Expand, Decompose, or Transform

Short queries in customer language miss; the same question in the documentation's words lands. Hybrid search and a reranker have already been tried. What now?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Which Amazon Assistant

Three asks land in the same week: engineers refactoring a legacy Java service, staff searching SharePoint and the ticketing system, and a customer-facing assistant inside the company's own product. Which surfaces?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Strands, Agent Squad, or AgentCore

One agent becomes four, and something now has to send each message to the right one. Which piece do you add, and which stay as they are?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Where the MCP Server Lives

Two MCP servers, one agent. One wraps a DynamoDB lookup and answers in 40ms. The other spends ninety seconds building a 6GB in-memory graph, then answers path queries against it. Where does each run?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Getting a GenAI Feature in Front of Users

Three asks in one week: a hosted chat UI with auth, an API contract agreed before anyone codes, and a pipeline reorderable without a deployment. Three different tools.

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: The Rule That Has to Be Provably Followed

An insurance assistant has to prove its eligibility answers follow from the published policy. Which guardrail policy carries that, and why is grounding not enough?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: The Bias Number That Went Stale

A hiring-summary feature passed its fairness evaluation nine months ago. Four prompt edits and two model versions later, nobody has re-measured. What keeps the number current?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Proving the Knowledge-Base Bucket Is Not Shared

Sign-off needs proof that nobody outside the account can read the knowledge-base bucket or use the key over the vector index. Which control produces it, and keeps producing it?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Naming the LLM Risk in a Pen-Test Finding

Four findings against one assistant, four different layers to fix them in. Which control closes the tool that can cancel anyone's subscription?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: A Bedrock Bill That Doubled Overnight

A seasonal Bedrock feature grows every month, so a fixed budget threshold never fires or fires constantly. What tells you the daily curve has left its normal?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: What to Scale a Model Endpoint On

CPU utilisation sits at nine per cent while the morning burst queues for minutes. What signal should the endpoint scale on, and why is the reflex metric wrong for token generation?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: The Agent Called the Wrong Tool, or the Tool Failed

The agent's answers got worse this week and its own error rate never moved. Did the model start selecting a different tool, or did a tool start returning empty results?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Retrieval Got Slow and the Answers Got Worse

Latency has tripled, compute is under its ceiling, ingestion is green, and recall has slid from 96 to 88 per cent. Three things go wrong with a vector store. Only one fits.

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Right Answer, Wrong Route

A refunds agent scores 92% on final-answer correctness and operations keep finding refunds issued twice. What do we measure next?

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: Reading a Bedrock Exception

A nightly batch now takes six hours and still fails. The logs hold two exception names, and only one of them is worth retrying.

Read article

Exam Room · Advanced Generative AI Developer

Pop Quiz: The Gate That Blocks on Noise

Every pull request runs 400 golden examples through an evaluation job and hard-fails below 0.8. Builds take fifty minutes and three of the four blocks passed on a re-run. What changes?

Read article

Labs

Build it with your own hands. Each ships a zip, a preflight check, and a teardown.

Exam Room · Advanced Generative AI Developer

Lab: Invoke a Foundation Model From Lambda

A hands-on lab, the first in the series. You are handed a Lambda function with an execution role, a model id in an environment variable, and one gap: the Bedrock call itself. Five lines of Python, deployed with CloudFormation, proven with a script, torn down when you are done. Every later lab builds on this function, so this is where the track starts.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Put a Guardrail in Front of a Bedrock Model

A hands-on lab. You are handed a working Bedrock model call and a fully-configured guardrail, and your job is the two lines that connect them. Deploy real infrastructure with CloudFormation, block a financial-advice question, watch a phone number get redacted, then tear it all down. The reading tells you what a guardrail is; this makes you wire one in.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Get Structured JSON Out With Tool Use

A hands-on lab. Asking a model for JSON in the prompt and hoping is how parsers break at 3am. This lab has you do it the reliable way: declare a tool schema, let the model fill it in, and read the answer back as parsed arguments rather than a string. You deploy a Lambda, turn a free-text support message into a structured record, and find out how much of the shape the schema really guarantees.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Give a Bedrock Chatbot a Memory

A hands-on lab. A model call is stateless: tell a chatbot your name, ask for it back, and the second reply does not have it. Memory here is a transcript you replay, stored somewhere durable between requests. This lab hands you a Lambda and a DynamoDB table and has you build the load-and-save loop that turns single calls into a conversation, then work out what replaying all those turns adds to each request.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Build RAG From Scratch

A hands-on lab. A Knowledge Base runs retrieval for you behind an API; here you write that step yourself. Five documents, two models, and one function: embed the question, compare it to the documents, ground the answer in the closest ones. No vector store, so the mechanics of RAG are in plain sight.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Wire a Tool the Model Can Call

A hands-on lab. In an earlier lab the model filled in a schema and stopped; here it returns a tool call instead of text, your code runs the tool, and the final answer comes back from the result. That request-run-return-continue cycle is the loop a managed agent runs for you. You build it by hand, so an agent's tool wiring stops being a black box.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Build a Data-Quality Gate

A hands-on lab. Bad data is easy to stop at the door and hard to remove once it is embedded. This lab hands you a pipeline that reads raw records from S3, routes them, and reports; you write the rules that separate the records fit to feed a model from the ones that would poison it. It is the hand-built version of a managed data-quality gate.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Answer a Metric Question With Text-to-SQL

A hands-on lab. You cannot embed your way to a SUM. When the answer is a computed number, retrieval is the wrong tool and text-to-SQL is the right one: hand the model a schema, let it write the query, run it safely, summarise the result. You deploy a Lambda with a small database baked in and write the one step that turns a question into SQL, behind a guard that rejects anything but a read-only SELECT.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Generate the Weekly Box Art

A hands-on lab. Greenbox's marketing changes every week because the box does, and the weekly change already exists as data: the box manifest. This wires Stability AI Stable Image Core and Luma Ray 2 onto the end of that pipeline, so one JSON file becomes the box hero, the recipe card art, a short clip of each featured farm's produce, and a looping clip of how to prep the vegetable nobody recognises. You write the two calls; the honesty policy is already in the manifest.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Evaluate the Pipeline

A hands-on lab. Every feature so far left the same question hanging: is it any good, and would a change help or hurt? You cannot tell from one reply. This lab builds the loop that answers it: a golden set, an automatic judge, and a score, so a prompt edit or a model swap becomes a number you can compare. You write the judge, the LLM-as-a-judge that turns a verdict into that number.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Fine-Tune a Model and Read the Loss Curves

A hands-on lab. The theory gave you epochs, learning rate, and the shape of a healthy loss curve. This runs an actual Bedrock customisation job over a few hundred support replies, then pulls the two metrics files back out of S3 and asks you to read them. You write the part that turns those CSVs into a verdict: underfitting, healthy, or overfitting, and the step the run should have stopped at. There is a free path, because a training job costs real money and runs long after you have stopped watching.

Read article

Exam Room · Advanced Generative AI Developer

Lab: The Capstone

A hands-on lab, and the last of the ten you build by hand. No gap to fill and no scaffolding: just data, a requirement, and an acceptance test. You assemble a grounded, guarded, honest assistant from the pieces you have built so far, and prove it passes. This is the shape of a production GenAI feature, where the model is one component and everything around it is what makes it trustworthy.

Read article

Exam Room · Advanced Generative AI Developer

Lab: Stand Up a Bedrock Knowledge Base

A hands-on lab. The from-scratch lab made you build retrieval by hand; this one hands the same documents to a managed Knowledge Base and asks you to write the two calls that query it. Chunking, an S3 Vectors index, an ingestion job, and the difference between asking for chunks and asking for an answer.

Read article