Boomi API Management study plan

Map the API Management domain blueprint into a one-page concept map linking gateway configuration, portal publication, and lifecycle states

Define the core API management vocabulary (API, endpoint, gateway, proxy, plan, consumer) in your own words without copying documentation phrasing

Configure a scratch API component in a trial account and record each configuration field you touched and why it exists

List the five most common failure points when first publishing an API and note how you would detect each

Build a working API proxy in front of a simple mock backend and verify request and response passthrough

Configure at least two distinct access plans with different rate limits and document the resulting consumer behavior

Trace one request end to end and write down where authentication, throttling, and routing each occur

Draft a troubleshooting checklist covering authentication failures, quota exhaustion, and backend timeouts

Compare API key, OAuth 2.0 client credentials, and JWT-based authentication and state when each is appropriate

Configure token-based access on your proxy and capture a successful and a rejected call for each method

Identify where secrets, client IDs, and signing keys are stored and describe what would happen if each leaked

Document the minimum set of transport and payload protections you would require before any API goes live

Apply rate limiting and quota policies at both plan and API level and observe which one wins when they conflict

Write a threat list of at least eight risks (credential replay, over-permissive scopes, verbose errors, missing input validation) and pair each with a control

Define three governance rules you would enforce in review, such as naming conventions and mandatory descriptions

Test how the gateway behaves when a backend returns errors and confirm no internal detail leaks to the consumer

Design a full API lifecycle from draft through deprecation and retirement, naming the approval gate at each transition

Create a review rubric scoring design consistency, documentation completeness, security posture, and versioning strategy

Simulate a versioning decision by introducing a breaking change and writing the consumer migration notice

Assess your own week-2 proxy against the rubric and log every gap found

Define an API product that bundles two or more APIs and assign differentiated plans to distinct consumer segments

Configure self-service consumer onboarding and verify that a new consumer can subscribe without manual intervention

Write consumer-facing documentation covering authentication, endpoints, limits, and error codes

Model a monetization or tiering structure and justify each tier boundary with a usage assumption

Instrument your product with analytics and identify the three metrics that would drive a real operational decision

Diagnose an injected fault (expired credential, exhausted quota, unreachable backend) using only logs and metrics

Reconcile your product design against the governance rubric from week 5 and correct every violation

Rehearse explaining your architecture aloud in under three minutes without notes

Retake a timed mixed-domain practice set and score each domain separately to expose weak areas

Rebuild from memory the full path from API creation to consumer subscription in a blank account

Review every missed item and write a one-line rule that would have prevented the error

Consolidate your glossary, rubrics, and checklists into a single pre-exam reference sheet