MENU
An administrator at AW Computing is trying to track the login history for a specific user. The AW Computing org has 150,000 users and multi-factor authentication (MFA) is enabled and enforced for all users. In reviewing the Identity Verification History data, the administrator is unable to find any information for the mentioned user. The user used to log in regularly but has been inactive this quarter.
Which two reasons explain why the user's data is missing from Identity Verification History?
Choose 2 answers
37 comments · newest first
CH
Chantell
11 months ago
C is definitely not true, they store way more than that!
WA
Walton
11 months ago
Wait, how can they not store data for inactive users? Seems odd!
LE
Leandro
12 months ago
B could be a reason too, some roles might not log that info.
RA
Raymon
12 months ago
Totally agree, that makes sense!
LA
Lashawn
1 year ago
A - Identity Verification History only keeps a year's worth of data.
FL
Florinda
1 year ago
I'm not entirely sure, but I feel like the inactivity of the user this quarter might mean their data is just not retained anymore.
LA
Laurel
1 year ago
I practiced a similar question where the number of records stored was mentioned. I wonder if that limit of 20,000 records could be a factor here.
MA
Malcom
1 year ago
I think there was something about roles affecting data storage in the Identity Verification History. Maybe that could explain why we can't see the user's info?
VE
Vesta
1 year ago
I remember reading that the Identity Verification History only keeps data for a certain time frame, but I can't recall if it's 6 months or a year.
JE
Jenelle
1 year ago
I feel pretty confident about this one. Based on the details provided, I think the most likely reasons are either that the Identity Verification History only stores the last year's worth of data or that it has a 6-month retention policy. I'll select those two options and move on to the next question.
EL
Elmer
1 year ago
Alright, let's break this down. The key information seems to be that the user used to log in regularly but has been inactive this quarter. That suggests the data might be older than the retention period. I'll start by considering the options related to data retention.
AN
Annabelle
1 year ago
I'm a bit confused here. The question doesn't provide much detail about the Identity Verification History, so I'm not sure what to focus on. I'll need to read through the options carefully and try to eliminate the less likely ones.
EL
Eleonora
1 year ago
Okay, let's see. The question mentions that MFA is enabled and enforced, so that's not the issue. Maybe it has something to do with the data retention policy or the user's role?
YO
Yolande
1 year ago
Hmm, this is a tricky one. I'll need to think carefully about the potential reasons why the user's data might be missing from the Identity Verification History.
SH
Shaniqua
1 year ago
Credit enhancements are an important topic, so I'll make sure to read each option closely and apply my understanding of the concept to determine which one is false.
LU
Luisa
1 year ago
I'm a bit stuck on this one. I know /etc/hosts is used for hostname resolution, but I can't recall the other file. I'll have to make an educated guess on the second answer.
TR
Trina
1 year ago
Maybe the user is secretly a time traveler and has been logging in from the future. That would definitely explain why their data is missing!
GL
Glennis
1 year ago
Haha, 20,000 records? That's cute. I bet the AW Computing org churns through that in a week. No wonder the admin is struggling to find this user's logs.
JE
Jeanice
1 year ago
B) User belongs to a specific role for which identity verification data is not stored.
JE
Jeniffer
1 year ago
Yeah, with 150,000 users, 20,000 records is not enough to track everyone.
TH
Thurman
1 year ago
C) Up to 20,000 records of users' identity verification attempts are stored.
SH
Sharen
1 year ago
A) Identity Verification History stores the last year's worth of data.
BR
Bronwyn
1 year ago
You know, I bet the user has been logging in with their phone's biometric security instead of the regular MFA. That might be why it's not showing up in the history.
BE
Bettina
1 year ago
B) User belongs to a specific role for which identity verification data is not stored.
GI
Gilma
1 year ago
A) Identity Verification History stores the last year's worth of data.
FR
Francine
1 year ago
Hold up, only 6 months of data? That's really not enough for a proper audit trail. I bet the admin is pulling their hair out trying to figure this one out.
NA
Nancey
1 year ago
A: Yeah, it must be frustrating for the admin to not have a complete login history.
MA
Martina
1 year ago
B: Or maybe the user's role doesn't require identity verification data to be stored.
BU
Buddy
1 year ago
A: Maybe the user's data got automatically purged after 6 months.
MI
Miss
2 years ago
Hmm, I'm not sure why the user's data is missing. Maybe they have a special role that doesn't get logged? Or perhaps the data only goes back a year - that seems a bit short, but who knows.
GO
Goldie
1 year ago
Perhaps the user's data is missing because the system only stores up to 20,000 records of identity verification attempts.
WI
Willard
1 year ago
I think the user's data might not be stored because the system only keeps the last 6 months of data.
HA
Han
1 year ago
It could be that the data only goes back a year, so older records are not available.
BE
Bev
2 years ago
Maybe the user belongs to a role that doesn't store identity verification data.
SI
Silva
2 years ago
I also think that the user's data is missing because they belong to a specific role for which identity verification data is not stored.
LE
Leatha
2 years ago
I agree with Leota. Maybe the user's data is not there because they have been inactive for this quarter.
LE
Leota
2 years ago
I think the user's data is missing because the Identity Verification History only stores the last 6 months of data.