Courseiva
Accelerate Workload Migration and ModernizationhardMultiple ChoiceObjective-mapped

SAP-C02 Practice Question: Accelerate Workload Migration and Modernization

A company is migrating a large-scale, stateful application to AWS. The application maintains session state in memory on the current on-premises servers. The company needs a solution that preserves session state during migration and minimizes latency for users worldwide. Which strategy should the company use?

⚠ Common exam trap

It's easy for candidates to confuse Route 53 weighted routing with Global Accelerator's traffic-shifting capabilities, overlooking that Global Accelerator provides both performance optimization and gradual traffic migration, while Route 53 alone lacks the anycast edge network and fine-grained endpoint weight management needed for low-latency stateful migration.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Use AWS Global Accelerator to gradually shift traffic, and use Amazon ElastiCache for Redis to centralize session state

AWS Global Accelerator allows you to gradually shift traffic from on-premises to AWS using endpoint weights, minimizing disruption during migration. Amazon ElastiCache for Redis provides a centralized, in-memory session store that preserves session state across the migration, ensuring low-latency access for users worldwide by leveraging Global Accelerator's anycast IP and AWS edge locations.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Use AWS Global Accelerator to gradually shift traffic, and use Amazon ElastiCache for Redis to centralize session state

    Why this is correct

    Global Accelerator provides anycast IP and traffic shifting; ElastiCache provides low-latency state sharing.

  • Use Amazon Route 53 weighted routing to shift traffic to new EC2 instances, and store session state in Amazon S3

    Why it's wrong here

    S3 is not designed for low-latency session state; Route 53 alone doesn't share state between on-prem and AWS.

  • Use AWS CloudFront to cache static content, and use Amazon DynamoDB for session state

    Why it's wrong here

    CloudFront is for content delivery, not traffic shifting for dynamic stateful apps.

  • Use AWS Global Accelerator to shift traffic, and deploy AWS WAF to protect the application

    Why it's wrong here

    WAF is for web application firewall, not session state management.

About these practice questions

Courseiva writes every SAP-C02 question from scratch — 1,660 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on SAP-C02

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A company is migrating a legacy monolithic application to AWS. The application has a stateful session layer that uses local disk storage. The migration plan involves rehosting the application on Amazon EC2 instances. What architecture change should the company implement to ensure high availability and stateless application tiers?

medium
  • A.Store session data in Amazon S3 with Transfer Acceleration.
  • B.Use Amazon RDS with Multi-AZ to store session data.
  • C.Use Amazon ElastiCache for session state management.
  • D.Attach Amazon EBS volumes to each EC2 instance for session persistence.

Why C: ElastiCache provides a low-latency, highly available, and scalable in-memory cache that can store session state independently from EC2 instances. This decouples state from compute, enabling stateless application tiers that can be auto-scaled and replaced without losing session data. Option A (S3 Transfer Acceleration) is not suitable for frequent, low-latency session reads/writes. Option B (RDS Multi-AZ) is designed for relational databases, not session caching, and would introduce unnecessary overhead. Option D (EBS volumes) ties state to specific instances, preventing high availability and auto-scaling.

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.