New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe AD0-E123 Exam - Topic 1 Question 14 Discussion

Actual exam question for Adobe's AD0-E123 exam
Question #: 14
Topic #: 1
[All AD0-E123 Questions]

A developer would like to view page transaction response times. Which log file would they use?

Show Suggested Answer Hide Answer
Suggested Answer: B

The request log in AEM records details about requests processed by the AEM instance, including transaction response times. This log is useful for developers when they need to analyze the performance of page requests, including how long each page takes to load. The request log can typically be found in the logs directory of the AEM installation and may be named request.log.

stdout.log typically contains the standard output of the AEM process and is not specific to request transactions.

audit.log is used to log user actions for auditing purposes and does not include transaction response times.


Contribute your Thoughts:

0/2000 characters
Dana
3 months ago
Wait, are we sure about that? Sounds a bit off.
upvoted 0 times
...
Mary
3 months ago
Yeah, request log makes the most sense.
upvoted 0 times
...
Ines
3 months ago
Audit log is for security, not response times.
upvoted 0 times
...
Cary
4 months ago
I thought it was stdout.log?
upvoted 0 times
...
Anastacia
4 months ago
Definitely the request log!
upvoted 0 times
...
Daniel
4 months ago
Audit.log sounds familiar, but I don't think it tracks response times. It seems more focused on security and access logs.
upvoted 0 times
...
Jennifer
4 months ago
I feel like I've seen practice questions where the request log was mentioned for performance metrics. That could be it.
upvoted 0 times
...
Dortha
4 months ago
I'm not entirely sure, but I remember something about stdout.log being used for general output, not specifically for transaction times.
upvoted 0 times
...
Stevie
5 months ago
I think the request log might be the right choice since it usually tracks all incoming requests and their response times.
upvoted 0 times
...
Krissy
5 months ago
I'm a bit confused on this one. I'll need to think it through carefully to make sure I select the correct log file.
upvoted 0 times
...
Lezlie
5 months ago
Hmm, I'm not sure about this one. I'd have to double-check the documentation to see which log file would have the information I need.
upvoted 0 times
...
Goldie
5 months ago
I think the request log would be the best place to look for page transaction response times. That's where I'd expect to find that kind of performance data.
upvoted 0 times
...
Lynda
5 months ago
The request log sounds like the right choice here. That's where I'd start looking for that kind of data.
upvoted 0 times
...
Annamaria
5 months ago
Option A seems promising - having a warm pool of stopped instances could help speed up the launch process. I'll need to think through the logistics of that approach.
upvoted 0 times
...
Dallas
5 months ago
Hmm, this looks like a tricky one. I think I'll try to Debug Matching first to see if that can fix the issue with the changed web page hierarchy.
upvoted 0 times
...
Malcom
5 months ago
I'm a bit confused on this one. Is it the Executing group or the Monitoring & Controlling group that typically consumes the most budget? I'll have to review my notes to be sure.
upvoted 0 times
...
Teri
5 months ago
The question mentions the view needs to be viewable by all users, so I'm guessing the Templates area is the right place to create it. I feel pretty confident about that.
upvoted 0 times
...
Sherman
2 years ago
I believe the audit.log might also contain information about page transaction response times.
upvoted 0 times
...
Cheryl
2 years ago
I agree with Nicholle, the request log would show the page transaction response times.
upvoted 0 times
...
Desiree
2 years ago
Forget the logs, I just use my trusty crystal ball to monitor page response times. Much more reliable than any boring old log file.
upvoted 0 times
Jamal
2 years ago
C) audit.log
upvoted 0 times
...
Gail
2 years ago
B) request log
upvoted 0 times
...
Lucina
2 years ago
A) stdout.log
upvoted 0 times
...
Tegan
2 years ago
A: Forget the logs, I just use my trusty crystal ball to monitor page response times.
upvoted 0 times
...
Nadine
2 years ago
B: Actually, the audit.log would be the best log file to use for that.
upvoted 0 times
...
Junita
2 years ago
A: I think you should use the request log to view page transaction response times.
upvoted 0 times
...
...
Dominque
2 years ago
This is a no-brainer. The request log is where all the juicy performance data lives. Gotta love that log file!
upvoted 0 times
Monroe
2 years ago
Agreed, the request log is where all the performance data is stored.
upvoted 0 times
...
Aron
2 years ago
The request log is definitely the one to check for page transaction response times.
upvoted 0 times
...
Renay
2 years ago
C) audit.log
upvoted 0 times
...
Darrin
2 years ago
B) request log
upvoted 0 times
...
Jarod
2 years ago
A) stdout.log
upvoted 0 times
...
...
Nicholle
2 years ago
I think the developer would use the request log.
upvoted 0 times
...
Mauricio
2 years ago
Hmm, I'm not sure about this one. Isn't the audit log for security-related events? Seems like the request log is the way to go.
upvoted 0 times
...
Pearlie
2 years ago
I'm going with B. The request log is the place to look for that kind of performance data.
upvoted 0 times
Delsie
2 years ago
I think C) audit.log might also have some relevant data.
upvoted 0 times
...
Polly
2 years ago
I agree, the request log is where you would find that information.
upvoted 0 times
...
...
Vallie
2 years ago
The request log seems like the obvious choice here. That's where I'd expect to find the page transaction response times.
upvoted 0 times
Sabrina
2 years ago
Yes, the request log is the right log file to check for page transaction response times.
upvoted 0 times
...
Tyra
2 years ago
I agree, the request log is where you would find that information.
upvoted 0 times
...
...

Save Cancel