How does AWS charge for AWS Lambda usage once the free tier has been exceeded? (choose two)

AWS Lambda charges are based on two primary factors: the number of requests made to the functions and the duration of the code execution.

When the free tier limit is surpassed, billing begins with the count of requests. AWS Lambda counts a request every time a function is invoked, and whether it’s short or long-lived, each interaction will contribute to the overall usage. This means that as the frequency of function invocations increases, so does the total charge based on the number of requests.

In addition to requests, AWS Lambda also charges for the duration of code execution, which measures how long your code runs in milliseconds. This is based on the time taken from when the code begins executing until it returns or otherwise terminates. Thus, both the count of requests and the duration of execution are essential metrics in calculating the total cost of using AWS Lambda services beyond the free tier.

Options that mentioned memory allocation and the number of AWS accounts do not directly influence the billing structure. While memory allocation can impact how long code runs and thus the billing indirectly tied to duration, it is not a primary factor for charges by itself. The number of AWS accounts is unrelated to Lambda usage and billing.