Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Attach appropriately sized EBS SSD volumes and test IOPS and throughput solves the related scenario A transactional database on EC2 needs low-latency persistent block storage; eBS provides persistent EC2 block devices suited to database files.

Although Move the photos to S3 object storage and expose them through application or CDN URLs can be valid when An object library containing product photos is accessed through HTTP URLs and has no filesystem mount requirement, it targets a different technical condition. S3 separates object persistence from host-attached file systems.

Migrate shares to Amazon FSx for Windows File Server with compatible directory configuration would address a different requirement: A migrated Windows file server must preserve SMB paths and Active Directory access semantics. FSx for Windows supports SMB and Windows ACL expectations.

Use Amazon OpenSearch Service for supported search workloads would address a different requirement: A product-search system needs stemming, ranking and full-text indexing over millions of documents. Search indexes provide text-query capabilities distinct from OLTP tables.

This alternative, Use Amazon Redshift with a measured migration from the source warehouse, is appropriate when An analytics warehouse processes historic columnar fact tables and complex aggregations. Redshift's columnar query design suits large analytical scans better than transactional RDS.

Redesign around DynamoDB with careful partition keys and access patterns solves the related scenario An old session database stores key-value records at very high scale without relational joins; dynamoDB can replace purpose-built key-value workloads with managed elastic capacity.

This alternative, Use Amazon Redshift with a measured migration from the source warehouse, is appropriate when An analytics warehouse processes historic columnar fact tables and complex aggregations. Redshift's columnar query design suits large analytical scans better than transactional RDS.

For the separate situation An on-premises PostgreSQL service uses complex joins and standard SQL transactions, Migrate to a compatible Amazon RDS or Aurora PostgreSQL offering could be useful. A managed relational engine preserves the SQL semantics required by the application.

Although Evaluate Amazon Neptune and appropriate graph queries can be valid when A fraud-analysis system traverses highly connected identity and relationship networks, it targets a different technical condition. A graph database fits variable-depth relationship traversal.

For the separate situation An old session database stores key-value records at very high scale without relational joins, Redesign around DynamoDB with careful partition keys and access patterns could be useful. DynamoDB can replace purpose-built key-value workloads with managed elastic capacity.

Evaluate Amazon Neptune and appropriate graph queries solves the related scenario A fraud-analysis system traverses highly connected identity and relationship networks; a graph database fits variable-depth relationship traversal.

Use Amazon Redshift with a measured migration from the source warehouse would address a different requirement: An analytics warehouse processes historic columnar fact tables and complex aggregations. Redshift's columnar query design suits large analytical scans better than transactional RDS.

Redesign around DynamoDB with careful partition keys and access patterns solves the related scenario An old session database stores key-value records at very high scale without relational joins; dynamoDB can replace purpose-built key-value workloads with managed elastic capacity.

Although Use Amazon OpenSearch Service for supported search workloads can be valid when A product-search system needs stemming, ranking and full-text indexing over millions of documents, it targets a different technical condition. Search indexes provide text-query capabilities distinct from OLTP tables.

Migrate to a compatible Amazon RDS or Aurora PostgreSQL offering would address a different requirement: An on-premises PostgreSQL service uses complex joins and standard SQL transactions. A managed relational engine preserves the SQL semantics required by the application.

Evaluate Amazon Neptune and appropriate graph queries would address a different requirement: A fraud-analysis system traverses highly connected identity and relationship networks. A graph database fits variable-depth relationship traversal.

This alternative, Migrate to a compatible Amazon RDS or Aurora PostgreSQL offering, is appropriate when An on-premises PostgreSQL service uses complex joins and standard SQL transactions. A managed relational engine preserves the SQL semantics required by the application.

For the separate situation An old session database stores key-value records at very high scale without relational joins, Redesign around DynamoDB with careful partition keys and access patterns could be useful. DynamoDB can replace purpose-built key-value workloads with managed elastic capacity.

This alternative, Configure Route 53 Resolver outbound forwarding to corporate DNS, is appropriate when A migrated application must resolve old corporate DNS names from inside its AWS VPC. Conditional Resolver rules preserve legacy hostname resolution across the hybrid boundary.

For the separate situation A migrated service's VPC overlaps an acquired subsidiary's on-premises address space, Redesign IP allocation or introduce scoped translation/proxy connectivity could be useful. Direct routed VPC connectivity cannot transparently handle overlapping CIDR blocks.

Although Configure proper ALB target groups, VPC routes and security-group references can be valid when A new public ALB must call migrated app tasks hosted only in private subnets, it targets a different technical condition. The ALB accepts public ingress while its registered targets remain privately addressed.

For the separate situation An application moved to private AWS subnets must retain a secure private path to its on-premises database during transition, Connect networks through approved Direct Connect or Site-to-Site VPN with correct routes could be useful. Hybrid transport and routing are needed while database calls remain on-premises.

Although Configure proper ALB target groups, VPC routes and security-group references can be valid when A new public ALB must call migrated app tasks hosted only in private subnets, it targets a different technical condition. The ALB accepts public ingress while its registered targets remain privately addressed.

Segment VPC and Transit Gateway route tables and apply centrally inspected egress would address a different requirement: A security team needs to isolate internet egress for different migrated divisions. Segmented routing limits shared east-west access among migration tenants.

Configure Route 53 Resolver outbound forwarding to corporate DNS solves the related scenario A migrated application must resolve old corporate DNS names from inside its AWS VPC; conditional Resolver rules preserve legacy hostname resolution across the hybrid boundary.

Segment VPC and Transit Gateway route tables and apply centrally inspected egress would address a different requirement: A security team needs to isolate internet egress for different migrated divisions. Segmented routing limits shared east-west access among migration tenants.

This alternative, Connect networks through approved Direct Connect or Site-to-Site VPN with correct routes, is appropriate when 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.

Although Segment VPC and Transit Gateway route tables and apply centrally inspected egress can be valid when A security team needs to isolate internet egress for different migrated divisions, it targets a different technical condition. Segmented routing limits shared east-west access among migration tenants.

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.

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.