AWS Cloud Practitioner Exam: Identify AWS Resources with Automation Capabilities

Which AWS Resource or Feature Does NOT Provide Automation Capabilities?

Question

Among the AWS resources or the AWS features (cloud concepts) listed below, which option does NOT provide automation capabilities?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer: D.

Option A is incorrect.

Elastic Beanstalk provides a fast way to deploy a web application on AWS.

Behind the scenes, it automatically handles resource provisioning, load balancing, autoscaling and monitoring when configured.

Option B is incorrect.

DynamoDB contains a feature called DynamoDB streams that provides change events for automatically capturing data during operations like CREATE, DELETE, UPDATE on its tables.

This relieves application developers from implementing naive methods like using a timer at regular intervals to scan the tables for specific data patterns for creating dashboards, which is non-real-time, performance-intensive and costly since it will use Read Capacity Units (RCU)

The events can be subscribed by a Lambda function, its resulting data patterns extracted in real-time without impacting Table performance or costs.

Option C is incorrect.

Fault tolerance environment always ensures that catastrophic loss of resources like DataCenters or Availability zones will not result in application downtime resulting in 100% availability.

Fault tolerance mechanisms always have an Active-Active site failover mechanism where both the Primary and Backup resources are fully functional and operational.

Traffic is sent to both the sites, and in the event of failover, traffic will be routed to the available site.

Fault-Tolerant setups may have different scenarios like Disaster Recovery,Multi-AZ database setups exhibiting redundancy with 2 copies of data to ensure write availability and 3 copies of data to ensure read availability.

We may compare Fault Tolerance to an Aircraft analogy where the loss of an engine will still allow the plane to function without rectifying it, which won't be possible mid-air.

Option D is CORRECT.

Unlike automated backups, manual snapshots are taken by users when needed.

It is not an automation method.

References:

https://medium.com/@crishantha/aws-disaster-recovery-scenarios-1e8234109e79 https://aws.amazon.com/blogs/database/dynamodb-streams-use-cases-and-design-patterns/#:~:text=DynamoDB%20Streams%20is%20a%20powerful,for%20up%20to%2024%20hours. https://youtu.be/OjppS4RWWt8

The option that does NOT provide automation capabilities among the AWS resources or features listed is D. RDS manual snapshot.

Here's a detailed explanation of each option:

A. Elastic Beanstalk: Elastic Beanstalk is a fully managed service provided by AWS that helps deploy and manage applications in a variety of programming languages such as Java, .NET, PHP, Node.js, Python, Ruby, and Go. It provides automation capabilities for deploying, scaling, monitoring, and updating applications.

B. DynamoDB: DynamoDB is a managed NoSQL database service provided by AWS. It provides automation capabilities for scaling, backup and recovery, and replication across multiple regions.

C. Fault Tolerance: Fault Tolerance is a characteristic of a system that can continue to operate properly in the event of the failure of one or more components. AWS provides automation capabilities for achieving fault tolerance by using services like Elastic Load Balancing, Auto Scaling, and AWS Lambda.

D. RDS manual snapshot: RDS (Relational Database Service) is a managed database service provided by AWS that supports various database engines such as MySQL, PostgreSQL, Oracle, and SQL Server. While RDS provides automation capabilities for many tasks such as database provisioning, backups, and software patching, manual snapshot creation is not automated.

In summary, all the options except for D provide automation capabilities. Elastic Beanstalk provides automation for deploying, scaling, monitoring, and updating applications. DynamoDB provides automation for scaling, backup and recovery, and replication. Fault Tolerance provides automation capabilities for achieving system reliability in the event of failures. RDS manual snapshots, on the other hand, do not provide automation capabilities.