MGWC study plan

Map a real or hypothetical system landscape into system, process, and experience layers and justify each boundary in writing

Draft an architecture description covering consumers, providers, protocols, data ownership, sync vs async, and latency/volume assumptions

Explain how API-led connectivity differs from point-to-point ESB integration and when each is appropriate

Identify three integration anti-patterns in a described landscape and propose a layered redesign for each

Select and justify integration patterns (request-reply, fire-and-forget, pub-sub, scatter-gather, idempotent consumer) for five given scenarios

Design a canonical data model and document field-level mapping rules between two source systems

Specify error-handling behavior: retry policy, dead-letter path, compensation, and idempotency keys

Document non-functional requirements (throughput, latency, availability, retention) for the same scenario

Decompose a business capability into experience, process, and system API responsibilities with explicit contracts

Choose between APIkit-driven flows, DataWeave transforms, and connector-based operations for each step and state why

Define reusable assets and versioning strategy for shared process and system APIs

Sketch a RAML or OAS fragment for two APIs including resources, methods, and error responses

Configure an API instance in API Manager and apply rate limiting, throttling, and SLA tiers to a described consumer set

Select and order policies (client ID enforcement, OAuth 2.0 token enforcement, JSON/XML threat protection, CORS) with rationale for ordering

Model identity flows for machine-to-machine and delegated user access, including token scope design

Explain how secrets, keystores, and truststores are managed without embedding credentials in application code

Diagnose throughput and latency bottlenecks in a described flow and propose concrete remediations

Design streaming vs in-memory processing decisions for large payloads and justify batch sizes

Specify caching, connection pooling, and backpressure behavior with target metrics

Write failure-mode tests for timeouts, partial failures, and duplicate delivery

Define a promotion path across dev, test, and prod including property externalization and environment-specific configuration

Design a CI/CD pipeline stage list from commit to production with automated tests and approval gates

Describe how API versions and policies are promoted and rolled back consistently with application deployments

List operational runbook items: health checks, log aggregation, alert thresholds, and on-call escalation

Threat-model one integration against OWASP API risks and map each risk to a mitigating policy or design change

Design a defense-in-depth plan covering transport, message-level protection, and data masking in logs

Specify audit logging and access review requirements for sensitive APIs

Evaluate trade-offs between centralized policy enforcement at the gateway and in-application validation

Rehearse scenario-based architecture decisions under time pressure across all eight domains

Reconcile earlier deliverables into one coherent reference architecture with consistent naming and assumptions

Identify and close the three weakest domain areas using targeted review of your own notes

Practice explaining trade-offs verbally in short, structured answers