Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Connect networks through approved Direct Connect or Site-to-Site VPN with correct routes would address a different requirement: An application moved to private AWS subnets must retain a secure private path to its on-premises database during transition. Hybrid transport and routing are needed while database calls remain on-premises.

This alternative, Redesign IP allocation or introduce scoped translation/proxy connectivity, is appropriate when A migrated service's VPC overlaps an acquired subsidiary's on-premises address space. Direct routed VPC connectivity cannot transparently handle overlapping CIDR blocks.

For the separate situation A new public ALB must call migrated app tasks hosted only in private subnets, Configure proper ALB target groups, VPC routes and security-group references could be useful. The ALB accepts public ingress while its registered targets remain privately addressed.

Use API Gateway with Lambda integration and an appropriate authorizer solves the related scenario A lightweight data API runs unpredictable bursts and requires managed authentication and request throttling; API Gateway centralizes API policy while Lambda scales invocation-driven compute.

Although Implement Step Functions orchestration with explicit approval and timeout states can be valid when A multi-step order workflow must wait for a human approval and resume on timeout, it targets a different technical condition. Durable state-machine transitions handle multi-step asynchronous approvals.

Use ECS Fargate scheduled tasks or an appropriate batch service for long-running compute would address a different requirement: An application has one monthly batch run that lasts much longer than Lambda's maximum runtime. Long tasks require a compute environment without Lambda's invocation-duration cap.

Use API Gateway with Lambda integration and an appropriate authorizer solves the related scenario A lightweight data API runs unpredictable bursts and requires managed authentication and request throttling; API Gateway centralizes API policy while Lambda scales invocation-driven compute.

Implement Step Functions orchestration with explicit approval and timeout states would address a different requirement: A multi-step order workflow must wait for a human approval and resume on timeout. Durable state-machine transitions handle multi-step asynchronous approvals.

This alternative, Replace its long-running polling host with EventBridge Scheduler and Lambda where execution fits, is appropriate when A scheduled ETL polling service has no work outside short nightly runs. Scheduled on-demand serverless execution avoids continuously provisioned idle hosts.

Although Use ECS Fargate scheduled tasks or an appropriate batch service for long-running compute can be valid when An application has one monthly batch run that lasts much longer than Lambda's maximum runtime, it targets a different technical condition. Long tasks require a compute environment without Lambda's invocation-duration cap.

Replace its long-running polling host with EventBridge Scheduler and Lambda where execution fits would address a different requirement: A scheduled ETL polling service has no work outside short nightly runs. Scheduled on-demand serverless execution avoids continuously provisioned idle hosts.

For the separate situation A monolith emits simple image thumbnail tasks that can run independently from the API response, Move thumbnail work to S3 event notifications and Lambda with idempotency safeguards could be useful. Object-event-driven compute decouples background image processing from the frontend.

Replace its long-running polling host with EventBridge Scheduler and Lambda where execution fits would address a different requirement: A scheduled ETL polling service has no work outside short nightly runs. Scheduled on-demand serverless execution avoids continuously provisioned idle hosts.

For the separate situation A lightweight data API runs unpredictable bursts and requires managed authentication and request throttling, Use API Gateway with Lambda integration and an appropriate authorizer could be useful. API Gateway centralizes API policy while Lambda scales invocation-driven compute.

Use ECS Fargate scheduled tasks or an appropriate batch service for long-running compute solves the related scenario An application has one monthly batch run that lasts much longer than Lambda's maximum runtime; long tasks require a compute environment without Lambda's invocation-duration cap.

This alternative, Use API Gateway with Lambda integration and an appropriate authorizer, is appropriate when A lightweight data API runs unpredictable bursts and requires managed authentication and request throttling. API Gateway centralizes API policy while Lambda scales invocation-driven compute.

Implement Step Functions orchestration with explicit approval and timeout states solves the related scenario A multi-step order workflow must wait for a human approval and resume on timeout; durable state-machine transitions handle multi-step asynchronous approvals.

Although Move thumbnail work to S3 event notifications and Lambda with idempotency safeguards can be valid when A monolith emits simple image thumbnail tasks that can run independently from the API response, it targets a different technical condition. Object-event-driven compute decouples background image processing from the frontend.

Prefer SNS fanout or EventBridge pub-sub for independent subscriber notifications solves the related scenario A company wants all new services to synchronously call one centralized orchestrator for simple notifications; asynchronous fanout avoids unnecessary runtime coupling through a central synchronous service.

Although Implement application idempotency keys and conditional transaction updates can be valid when A payment event may be delivered twice during migration and could double-charge customers, it targets a different technical condition. At-least-once messaging requires business-level deduplication of side effects.

This alternative, Publish domain events to EventBridge and configure independent downstream subscriptions, is appropriate when A billing service must receive every product-created event without depending on the catalog service's uptime. Event buses decouple producers from independently available consumers.

Although Implement application idempotency keys and conditional transaction updates can be valid when A payment event may be delivered twice during migration and could double-charge customers, it targets a different technical condition. At-least-once messaging requires business-level deduplication of side effects.

Assign data ownership and introduce a versioned API or events between the services would address a different requirement: A migration extracts customer profiles into a new service but shared database tables cause accidental cross-service writes. Service isolation requires explicit state ownership rather than shared mutable tables.

This alternative, Prefer SNS fanout or EventBridge pub-sub for independent subscriber notifications, is appropriate when A company wants all new services to synchronously call one centralized orchestrator for simple notifications. Asynchronous fanout avoids unnecessary runtime coupling through a central synchronous service.

Introduce an SQS queue and idempotent inventory consumers would address a different requirement: A monolith holds incoming orders synchronously while a slow inventory system responds. Queued work absorbs dependency latency and separates acceptance from processing.

For the separate situation A billing service must receive every product-created event without depending on the catalog service's uptime, Publish domain events to EventBridge and configure independent downstream subscriptions could be useful. Event buses decouple producers from independently available consumers.

Prefer SNS fanout or EventBridge pub-sub for independent subscriber notifications solves the related scenario A company wants all new services to synchronously call one centralized orchestrator for simple notifications; asynchronous fanout avoids unnecessary runtime coupling through a central synchronous service.

This alternative, Publish domain events to EventBridge and configure independent downstream subscriptions, is appropriate when A billing service must receive every product-created event without depending on the catalog service's uptime. Event buses decouple producers from independently available consumers.

Implement application idempotency keys and conditional transaction updates solves the related scenario A payment event may be delivered twice during migration and could double-charge customers; at-least-once messaging requires business-level deduplication of side effects.

Although Introduce an SQS queue and idempotent inventory consumers can be valid when A monolith holds incoming orders synchronously while a slow inventory system responds, it targets a different technical condition. Queued work absorbs dependency latency and separates acceptance from processing.

For the separate situation A company wants all new services to synchronously call one centralized orchestrator for simple notifications, Prefer SNS fanout or EventBridge pub-sub for independent subscriber notifications could be useful. Asynchronous fanout avoids unnecessary runtime coupling through a central synchronous service.

Introduce an SQS queue and idempotent inventory consumers solves the related scenario A monolith holds incoming orders synchronously while a slow inventory system responds; queued work absorbs dependency latency and separates acceptance from processing.

Although Assign data ownership and introduce a versioned API or events between the services can be valid when A migration extracts customer profiles into a new service but shared database tables cause accidental cross-service writes, it targets a different technical condition. Service isolation requires explicit state ownership rather than shared mutable tables.