1.1.2 - Evaluating connectivity options for on-premises, co-location, and cloud integration

1.1.3 - Selecting Aws Regions and Availability Zones based on network and latency requirements

1.1.4 - Troubleshooting traffic flows by using Aws tools

1.1.5 - Using service endpoints for service integrations

1.2.1 - Evaluating cross-account access management

1.2.2 - Integrating with third-party identity providers

1.2.3 - Deploying encryption strategies for data at rest and data in transit

1.2.4 - Developing a strategy for centralized security event notifications and auditing

1.3.1 - Designing disaster recovery solutions based on RTO and RPO requirements

1.3.2 - Implementing architectures to automatically recover from failure

1.3.3 - Developing the optimal architecture by considering scale-up and scale-out options

1.3.4 - Designing an effective backup and restoration strategy

1.4.1 - Evaluating the most appropriate account structure for organizational requirements

1.4.2 - Recommending a strategy for central logging and event notifications

1.4.3 - Developing a multi-account governance model

1.5.1 - Monitoring cost and usage with Aws tools

1.5.2 - Developing an effective tagging strategy that maps costs to business units

1.5.3 - Understanding how purchasing options affect cost and performance

2.1.1 - Determining an application or upgrade path for new services and features

2.1.2 - Selecting services to develop deployment strategies and implement appropriate rollback mechanisms

2.1.3 - Adopting managed services as needed to reduce infrastructure provisioning and patching overhead

2.1.4 - Making advanced technologies accessible by delegating complex development and deployment tasks to Aws

2.2.1 - Configuring disaster recovery solutions

2.2.2 - Configuring data and database replication

2.2.3 - Performing disaster recovery testing

2.2.4 - Architecting a backup solution that is automated, is cost-effective, and supports business continuity across multiple Availability Zones or Regions

2.2.5 - Designing an architecture that provides application and infrastructure availability in the event of a disruption

2.2.6 - Using processes and components for centralized monitoring to proactively recover from system failures

2.3.1 - Specifying IAM users and IAM roles that adhere to the principle of least privilege access

2.3.2 - Specifying inbound and outbound network flows by using security group rules and network ACL rules

2.3.3 - Developing attack mitigation strategies for large-scale web applications

2.3.4 - Developing encryption strategies for data at rest and data in transit

2.3.5 - Specifying service endpoints for service integrations

2.3.6 - Developing strategies for patch management to remain compliant with organizational standards

2.4.1 - Designing highly available application environments based on business requirements

2.4.2 - Using advanced techniques to design for failure and ensure seamless system recoverability

2.4.3 - Implementing loosely coupled dependencies

2.4.4 - Operating and maintaining high-availability architectures

2.4.5 - Using Aws managed services for high availability

2.4.6 - Implementing DNS routing policies

2.5.1 - Designing large-scale application architectures for a variety of access patterns

2.5.2 - Designing an elastic architecture based on business objectives

2.5.3 - Applying design patterns to meet performance objectives with caching, buffering, and replicas

2.5.4 - Developing a process methodology for selecting purpose-built services for required tasks

2.5.5 - Designing a rightsizing strategy

2.6.1 - Identifying opportunities to select and rightsize infrastructure for cost-effective resources

2.6.2 - Identifying appropriate pricing models

2.6.3 - Performing data transfer modeling and selecting services to reduce data transfer costs

2.6.4 - Developing a strategy and implementing controls for expenditure and usage awareness