Q: 16
A company hosts its primary API on AWS using Amazon API Gateway and AWS Lambda functions.
Internal applications and external customers use this API. Some customers also use a legacy API
hosted on a standalone EC2 instance.
The company wants to increase security across all APIs to prevent denial of service (DoS) attacks,
check for vulnerabilities, and guard against common exploits.
What should a solutions architect do to meet these requirements?
Options
Discussion
Call it C here. WAF handles API Gateway, Inspector checks the legacy EC2-based API, and GuardDuty is all about monitoring, not blocking. The blocking language in D doesn't line up with how GuardDuty actually works. Anyone see it differently?
D imo, but honestly C also looks good here.
C/D? Had something like this in a mock, but the GuardDuty part throws me off. C mentions monitoring which matches what GuardDuty actually does (it doesn't block), but D says it blocks. Pretty sure it's C from what I've seen, but not 100%.
Its C, saw a similar question in practice where WAF goes with API Gateway, Inspector for EC2, GuardDuty just monitors.
Be respectful. No spam.
Question 16 of 35