Question 450
A Lambda function is invoked over an AWS-managed runtime and exposes an overly broad IAM role. What outcome would MOST clearly confirm the approach works?
Explanation
Correct Answer
The function succeeds on approved operations and is denied unrelated service actions. This result is directly relevant because AWS manages execution infrastructure while customers grant what their workloads can access. The underlying AWS decision is: Narrow the function's execution-role permissions as a customer control. The ongoing safeguard is: Review permissions with each function release.
Incorrect Answers
Providing a managed key service does not remove the need for customer-defined access and rotation decisions. In this question, however, aWS manages execution infrastructure while customers grant what their workloads can access. The answer that meets the requirement is: The function succeeds on approved operations and is denied unrelated service actions.
Fargate abstracts server provisioning, but application images, secrets and permissions remain customer-controlled. In this question, however, aWS manages execution infrastructure while customers grant what their workloads can access. The answer that meets the requirement is: The function succeeds on approved operations and is denied unrelated service actions.
Managed RDS removes routine infrastructure and database-engine platform tasks from the customer's responsibility, subject to service features. In this question, however, aWS manages execution infrastructure while customers grant what their workloads can access. The answer that meets the requirement is: The function succeeds on approved operations and is denied unrelated service actions.