ANS-C01 Question 326
Single answerYour organization uses AWS to host a multi-tier application, and you are tasked with automating network changes in response to specific events, such as changes in application load. The solution must ensure scalability, minimize manual intervention, and integrate seamlessly with AWS services. Which approach should you use to achieve event-driven network automation?
- A
Use Amazon CloudWatch Alarms to monitor application metrics and trigger AWS Lambda functions to modify network configurations.
- B
Manually configure network changes based on logs from Amazon CloudWatch Logs Insights.
- C
Use AWS Direct Connect to automatically scale bandwidth in response to application load changes.
- D
Implement a cron job on an EC2 instance to periodically check application load and adjust network configurations.
Show answer and explanation
Correct answer: A
Explanation
Event-driven network automation in AWS involves leveraging services like Amazon CloudWatch to monitor metrics and using AWS Lambda to act on those events. This ensures automated, scalable, and integrated responses to changes in application load or other defined triggers, minimizing manual intervention and operational overhead.
- A. Correct.
This is the correct answer. Amazon CloudWatch Alarms can monitor metrics such as CPU utilization or application latency, and trigger AWS Lambda functions to automate network changes, such as updating security groups or modifying route tables. This approach is event-driven, scalable, and minimizes manual intervention.
- B. Incorrect.
This option is incorrect because manually configuring network changes does not align with event-driven automation. It also introduces delays and potential human errors.
- C. Incorrect.
This option is incorrect because AWS Direct Connect is primarily used for establishing a dedicated private connection between on-premises networks and AWS. It does not automatically scale bandwidth or manage event-driven network automation.
- D. Incorrect.
This option is incorrect because a cron job on an EC2 instance involves periodic checks and manual script management, which is not truly event-driven. It also lacks the scalability and integration benefits of AWS-native services like CloudWatch and Lambda.