050-80-CASECURID01 · Question #69
When using the "Resynchronize Token" function, after an administrator enters two consecutive tokencodes, the token clock time is displayed.
The correct answer is B. True. See the full explanation below for the reasoning.
Question
When using the “Resynchronize Token” function, after an administrator enters two consecutive tokencodes, the token clock time is displayed.
Options
- AFalse
- BTrue
How the community answered
(18 responses)- A28% (5)
- B72% (13)
Community Discussion
4
Dragan B.Feb 19, 2026The answer is B, True, and it makes sense once you understand what the resync process is actually doing under the hood. RSA Authentication Manager needs two consecutive tokencodes precisely because the algorithm uses the time-based drift between them to calculate where the token's internal clock currently sits relative to the server. After you feed those two codes in, the system resolves the offset and surfaces the token clock time so the administrator can confirm the drift value and verify the resync took effect. If you have ever pulled RADIUS authentication logs during a resync event, you will see the server logging that clock calculation before it accepts the next authentication attempt. Candidates who answer False are probably thinking of a PIN reset or a different administrative function, not the resync workflow, so keep the steps straight.
Anjali D.Feb 27, 2026Yep, B is right on this one. After the admin enters those two consecutive tokencodes during resync, the system does display the token clock time, which is exactly how it confirms the drift has been calculated and corrected so the token and server are back in sync.
Yusuf A.Feb 28, 2026Right, and the senior I shadow always emphasizes that you need those two consecutive codes specifically because one alone only tells the server the current value, while the second one lets it calculate the actual drift interval and lock in the corrected offset for future authentications.
Yusuf A.Mar 3, 2026Yeah this one tripped me up at first but I went back and looked at the RSA Authentication Manager admin guide after my senior walked me through a resync on a real token last week. The answer is True, B. When the admin enters those two back-to-back tokencodes, the system uses them to calculate the drift between the token hardware clock and the server clock, and then it surfaces the token clock time so the admin can confirm the resync actually took effect and see how far out of alignment it was. It makes sense if you think about it, because entering two consecutive codes gives the server enough of a pattern to figure out exactly where in the time window the token thinks it is. My question is, does the displayed clock time reflect the token's raw hardware time, or is it already the corrected value after the server applies the offset? I am guessing it shows the token's current time as the server now understands it, but I want to make sure I am not confusing that with what you would see before the resync completes.