Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Although Provide compatible directory connectivity through AWS Directory Service or managed AD integration can be valid when A migrated application previously used Active Directory integrated authentication for file shares, it targets a different technical condition. Directory-aware workloads require working identity and domain services after relocation.

Establish appropriate Organizations OUs and SCP guardrails before account enrollment would address a different requirement: A new AWS landing zone must enforce region restrictions before the first migration wave lands. Precutover governance prevents new workloads from deploying outside authorized boundaries.

This alternative, Remove and rotate the secret and use Secrets Manager or temporary role credentials, is appropriate when An on-premises service account password is embedded in a migration script checked into Git. Secret rotation and controlled runtime retrieval prevent repeating source-code credential leaks.

For the separate situation A historical data archive requires documented chain of custody after copying into S3, Enable object integrity checks, audit logs and immutable retention where required could be useful. Migration evidence must establish object completeness and protection from modification.

Use incremental transfer retries and inspect the tool's detailed failure reports solves the related scenario A migration job fails on a few files with invalid path names and repeatedly restarts the entire transfer; targeted retries address malformed files without recopying an entire dataset.

Although Scope audit logging and access controls to the migration role, and review data-access event history can be valid when A regulated migration must prove that no unexpected records were exposed during source access, it targets a different technical condition. Fine-grained data access evidence supports migration security verification.

For the separate situation An encrypted S3 destination receives objects copied from another AWS account under a different KMS key, Configure correct KMS decrypt and encrypt permissions for the migration principal and destination key could be useful. Cross-account object movement can fail without both source and destination key authority.

Scope audit logging and access controls to the migration role, and review data-access event history solves the related scenario A regulated migration must prove that no unexpected records were exposed during source access; fine-grained data access evidence supports migration security verification.

Replace administrator permissions with minimum S3 and KMS actions at required resource scope would address a different requirement: A data transfer agent must write to one S3 destination prefix but has full account-wide administrator permissions. Narrow transfer-role policies protect other resources during bulk migrations.

Scope audit logging and access controls to the migration role, and review data-access event history solves the related scenario A regulated migration must prove that no unexpected records were exposed during source access; fine-grained data access evidence supports migration security verification.

Enable object integrity checks, audit logs and immutable retention where required would address a different requirement: A historical data archive requires documented chain of custody after copying into S3. Migration evidence must establish object completeness and protection from modification.

This alternative, Configure correct KMS decrypt and encrypt permissions for the migration principal and destination key, is appropriate when An encrypted S3 destination receives objects copied from another AWS account under a different KMS key. Cross-account object movement can fail without both source and destination key authority.

Although Replace administrator permissions with minimum S3 and KMS actions at required resource scope can be valid when A data transfer agent must write to one S3 destination prefix but has full account-wide administrator permissions, it targets a different technical condition. Narrow transfer-role policies protect other resources during bulk migrations.

Enable object integrity checks, audit logs and immutable retention where required would address a different requirement: A historical data archive requires documented chain of custody after copying into S3. Migration evidence must establish object completeness and protection from modification.

For the separate situation A migration job fails on a few files with invalid path names and repeatedly restarts the entire transfer, Use incremental transfer retries and inspect the tool's detailed failure reports could be useful. Targeted retries address malformed files without recopying an entire dataset.

Enable object integrity checks, audit logs and immutable retention where required would address a different requirement: A historical data archive requires documented chain of custody after copying into S3. Migration evidence must establish object completeness and protection from modification.

This alternative, Configure correct KMS decrypt and encrypt permissions for the migration principal and destination key, is appropriate when An encrypted S3 destination receives objects copied from another AWS account under a different KMS key. Cross-account object movement can fail without both source and destination key authority.

For the separate situation A data transfer agent must write to one S3 destination prefix but has full account-wide administrator permissions, Replace administrator permissions with minimum S3 and KMS actions at required resource scope could be useful. Narrow transfer-role policies protect other resources during bulk migrations.

For the separate situation A containerized API already has an ECS task definition and team wants to stop managing node instances, Migrate eligible tasks to ECS with Fargate launch type could be useful. Fargate removes host provisioning while retaining ECS task and service concepts.

Although Use appropriate EC2 accelerated instances with workload-aware scheduling can be valid when A large batch simulation runs for hours with custom GPU drivers and high fixed capacity needs, it targets a different technical condition. Long specialized compute jobs may require direct host and accelerator control.

Move the handler to Lambda after validating runtime and request constraints would address a different requirement: A migrated HTTP handler is stateless, runs for seconds and has unpredictable demand. Lambda handles short on-demand work without persistent server capacity.

Choose Elastic Beanstalk and test the application's platform compatibility solves the related scenario A migration requires a managed web deployment environment for a supported platform with minimal infrastructure scripting; beanstalk handles environment orchestration while preserving a conventional web app deployment model.

Keep it on managed EC2 instances until those OS dependencies can be removed would address a different requirement: A legacy application has a tightly coupled OS service and requires privileged host-level changes. EC2 retains operating-system control unavailable in fully managed serverless services.

This alternative, Migrate eligible tasks to ECS with Fargate launch type, is appropriate when A containerized API already has an ECS task definition and team wants to stop managing node instances. Fargate removes host provisioning while retaining ECS task and service concepts.

Although Keep it on managed EC2 instances until those OS dependencies can be removed can be valid when A legacy application has a tightly coupled OS service and requires privileged host-level changes, it targets a different technical condition. EC2 retains operating-system control unavailable in fully managed serverless services.

This alternative, Use appropriate EC2 accelerated instances with workload-aware scheduling, is appropriate when A large batch simulation runs for hours with custom GPU drivers and high fixed capacity needs. Long specialized compute jobs may require direct host and accelerator control.

For the separate situation A migration requires a managed web deployment environment for a supported platform with minimal infrastructure scripting, Choose Elastic Beanstalk and test the application's platform compatibility could be useful. Beanstalk handles environment orchestration while preserving a conventional web app deployment model.

This alternative, Migrate eligible tasks to ECS with Fargate launch type, is appropriate when A containerized API already has an ECS task definition and team wants to stop managing node instances. Fargate removes host provisioning while retaining ECS task and service concepts.

For the separate situation A migration requires a managed web deployment environment for a supported platform with minimal infrastructure scripting, Choose Elastic Beanstalk and test the application's platform compatibility could be useful. Beanstalk handles environment orchestration while preserving a conventional web app deployment model.

Move the handler to Lambda after validating runtime and request constraints solves the related scenario A migrated HTTP handler is stateless, runs for seconds and has unpredictable demand; lambda handles short on-demand work without persistent server capacity.

This alternative, Migrate eligible tasks to ECS with Fargate launch type, is appropriate when A containerized API already has an ECS task definition and team wants to stop managing node instances. Fargate removes host provisioning while retaining ECS task and service concepts.

For the separate situation A legacy application has a tightly coupled OS service and requires privileged host-level changes, Keep it on managed EC2 instances until those OS dependencies can be removed could be useful. EC2 retains operating-system control unavailable in fully managed serverless services.

Although Move the handler to Lambda after validating runtime and request constraints can be valid when A migrated HTTP handler is stateless, runs for seconds and has unpredictable demand, it targets a different technical condition. Lambda handles short on-demand work without persistent server capacity.