Recent Score: out of 25.

Design High Performing Architectures
Take the Test again Go Home


Loading Questions...

❮ Previous Reload Next ❯
1 / 12
Running a high-performance SAS Grid Manager cluster on AWS
2 / 12
Scaling on AWS: Service-Oriented Architecture
3 / 12
Architecture I: How to Get High Availability
4 / 12
AWS Shared Responsibility Model
5 / 12
AWS Security Toolkit
6 / 12
Architecting for Reliable Scalability
7 / 12
Monolithic architecture vs. modular architecture
8 / 12
Scalable modular applications
9/ 12
How to Get High Availability
10 / 12
Scalable 3D CAD Conversion Pipeline with PIXYZ on AWS
11 / 12
Autodesk’s Shotgun Private Cloud
12 / 12
Quick Start architecture for MongoDB on AWS



Top AWS Certified Solutions Architect Associate Exam Tips

*

This domain makes up 24% of the exam and includes the following 4 objectives:
1. Identify elastic and scalable compute solutions for a workload
2. Select high-performing and scalable storage solutions for a workload
3. Select high-performing networking solutions for a workload
4. Choose high-performing database solutions for a workload


Be able to select the best storage and database services to use for a given scenario, taking into account requirements for performance.
know how to effectively implement elasticity and scalability to your application architectures.
AWS CERTIFIED SOLUTIONS ARCHITECT SAA-C02 : HOW TO BEST PREPARE IN 5 STEPS

0

Take handwritten notes and draw diagrams to strengthen your understanding of the material and construct a robust mental model of how AWS components fit together.
#AWS Exam Prep

1

Be able to identify multiple possible use cases and eliminate non-use cases for SWF.
#AWS SWF

2

Understand how you might set up consolidated billing and cross-account access such that individual divisions resources are isolated from each other, but corporate IT can oversee all of it.
#AWS Set up consolidated billing

3

Know how you would go about making changes to an Auto Scaling group, fully understanding what you can and can't change. "You can only specify one launch configuration for an Auto Scaling group at a time, and you can't modify a launch configuration after you've created it. Therefore, if you want to change the launch configuration for your Auto Scaling group, you must create a launch configuration and then update your Auto Scaling group with the new launch configuration. When you change the launch configuration for your Auto Scaling group, any new instances are launched using the new configuration parameters, but existing instances are not affected.
#AWS Make Change to Auto Scaling group

4

Know how you would go about making changes to an Auto Scaling group, fully understanding what you can and can't change. "You can only specify one launch configuration for an Auto Scaling group at a time, and you can't modify a launch configuration after you've created it. Therefore, if you want to change the launch configuration for your Auto Scaling group, you must create a launch configuration and then update your Auto Scaling group with the new launch configuration. When you change the launch configuration for your Auto Scaling group, any new instances are launched using the new configuration parameters, but existing instances are not affected.
#AWS Make Change to Auto Scaling group

5

Know which field you use to run a script upon launching your instance.
#AWS User data script

6

Know how DynamoDB (durable, and you can pay for strong consistency), Elasticache (great for speed, not so durable), and S3 (eventual consistency results in lower latency) compare to each other in terms of durability and low latency.
#AWS DynamoDB consistency

7

Know the difference between bucket policies, IAM policies, and ACLs for use with S3, and examples of when you would use each. "With IAM policies, companies can grant IAM users fine-grained control to their Amazon S3 bucket or objects while also retaining full control over everything the users do. With bucket policies, companies can define rules which apply broadly across all requests to their Amazon S3 resources, such as granting write privileges to a subset of Amazon S3 resources. Customers can also restrict access based on an aspect of the request, such as HTTP referrer and IP address. With ACLs, customers can grant specific permissions (i.e. READ, WRITE, FULL_CONTROL) to specific users for an individual bucket or object.
#AWS Difference between bucket policies

8

Know when and how you can encrypt snapshots.
#AWS EBS Encryption

9

Understand how you can use ELB cross-zone load balancing to ensure even distribution of traffic to EC2 instances in multiple AZs registered with a load balancer.
#AWS ELB cross-zone load balancing

10

How would you allow users to log into the AWS console using active directory integration. Here is a link to some good reference material.
#AWS og into the AWS console using active directory integration

11

Spot instances are good for cost optimization, even if it seems you might need to fall back to On-Demand instances if you wind up getting kicked off them and the timeline grows tighter. The primary (but still not only) factor seems to be whether you can gracefully handle instances that die on you--which is pretty much how you should always design everything, anyway!
#AWS Spot instances