304 North Cardinal St.
Dorchester Center, MA 02124
This is not your typical AWS reference course. You won’t find most of the knowledge that’s shared here in the AWS docs. The goal here is to help you realize which AWS features you’d be foolish not to use — features that have passed the test of time by being at the backbone of most things on the Internet.
In this course, you’ll learn a technique used to help make reliable technical choices without getting paralyzed in the face of so many options. You’ll start by going through the most fundamental services AWS offers such as DynamoDB, S3, EC2. Each section breaks down how it’s used, the pros and cons, why you should (or shouldn’t) be using it, and more.
Q1. Which of the following is the central application in the AWS fleet of services?
Q1. What should your default choice be?
Q1. One of the major differences between DynamoDB and relational database is that in DynamoDB, data aggregration is done close to the data as opposed to relational database.
Q1. With on-demand request pricing, you will have the burden to monitor your utilization and proactively provision the necessary capacity.
Q1. S3 is a highly-durable hash table in the cloud. The key can be any string, and the value any blob of data up to ______ TB?
Q1. The biggest benefit in using EC2 instances is: you pay for the number of seconds an instance is being used and not by the number of seconds an instance is running.
Q1. Headroom acts as a safety buffer that can absorb many types of unpredictable events.
Q1. One of the limitations of Auto Scaling is that you have to manually remove an instance from the auto scaling group if it becomes unhealthy.
Q1. Unlike S3, it is very hard to run a sophisticated piece of software on Lambda without making some very drastic changes to your application.
Q1. NLBs are proper reverse proxies that sit between the internet and your application.
Q1. Route 53 provides support for ALIAS records as long as they point to AWS resources.
Q1. CloudFormation lets you create and update the things you have in AWS without having to click around on the console or write fragile scripts.
Q1. In SQS, there is no strict ordering because SQS queue is actually a bunch of queues behind the scenes and duplicate messages can emerge within SQS too.
Q1. Once a Kinesis message gets consumed, it gets deleted from the queue as opposed to SQS where it is appended to the end of the file.
Q1. The other nice thing that comes with ______ is the ability to simply add or remove instances just by updating the desired capacity setting.
Q2. The nice thing about EC2 is that the computer you get will be very similar to the computer you use to develop your software.
Q3. Unlike SQS, records in a Kinesis stream don’t get deleted when consumed, so it’s a pure append-only data structure behind the scenes.
Q4. Fundamentally, you can think of ______ as a highly-durable hash table in the cloud.
Q5. NLB behaves like a single-tenant system. AWS keeps track of your request rates and then automatically scales your NLB up or down based on the demand it sees.
Q6. ______ doesn’t come with an API to resize an image after uploading it to a bucket, but with Lambda, you can add that capability.
Q7. Application load balancers come with an API to respond with a fixed response for a given route, but they can’t respond with an image. ______ lets you make your load balancer do that.
Q8. If we have a small piece of code that will rarely need to be changed and that needs to run in response to something that happens in our AWS account, then ______ is a very good default choice.
Q9. The number of messages stored in SQS (the backlog size) is limited.
Q10. ______ doesn’t support regex-based alerting on application logs.
I hope this The Good Parts of AWS: Cutting Through the Clutter Educative Quiz Answers would be useful for you to learn something new from this problem. If it helped you then don’t forget to bookmark our site for more Coding Solutions.
This Problem is intended for audiences of all experiences who are interested in learning about Data Science in a business context; there are no prerequisites.
More Coding Solutions >>