Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Platform Developer II Topic 1 Question 97 Discussion

Actual exam question for Salesforce's Platform Developer II exam
Question #: 97
Topic #: 1
[All Platform Developer II Questions]

Which Salesforce feature allows a developer to see when a user last logged in to

Salesforce if real-time notification is not required?

Show Suggested Answer Hide Answer
Suggested Answer: A, B

Contribute your Thoughts:

Arlette
1 months ago
Forget the Event Monitoring Log, I'm all about the User Seance Log. That's where you can commune with the spirits of past Salesforce users and find out their login history. Totally legit, trust me.
upvoted 0 times
Lizette
16 days ago
A) Calendar Events
upvoted 0 times
...
...
Cecily
1 months ago
Ah, the age-old question: how to stalk your users without them knowing. The Event Monitoring Log is the answer, my friends. Just don't forget to install hidden cameras for the full experience.
upvoted 0 times
Rosita
11 days ago
Yeah, it's a useful feature for tracking user activity.
upvoted 0 times
...
Alida
16 days ago
I didn't know that, thanks for the info!
upvoted 0 times
...
Delpha
17 days ago
Event Monitoring Log allows you to see user login history.
upvoted 0 times
...
...
Tori
2 months ago
Asynchronous Data Capture Events? What is this, a trick question? I'm sticking with the Event Monitoring Log.
upvoted 0 times
Melissia
1 months ago
Yeah, Developer Log is more for debugging purposes, Event Monitoring Log is the way to go.
upvoted 0 times
...
Raelene
1 months ago
I agree, Event Monitoring Log is the correct choice for seeing when a user last logged in.
upvoted 0 times
...
Gennie
1 months ago
I think Asynchronous Data Capture Events is a distraction, I'm going with Event Monitoring Log.
upvoted 0 times
...
...
Anna
2 months ago
I bet the calendar events would have some information about when users logged in, but that's not what the question is asking for. Gotta go with C on this one.
upvoted 0 times
Portia
22 hours ago
Definitely C) Event Monitoring Log, it's the most suitable for this scenario.
upvoted 0 times
...
Gwenn
11 days ago
I would go with C) Event Monitoring Log as well.
upvoted 0 times
...
Coleen
20 days ago
Yeah, I agree. It's the best option for tracking user logins.
upvoted 0 times
...
Kaycee
2 months ago
I think it's C) Event Monitoring Log.
upvoted 0 times
...
...
Pearline
2 months ago
Developer Log? Really? That's for debugging our own code, not tracking user activity. I think C is the way to go.
upvoted 0 times
Gladys
1 months ago
Yeah, Developer Log is not meant for tracking user logins. Event Monitoring Log is the right choice.
upvoted 0 times
...
Alida
2 months ago
I agree, Event Monitoring Log is the feature we need to track user activity.
upvoted 0 times
...
...
Alverta
2 months ago
Hmm, the Event Monitoring Log seems like the most logical choice here. That's where I'd expect to find user login information.
upvoted 0 times
Hermila
21 days ago
I would go with the Event Monitoring Log as well, it seems like the most relevant choice for this scenario.
upvoted 0 times
...
Lazaro
30 days ago
Yeah, the Event Monitoring Log is designed for tracking user activity, so it makes sense to check there first.
upvoted 0 times
...
Ryan
1 months ago
I think the Developer Log might also have that information, but the Event Monitoring Log is probably more specific.
upvoted 0 times
...
Jamal
2 months ago
I agree, the Event Monitoring Log is the best option for tracking user logins.
upvoted 0 times
...
...
Edna
2 months ago
I'm not sure, but I think D) Developer Log could also be a possibility.
upvoted 0 times
...
Freeman
2 months ago
I agree with Derick, Event Monitoring Log makes sense for tracking user logins.
upvoted 0 times
...
Derick
3 months ago
I think the answer is C) Event Monitoring Log.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77