Exam AWS Certified Developer - Associate DVA-C02 topic 1 question 45 discussion

Both A and D could work here, as both rely on the context object to get access to execution ID https://docs.aws.amazon.com/us_en/lambda/latest/dg/python-context.html While A uses stoud to send log to CloudWatch Log, D writes to a file. D is less specific (where is the file stored? A single file for each execution?) and looks more comples (manage file(s), manage concurrency access to the file ...), thus I'll go for A

A https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.html https://docs.aws.amazon.com/lambda/latest/dg/nodejs-logging.html There is no explicit information for the runtime, the code is written in Node.js.

https://docs.aws.amazon.com/lambda/latest/dg/getting-started.html

A) Correct - The context object contains the AWS request ID, which uniquely identifies each function invocation. Writing logs to standard output ensures they are automatically captured by CloudWatch Logs. B) Eliminated - The event object contains input data passed to the Lambda function but does not include the AWS request ID. Writing logs to a file is not practical in Lambda because the filesystem is ephemeral, and logs stored in files would not persist beyond the function invocation.

A is the correct answer.

A should work

See getAwsRequestId() at https://docs.aws.amazon.com/lambda/latest/dg/java-context.html

Tricky question. Sure A and D both can do, but... The question is: why we need to get the request identifier if we will write logs to CloudWatch? So, I will go with answer A.

I think it should be A. Also can anyone advise why the two answers are different ? https://www.examtopics.com/discussions/amazon/view/29007-exam-aws-certified-developer-associate-topic-1-question-26/

The Option A is correct because: The second argument is the context object. A context object is passed to your function by Lambda at runtime. This object provides methods and properties that provide information about the invocation, function, and runtime environment. https://docs.aws.amazon.com/lambda/latest/dg/python-handler.html

invocation is in the Context object, and loggging into Standard output, which goes into CloudWatch(more durable, more scalable, etc.), is generally better than using temporary Files

Selected Answer A: Handler function https://docs.aws.amazon.com/lambda/latest/dg/nodejs-handler.html Context object awsRequestId – The identifier of the invocation request. https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.html

In my opinion both options A and D can fulfill the requirement, since there is no requirement about any specific logging and monitoring tool I will go with defaults (A) because, simple is better than complex :)

The application can write logs to standard output or to a file. Standard output is the default destination for logs. Logs that are written to standard output are sent to Amazon CloudWatch Logs. Logs that are written to a file are stored on the Lambda function's execution environment.

Ans: D The code snippet provided in the question is obtaining the request identifier from the context.awsRequestId property, which is available in the context object provided to the Lambda function handler. Therefore, the correct option is: D. Obtain the request identifier from the AWS request ID field in the context object. Configure the application to write logs to a file. This option meets the requirement of logging key events and including a unique identifier to associate the events with a specific function invocation.

Why not D ? Writing logs to a file seems more appropriate than stdout

https://docs.aws.amazon.com/us_en/lambda/latest/dg/python-context.html https://docs.aws.amazon.com/us_en/lambda/latest/dg/python-logging.html