220-1002 · Question #658
A user's company phone was recently wiped. The user Is unsure if an IT administrator wiped the phone or if it was the result of a hacking attempt. A new company policy was recently implemented to…
The correct answer is A. Unauthorized remote access. The stated answer (A: Unauthorized remote access) is unlikely given the context clues. The new policy explicitly includes 'Failed-attempt device wiping,' and the user 'keeps the phone in a pocket' - pocket pressure and accidental touches are a well-known cause of repeated…
Question
A user's company phone was recently wiped. The user Is unsure if an IT administrator wiped the phone or if it was the result of a hacking attempt. A new company policy was recently implemented to tighten security. The new policy requirements include:
- An allowance for the remote wiping of company data
- PIN unlock
- Failed-attempt device wiping
The user normally keeps the phone in a pocket, so it is unlikely that anyone else had access to It. Which of the following is the MOST likely cause of the device being wiped?
Options
- AUnauthorized remote access
- BA system lockout
- CA virus
- DA faulty device
How the community answered
(33 responses)- A85% (28)
- B3% (1)
- C3% (1)
- D9% (3)
Explanation
The stated answer (A: Unauthorized remote access) is unlikely given the context clues. The new policy explicitly includes 'Failed-attempt device wiping,' and the user 'keeps the phone in a pocket' - pocket pressure and accidental touches are a well-known cause of repeated failed PIN entry attempts. Once the failed-attempt threshold is hit, the policy automatically wipes the device. This points to B) A system lockout as the most likely cause. The question also notes it is 'unlikely that anyone else had access' to the phone, which weakens the case for unauthorized remote access (A). A virus (C) does not typically trigger a clean device wipe. A faulty device (D) would show other symptoms. This appears to be an error in the answer key; the correct answer is B.
Topics
Community Discussion
No community discussion yet for this question.