Q: 14
A company needs to scan all AWS Lambda functions for code vulnerabilities.
Options
Discussion
That one's B. No explanation needed here, Inspector Lambda scanning handles this.
Not D, it’s B. D is for runtime issues but the question wants code scanning.
Ugh, AWS naming drives me nuts, always sounds so similar. Probably B here.
D here. Lambda Protection sounds like it covers vulnerabilities, so I'd pick that for code scanning over Inspector. Maybe a trap but seems logical to me.
B makes sense since Inspector targets Lambda code itself, not just runtime stuff. Pretty sure that's what AWS intends for this scenario. Let me know if you see it differently.
Its B here, not D. D is a trap since it's more about runtime detection, Inspector does the actual code scanning.
B , Inspector is made for Lambda code scanning so fits the ask.
B tbh here. D looks attractive but that's for runtime threats, not code scanning. Seen similar on practice, B's correct.
Seen questions like this in official practice sets, always points to B.
Option D is tempting because GuardDuty sounds security-focused, but it's actually a trap. Inspector (B) does Lambda code vuln scans. Not 100 percent though, someone else might see it differently.
Be respectful. No spam.