Exam AWS Certified Developer Associate topic 1 question 26 discussion

Answer A When Lambda runs your function, it passes a context object to the handler. This object provides methods and properties that provide information about the invocation, function, and execution environment. Context methods getRemainingTimeInMillis() – Returns the number of milliseconds left before the execution times out. Context properties functionName – The name of the Lambda function. functionVersion – The version of the function. invokedFunctionArn – The Amazon Resource Name (ARN) that's used to invoke the function. Indicates if the invoker specified a version number or alias. memoryLimitInMB – The amount of memory that's allocated for the function. awsRequestId – The identifier of the invocation request.

A is the answer Each service that integrates with Lambda sends data to your function in JSON as an event. The structure of the event document is different for each event type, and contains data about the resource or request that triggered the function. Lambda runtimes convert the event into an object and pass it to your function.

Each invocation of a Lambda function may run on a new container instance. The local file system (/tmp) is the only writable directory, but it: Is cleared out when the Lambda container is terminated or reused for another invocation.

A) Correct - Each AWS Lambda invocation has a unique request identifier (aws_request_id) that can be obtained from the Lambda context object (context.aws_request_id). Logs written to the console are automatically captured and sent to Amazon CloudWatch Logs by the Lambda service. No additional file handling is required, ensuring simplicity.

Lambda event object doesn't provide unique identifier Writing logs to a file is not practical in a Lambda environment, as Lambda functions are stateless and ephemeral, meaning any files written to the local filesystem are not persistent.

AAAAAAAA

i will go with A

Answer A because: While Lambda supports writing logs to files, logging to the console offers distinct advantages: - Integration with CloudWatch Logs: Lambda automatically forwards console logs to CloudWatch Logs, providing centralized logging and monitoring. - Efficiency and Scalability: Lambda manages console logging, avoiding overhead and ensuring scalability. - Querying and Filtering: CloudWatch Logs allows you to query and filter logs based on the request identifier, making it easy to track events for specific invocations.

considering the best practices for logging and persisting logs associated with Lambda function

D. Obtain the request identifier from the Lambda context object. Architect the application to write logs to a file. Explanation: Lambda Context Object: The Lambda context object contains information about the invocation, including a unique identifier for the request. This identifier can be used to associate events with a specific function invocation. Write Logs to a File: Writing logs to a file is a common practice in Lambda functions, as it allows for persistent storage of logs that can be later analyzed. This is more suitable for production scenarios compared to writing logs to the console, which might not persist after the function execution.

The default file options available to Lambda are temporary, and there's no mention of configuring any advanced storage system. Nor is it necessary - CloudWatch will just automatically collect output from Lambda STDOUT, providing optimal management and processing options inherently.

Obtaining Request Identifier from Lambda Context Object: The Lambda context object includes a unique request ID, which can be used to associate events with a specific function invocation. Writing Logs to the Console: Writing logs to the console (stdout) within a Lambda function is a common practice. These console logs can be captured and persisted using AWS CloudWatch Logs, making them accessible for later analysis and troubleshooting.

It's A, not D. writing logs to a file is not recommended for Lambda functions because the file system of a Lambda execution environment is ephemeral and not persisted across invocations.

It is context that will add data to console or standard output, cause saving to file just adds overhead but output can anyways be seen or saved from cloudwatch if needed

Both A & D seems correct. Actually D seems more relevant as it will contain only function logs which app is stroring instead of CloudWatch logs which contains Lambda default start execution logs as well. But still I want to go with A as storing to file in S3 will require additional IAM Role attached to Lambda execution role and question has just mention what will just work so.

The correct answer is D. Obtain the request identifier from the Lambda context object. Architect the application to write logs to a file. AWS Lambda provides a context object that contains information about the runtime environment and the current function invocation. The context object includes a unique identifier called the "request identifier" or "request ID." This identifier can be obtained from the context object and used to associate the events with a specific function invocation. To accomplish the objective of logging key events with a unique identifier, the developer should obtain the request identifier from the Lambda context object. Additionally, the developer should architect the application to write logs to a file, rather than just writing them to the console. Writing logs to a file allows for better log management and enables additional analysis and processing of the logs. Therefore, option D is the correct choice: Obtain the request identifier from the Lambda context object and architect the application to write logs to a file.

CloudWatch will collect the output from console.