A newly deployed AWS Lambda function in a shared account is showing increased throttle metrics in CloudWatch. Which operationally efficient actions will reduce throttling? (Choose two.)

When a Lambda function experiences throttling, it means that the service is rejecting invocation requests because it has reached a concurrency limit. Allocating more reserved concurrency for the function directly addresses throttling by dedicating a specific amount of concurrency exclusively to that function, preventing other functions in the account from consuming its available concurrency. Requesting a service quota increase for account-level concurrency raises the total number of concurrent executions allowed for all Lambda functions within the account. This provides more overall capacity, reducing the likelihood of throttling for all functions, including the newly deployed one. Migrating to Amazon EKS is not a solution for Lambda throttling; it's a different compute service. Increasing the maximum age of events in Lambda relates to event source mapping retry behavior, not concurrency limits. Adding lambda:GetFunctionConcurrency to the execution role is a permission for retrieving concurrency information, not for increasing it.