AIP-C01 · LESSON 2

Implementation and Integration26% · 5 topics

Learn agentic AI and tool integration, model deployment strategies, enterprise integration, FM API integration, and app integration patterns and development tools.

2.1Agentic AI and tool integration

2.1 Implement agentic AI solutions and tool integrations.

Concept

An agent is a mechanism where the model makes a plan, calls tools, looks at the results and decides the next step. Amazon Bedrock AgentCore is a foundation for running agents built with any framework (Strands Agents, LangGraph, etc.) in production, providing Runtime (execution), Gateway (turning APIs and Lambda into MCP tools), Memory (short- and long-term memory), Identity (authentication) and Observability. Bedrock Agents (managed) are built from action groups and knowledge bases.

How it works / steps

  1. Define the agent's purpose and the scope of tools it may use
  2. Expose existing APIs and Lambda functions as MCP tools with AgentCore Gateway
  3. Store information that spans conversations in AgentCore Memory
  4. Insert human approval (human-in-the-loop) for high-impact actions
  5. Check the tool call path in traces

Workplace example

Build an internal expense reimbursement agent with Strands Agents, run it on AgentCore Runtime, turn the expense system's API into an MCP tool with Gateway, and carry over user permissions with Identity.

Common confusions and exam tips

Mini quiz

Q1. Which is the most appropriate description of how a ReAct-style agent works?

  1. Regardless of the question, call every tool once in a fixed order and return the concatenated results
  2. Generate an answer only once at the start and return it to the user without using tools
  3. Have the user choose which tool to use every time and act exactly on that instruction
  4. Repeat think → use a tool → observe the result, and answer once the goal is reached
Show answer and explanation

Answer: D Repeat think → use a tool → observe the result, and answer once the goal is reached

ReAct alternates reasoning (Reason) and action (Act), observing tool results to decide the next action.

Q2. You are defining tools for an agent. What is most important so the model chooses tools correctly?

  1. Provide as many tools with similar names and functions as possible and let the model choose
  2. Do not define tool input formats and accept any string
  3. Make tool names and descriptions clear and show argument meaning and types in an input JSON Schema
  4. Name tools with short numbers only and let the model guess without descriptions
Show answer and explanation

Answer: C Make tool names and descriptions clear and show argument meaning and types in an input JSON Schema

The model chooses by looking at tool names, descriptions and schemas. Clear descriptions and schemas lead to correct choices and arguments.

Reference links

2.2Model deployment strategies

2.2 Implement model deployment strategies.

Concept

Bedrock inference options are on-demand (per token), batch inference (cheap for large asynchronous workloads), Provisioned Throughput (capacity reserved in model units, often required for custom models) and cross-Region inference. Intelligent Prompt Routing lowers cost by routing between larger and smaller models within a model family according to question difficulty. You can also host your own models on SageMaker AI.

How it works / steps

  1. Check traffic volume, patterns and immediacy requirements
  2. Use on-demand for variable conversations and batch inference for nightly bulk jobs
  3. Use Provisioned Throughput for steady heavy use or custom models
  4. Use Intelligent Prompt Routing when there are many easy questions
  5. Use SageMaker AI when you need your own models or fine-grained control

Workplace example

Run nightly generation of 1 million product descriptions as batch inference to make it cheaper than on-demand, and use prompt routing in daytime chat to send easy questions to a smaller model.

Common confusions and exam tips

Mini quiz

Q1. Which statement about Bedrock Provisioned Throughput is incorrect?

  1. Only tokens used are billed, with no charge for idle time
  2. You purchase model units to secure a fixed throughput
  3. Longer commitment terms such as 1 or 6 months give discounted hourly rates
  4. It may be usable for inference with custom models
Show answer and explanation

Answer: A Only tokens used are billed, with no charge for idle time

Provisioned Throughput is billed hourly for the purchased model units, and charges apply even when unused.

Q2. Throttling on on-demand Bedrock increases at peak times, and you are considering buying Provisioned Throughput. What is the most appropriate next step?

  1. Without investigating the cause, just greatly increase app retry counts
  2. Without measuring needs, buy as many model units as possible for the longest term
  3. Ban all use at peak times and tell users to use it late at night or early morning
  4. Measure tokens per minute at peak in CloudWatch and estimate the number of model units needed
Show answer and explanation

Answer: D Measure tokens per minute at peak in CloudWatch and estimate the number of model units needed

Buy Provisioned Throughput by estimating capacity from the required token volume. Also compare cross-Region inference and quota increases.

Reference links

2.3Enterprise integration architecture

2.3 Design and implement enterprise integration architectures.

Concept

When integrating with enterprise systems, combine API Gateway (authentication, throttling), EventBridge (event-driven), SQS (asynchronous, load leveling) and Step Functions (workflows) to connect generative AI with existing business systems (ERP, CRM) and data platforms. Use IAM, Cognito or the corporate IdP for authentication, and keep networking private with VPC endpoints (PrivateLink).

How it works / steps

  1. Decide the business flow that calls generative AI (synchronous or asynchronous)
  2. Handle authentication and throttling with API Gateway
  3. Make long-running processing asynchronous with SQS or Step Functions
  4. Receive business system events with EventBridge to start processing
  5. Call Bedrock privately through VPC endpoints

Workplace example

When an inquiry is created in the CRM, an EventBridge event starts Step Functions, which creates a summary and classification with Bedrock and writes them back to the CRM.

Common confusions and exam tips

Mini quiz

Q1. Most steps are fixed, but you want to use FM judgment (summarization or classification) at some stages, with reliable control of the overall flow. Which architecture is most appropriate?

  1. Instruct a Bedrock agent on the steps and let it decide tool call order
  2. Chain Lambda functions so each calls the next one directly
  3. Define the flow in Step Functions and use the Bedrock invoke integration where needed
  4. Process every step with FM nodes in Bedrock Prompt Flows
Show answer and explanation

Answer: C Define the flow in Step Functions and use the Bedrock invoke integration where needed

Step Functions can integrate Bedrock calls directly, using FM judgment within a fixed flow. [Other options] With agents the model decides the order, so control is weak. FM nodes everywhere rely on the FM even for fixed steps. Direct Lambda chaining makes retries and state hard.

Q2. You want an on-premises workflow system to call the assistant API without going over the internet. Which architecture is most appropriate?

  1. Call an API Gateway private API via a VPC endpoint over Direct Connect or VPN
  2. Attach an IP-restricting resource policy to an API Gateway Regional API
  3. Put the API behind CloudFront and restrict access with AWS WAF
  4. Create a Lambda function URL and restrict callers with IAM auth
Show answer and explanation

Answer: A Call an API Gateway private API via a VPC endpoint over Direct Connect or VPN

An API Gateway private API can be called only through a VPC endpoint. Connect from on-premises with Direct Connect or VPN. [Other options] Regional APIs, CloudFront and function URLs all use internet paths. Restrictions don't meet the no-internet requirement.

Reference links

2.4FM API integration

2.4 Implement FM API integrations.

Concept

Bedrock APIs include InvokeModel (model-specific format), Converse (unified format, tool use) and streaming (InvokeModelWithResponseStream, ConverseStream). Use retries with exponential backoff for throttling (ThrottlingException), streaming for long responses, and tool use (JSON schema) to fix the output format.

How it works / steps

  1. Implement with the Converse API to prepare for switching models
  2. Return responses with streaming when perceived speed matters
  3. Tune the SDK retry settings (exponential backoff)
  4. Get structured output through tool definitions (JSON schema)
  5. Handle each error code (429, 400, 500) differently

Workplace example

Use ConverseStream in the chat UI to show the first token within one second, and retry ThrottlingException with exponential backoff and jitter.

Common confusions and exam tips

Mini quiz

Q1. An agent's tool calls an external API. You want the agent to stay stable even when the API is slow or fails. Which implementation is most appropriate?

  1. Set timeouts and retries, return failures to the model as structured errors, and let it decide the next action
  2. Repeat the same call any number of times with no wait or timeout until the API succeeds
  3. When the API fails, hide the error and return a “succeeded” result to the model
  4. Ignore all API failures and immediately end the whole agent process
Show answer and explanation

Answer: A Set timeouts and retries, return failures to the model as structured errors, and let it decide the next action

Add timeouts, retries and error handling to tools, and clearly convey failures to the model so it can choose an alternative.

Q2. You want every AWS account in the company to use only specific approved models. Which approach is most appropriate?

  1. Grant permissions to each team's role with IAM Identity Center permission sets
  2. Enable only approved models in each account's Bedrock model access
  3. Use an Organizations SCP to deny InvokeModel except on approved model ARNs
  4. Detect and notify unapproved model use with AWS Config rules
Show answer and explanation

Answer: C Use an Organizations SCP to deny InvokeModel except on approved model ARNs

SCPs and IAM policies can restrict invocation conditioned on model ARNs. SCPs suit organization-wide governance. [Other options] Per-account model access can be changed by each account's admins. Config detects but doesn't block calls. Permission sets only cover Identity Center users.

Reference links

2.5App integration patterns and development tools

2.5 Implement application integration patterns and development tools.

Concept

Generative AI app development uses the AWS SDKs, agent frameworks such as Strands Agents, Amazon Q Developer (coding assistance), Bedrock Prompt Flows (no-code workflows), Amplify (frontend) and more. Integration patterns such as caching, asynchronous processing and fallback (switching to another model) also matter.

How it works / steps

  1. Choose development tools and frameworks that fit the use case
  2. Cache responses to identical questions
  3. Prepare fallbacks for model failures and throttling
  4. Make environments reproducible with IaC (CDK, CloudFormation)
  5. Build prompts and evaluation into CI/CD

Workplace example

Cache responses to common FAQ questions in ElastiCache, and fall back to another model when the primary model is throttled.

Common confusions and exam tips

Mini quiz

Q1. You want Bedrock Agents actions to run inside your own app rather than Lambda (to call systems inside the internal network). Which approach is most appropriate?

  1. Expose internal systems to the internet so the agent can call them freely
  2. Use return of control so the agent returns the chosen operation and arguments to the app to execute
  3. Stop using actions and have the agent guess internal system information
  4. Write all action logic in the prompt and let the model operate internal systems directly without permission limits
Show answer and explanation

Answer: B Use return of control so the agent returns the chosen operation and arguments to the app to execute

With return of control, the agent returns the chosen action and arguments to the app, which executes it and returns the result.

Q2. You want to add an “order note summary” feature to an existing order app without changing the app's response speed. Which integration method is most appropriate?

  1. Make summarization a separate app and have staff copy and paste order content by hand each time
  2. Run summarization (Lambda, etc.) asynchronously on the order-saved event and display the summary on screen later
  3. Call the FM synchronously inside the order-save process and make saving wait until the summary is ready
  4. Do not save order notes and have the FM imagine and summarize the content each time
Show answer and explanation

Answer: B Run summarization (Lambda, etc.) asynchronously on the order-saved event and display the summary on screen later

To avoid slowing main processing, run generative AI processing asynchronously on events.

Reference links

Lessons are written by this site based on public information and do not guarantee exam content. Product specifications change, so check the latest information at the reference links.

Notes (unofficial, original questions, no pass guarantee)