Question 370
To avoid following fraudulent sign-in destinations encoded in printed QR tags, what is the most direct option?
- Bluetooth discovery restriction
- Tethering restrictions
- NFC payment and pairing policy
- QR-code phishing checks
- Location permission minimization
Explanation
Correct Answer
D:URL inspection and trusted app flows prevent QR content from bypassing ordinary link scrutiny; the requested outcome is precisely to avoid following fraudulent sign-in destinations encoded in printed QR tags.
Incorrect Answers
A:Disabling discoverability limits opportunities for unknown nearby devices to initiate connections; that is useful when the task is to reduce unsolicited pairing exposure on sensitive mobile devices, not the stated requirement to avoid following fraudulent sign-in destinations encoded in printed QR tags.
B:Disabling personal hotspots limits unapproved network paths and bypass of enterprise connectivity policy; a team would select it to stop a managed phone creating an unmanaged bridge to a secure laptop, which does not provide the particular result to avoid following fraudulent sign-in destinations encoded in printed QR tags.
C:Platform capability policy can limit short-range communications that the business does not require; its operational purpose is to restrict near-field transactions on tightly controlled field equipment, not to achieve the specific requirement to avoid following fraudulent sign-in destinations encoded in printed QR tags.
E:Permission and privacy settings restrict tracking beyond legitimate operational requirements; it addresses the different need to reduce unnecessary collection of employees' precise geographic data, leaving the requested ability to avoid following fraudulent sign-in destinations encoded in printed QR tags unresolved.
Question 371
To stop a managed phone creating an unmanaged bridge to a secure laptop, what should defenders select?
- Location permission minimization
- Nearby-share disablement
- Tethering restrictions
- Mobile DNS filtering
Explanation
Correct Answer
C:Disabling personal hotspots limits unapproved network paths and bypass of enterprise connectivity policy; this choice fits the scenario because the team must stop a managed phone creating an unmanaged bridge to a secure laptop.
Incorrect Answers
A:Permission and privacy settings restrict tracking beyond legitimate operational requirements; it could help someone trying to reduce unnecessary collection of employees' precise geographic data, but the problem is instead to stop a managed phone creating an unmanaged bridge to a secure laptop.
B:Platform sharing policies can narrow ad hoc content transfer outside approved enterprise channels; that is useful when the task is to prevent uncontrolled local file exchange from managed mobile devices, not the stated requirement to stop a managed phone creating an unmanaged bridge to a secure laptop.
D:Device or app-level secure resolver policy extends name-based controls to roaming networks; its operational purpose is to prevent managed phones resolving known malicious domains off corporate Wi-Fi, not to achieve the specific requirement to stop a managed phone creating an unmanaged bridge to a secure laptop.
Question 372
To reduce unnecessary collection of employees' precise geographic data, which mechanism best fits?
- Mobile DNS filtering
- Cellular roaming policy
- Nearby-share disablement
- Location permission minimization
Explanation
Correct Answer
D:Permission and privacy settings restrict tracking beyond legitimate operational requirements; this mechanism directly supports the requirement to reduce unnecessary collection of employees' precise geographic data.
Incorrect Answers
A:Device or app-level secure resolver policy extends name-based controls to roaming networks; although relevant to prevent managed phones resolving known malicious domains off corporate Wi-Fi, it does not by itself achieve the required task to reduce unnecessary collection of employees' precise geographic data.
B:Managed roaming settings restrict unapproved mobile-network use without changing application encryption; it could help someone trying to control data exposure and operational costs when phones cross countries, but the problem is instead to reduce unnecessary collection of employees' precise geographic data.
C:Platform sharing policies can narrow ad hoc content transfer outside approved enterprise channels; that is useful when the task is to prevent uncontrolled local file exchange from managed mobile devices, not the stated requirement to reduce unnecessary collection of employees' precise geographic data.
Question 373
To prevent uncontrolled local file exchange from managed mobile devices, which measure best meets the requirement?
- Tethering restrictions
- Nearby-share disablement
- NFC payment and pairing policy
- Mobile DNS filtering
Explanation
Correct Answer
B:Platform sharing policies can narrow ad hoc content transfer outside approved enterprise channels; it supplies the specific control needed to prevent uncontrolled local file exchange from managed mobile devices.
Incorrect Answers
A:Disabling personal hotspots limits unapproved network paths and bypass of enterprise connectivity policy; the outcome it supports is to stop a managed phone creating an unmanaged bridge to a secure laptop, whereas this scenario asks defenders to prevent uncontrolled local file exchange from managed mobile devices.
C:Platform capability policy can limit short-range communications that the business does not require. This can help to restrict near-field transactions on tightly controlled field equipment, but it does not provide the particular mechanism required to prevent uncontrolled local file exchange from managed mobile devices.
D:Device or app-level secure resolver policy extends name-based controls to roaming networks; that is useful when the task is to prevent managed phones resolving known malicious domains off corporate Wi-Fi, not the stated requirement to prevent uncontrolled local file exchange from managed mobile devices.
Question 374
To reduce unnecessary collection of employees' precise geographic data, to prevent uncontrolled local file exchange from managed mobile devices, and to identify handsets exposing outdated or unnecessary wireless interfaces, which THREE measures should the team select? Choose THREE.
- QR-code phishing checks
- Device radio inventory
- Nearby-share disablement
- Mobile DNS filtering
- Tethering restrictions
- Location permission minimization
Explanation
Correct Answers
B:Asset telemetry reveals Bluetooth, Wi-Fi and cellular capabilities requiring policy management; it satisfies the distinct requirement to identify handsets exposing outdated or unnecessary wireless interfaces within the multi-control task.
C:Platform sharing policies can narrow ad hoc content transfer outside approved enterprise channels; it satisfies the distinct requirement to prevent uncontrolled local file exchange from managed mobile devices within the multi-control task.
F:Permission and privacy settings restrict tracking beyond legitimate operational requirements; it satisfies the distinct requirement to reduce unnecessary collection of employees' precise geographic data within the multi-control task.
Incorrect Answers
A:URL inspection and trusted app flows prevent QR content from bypassing ordinary link scrutiny; its mechanism supports avoid following fraudulent sign-in destinations encoded in printed QR tags, while the requested control must be able to reduce unnecessary collection of employees' precise geographic data, to prevent uncontrolled local file exchange from managed mobile devices, and to identify handsets exposing outdated or unnecessary wireless interfaces.
D:Device or app-level secure resolver policy extends name-based controls to roaming networks; it could help someone trying to prevent managed phones resolving known malicious domains off corporate Wi-Fi, but the problem is instead to reduce unnecessary collection of employees' precise geographic data, to prevent uncontrolled local file exchange from managed mobile devices, and to identify handsets exposing outdated or unnecessary wireless interfaces.
E:Disabling personal hotspots limits unapproved network paths and bypass of enterprise connectivity policy; that is useful when the task is to stop a managed phone creating an unmanaged bridge to a secure laptop, not the stated requirement to reduce unnecessary collection of employees' precise geographic data, to prevent uncontrolled local file exchange from managed mobile devices, and to identify handsets exposing outdated or unnecessary wireless interfaces.
Question 375
To contain immediate exposure after a reported missing mobile phone, what control should be selected?
- Mobile token revocation
- Device retirement workflow
- SIM-swap risk mitigation
- Mobile incident triage
- Lost-device lock
Explanation
Correct Answer
E:Remote lock restricts local access while responders assess wipe, recovery and credential revocation; its relevant protective or investigative effect is to contain immediate exposure after a reported missing mobile phone.
Incorrect Answers
A:Revoking tokens and sessions stops cloud access even when the device cannot yet receive commands; the technique works for situations involving invalidate authentication sessions when a phone is stolen, rather than this need to contain immediate exposure after a reported missing mobile phone.
B:Sanitization and inventory closure prevent residual enterprise data on reassigned hardware; its mechanism supports remove management profiles and corporate content before a handset is disposed, while the requested control must be able to contain immediate exposure after a reported missing mobile phone.
C:Phishing-resistant authenticators and carrier protections lessen dependence on SMS-based recovery; the outcome it supports is to reduce account takeover when an attacker gains control of a phone number, whereas this scenario asks defenders to contain immediate exposure after a reported missing mobile phone.
D:Controlled collection and escalation weigh evidence retention against containment and privacy duties; although relevant to preserve volatile device state when a suspected app compromise is reported, it does not by itself achieve the required task to contain immediate exposure after a reported missing mobile phone.
Question 376
To invalidate authentication sessions when a phone is stolen, which security control is most appropriate?
- Device retirement workflow
- Lost-device lock
- SIM-swap risk mitigation
- Mobile token revocation
Explanation
Correct Answer
D:Revoking tokens and sessions stops cloud access even when the device cannot yet receive commands; the requested outcome is precisely to invalidate authentication sessions when a phone is stolen.
Incorrect Answers
A:Sanitization and inventory closure prevent residual enterprise data on reassigned hardware; it addresses the different need to remove management profiles and corporate content before a handset is disposed, leaving the requested ability to invalidate authentication sessions when a phone is stolen unresolved.
B:Remote lock restricts local access while responders assess wipe, recovery and credential revocation; the technique works for situations involving contain immediate exposure after a reported missing mobile phone, rather than this need to invalidate authentication sessions when a phone is stolen.
C:Phishing-resistant authenticators and carrier protections lessen dependence on SMS-based recovery; its mechanism supports reduce account takeover when an attacker gains control of a phone number, while the requested control must be able to invalidate authentication sessions when a phone is stolen.
Question 377
To remove management profiles and corporate content before a handset is disposed, what would a mobile security administrator implement or use?
- Push MFA fatigue protection
- Lost-device lock
- Mobile token revocation
- Device retirement workflow
Explanation
Correct Answer
D:Sanitization and inventory closure prevent residual enterprise data on reassigned hardware; this choice fits the scenario because the team must remove management profiles and corporate content before a handset is disposed.
Incorrect Answers
A:Number matching and contextual prompts make blind approval more difficult than one-tap acceptance; applying it would serve stop repeated login prompts being accepted reflexively on mobile devices without directly satisfying the goal to remove management profiles and corporate content before a handset is disposed.
B:Remote lock restricts local access while responders assess wipe, recovery and credential revocation; it addresses the different need to contain immediate exposure after a reported missing mobile phone, leaving the requested ability to remove management profiles and corporate content before a handset is disposed unresolved.
C:Revoking tokens and sessions stops cloud access even when the device cannot yet receive commands; the technique works for situations involving invalidate authentication sessions when a phone is stolen, rather than this need to remove management profiles and corporate content before a handset is disposed.
Question 378
To reduce account takeover when an attacker gains control of a phone number, which practice addresses that objective?
- Mobile token revocation
- Managed certificate revocation
- Device retirement workflow
- SIM-swap risk mitigation
Explanation
Correct Answer
D:Phishing-resistant authenticators and carrier protections lessen dependence on SMS-based recovery; this mechanism directly supports the requirement to reduce account takeover when an attacker gains control of a phone number.
Incorrect Answers
A:Revoking tokens and sessions stops cloud access even when the device cannot yet receive commands; its operational purpose is to invalidate authentication sessions when a phone is stolen, not to achieve the specific requirement to reduce account takeover when an attacker gains control of a phone number.
B:PKI revocation and access-policy updates stop relying on a stolen or untrusted credential; applying it would serve revoke a device identity certificate after a reported compromise without directly satisfying the goal to reduce account takeover when an attacker gains control of a phone number.
C:Sanitization and inventory closure prevent residual enterprise data on reassigned hardware; it addresses the different need to remove management profiles and corporate content before a handset is disposed, leaving the requested ability to reduce account takeover when an attacker gains control of a phone number unresolved.
Question 379
To stop repeated login prompts being accepted reflexively on mobile devices, which tool, policy, or technique is appropriate?
- Device retirement workflow
- Mobile incident triage
- Managed certificate revocation
- Push MFA fatigue protection
Explanation
Correct Answer
D:Number matching and contextual prompts make blind approval more difficult than one-tap acceptance; it supplies the specific control needed to stop repeated login prompts being accepted reflexively on mobile devices.
Incorrect Answers
A:Sanitization and inventory closure prevent residual enterprise data on reassigned hardware; a team would select it to remove management profiles and corporate content before a handset is disposed, which does not provide the particular result to stop repeated login prompts being accepted reflexively on mobile devices.
B:Controlled collection and escalation weigh evidence retention against containment and privacy duties; its operational purpose is to preserve volatile device state when a suspected app compromise is reported, not to achieve the specific requirement to stop repeated login prompts being accepted reflexively on mobile devices.
C:PKI revocation and access-policy updates stop relying on a stolen or untrusted credential; applying it would serve revoke a device identity certificate after a reported compromise without directly satisfying the goal to stop repeated login prompts being accepted reflexively on mobile devices.
Question 380
To preserve volatile device state when a suspected app compromise is reported, what safeguard would be most applicable?
- Mobile token revocation
- Managed certificate revocation
- Mobile incident triage
- Push MFA fatigue protection
- Conditional access to SaaS
- Compliance remediation notice
Explanation
Correct Answer
C:Controlled collection and escalation weigh evidence retention against containment and privacy duties; that is why it addresses the operational task to preserve volatile device state when a suspected app compromise is reported.
Incorrect Answers
A:Revoking tokens and sessions stops cloud access even when the device cannot yet receive commands; that is useful when the task is to invalidate authentication sessions when a phone is stolen, not the stated requirement to preserve volatile device state when a suspected app compromise is reported.
B:PKI revocation and access-policy updates stop relying on a stolen or untrusted credential; a team would select it to revoke a device identity certificate after a reported compromise, which does not provide the particular result to preserve volatile device state when a suspected app compromise is reported.
D:Number matching and contextual prompts make blind approval more difficult than one-tap acceptance; applying it would serve stop repeated login prompts being accepted reflexively on mobile devices without directly satisfying the goal to preserve volatile device state when a suspected app compromise is reported.
E:Access policy combines sign-in identity with application and posture context rather than trusting passwords alone; it addresses the different need to require approved mobile app and healthy device before opening business documents, leaving the requested ability to preserve volatile device state when a suspected app compromise is reported unresolved.
F:Managed notifications give actionable steps while conditional access continues protecting the service; the technique works for situations involving guide users to fix a phone that fails the minimum patch policy, rather than this need to preserve volatile device state when a suspected app compromise is reported.