Question 210
Linux kiosks must return to a vetted system configuration after each restart rather than accumulating untracked local administrator edits. Which Linux boot or persistence safeguard most directly addresses the issue?
- Restricted bootloader editing
- Full-disk encryption with LUKS
- Immutable configuration deployment
- UEFI Secure Boot
- Kernel module loading restrictions
Explanation
Correct Answer
C:Immutable or image-based deployment rebuilds from a controlled baseline, reducing configuration drift and persistence opportunities. State and updates need planned handling.
Incorrect Answers
A:Bootloader access controls and physical security can restrict unauthorized changes to boot parameters for situations characterized by unauthorized kernel command-line alteration; the case points instead to restoration of vetted baseline at restart.
B:LUKS protects block-device contents with encryption and managed unlocking secrets when the underlying evidence concerns confidentiality of powered-off Linux storage rather than the stated restoration of vetted baseline at restart.
D:Secure Boot verifies signed boot components against trusted keys when properly configured for situations characterized by verification of boot-time executable trust; the case points instead to restoration of vetted baseline at restart.
E:Kernel module restrictions reduce opportunities for runtime kernel extension; its distinguishing scope is prevention of late arbitrary kernel modules, not the reported restoration of vetted baseline at restart.
Question 211
Employees want to use personally purchased smartphones for limited business email while keeping personal ownership and most personal data private. Which enterprise mobility enrollment or ownership model best matches the case?
- Corporate owned personally enabled
- Unmanaged personal device prohibition
- Bring your own device
- Choose your own device
Explanation
Correct Answer
C:BYOD allows personal hardware to access corporate services under defined conditions. Containerization and privacy-aware management help separate business and personal information.
Incorrect Answers
A:COPE keeps corporate ownership while permitting controlled personal use when analysts encounter company-owned phone with limited personal use; this question instead describes employee-owned device accessing corporate services.
B:A prohibition policy denies corporate access from devices outside approved management and assurance for situations characterized by disallowing unassessed personal endpoints; the case points instead to employee-owned device accessing corporate services.
D:CYOD balances user preference with a supported procurement list; it handles employee choice within approved corporate catalog, while the decisive evidence in the question is employee-owned device accessing corporate services.
Question 212
A company buys phones but allows staff a defined range of personal applications and use during nonworking hours. Which enterprise mobility enrollment or ownership model best matches the case?
- Corporate owned personally enabled
- Bring your own device
- Unmanaged personal device prohibition
- Choose your own device
Explanation
Correct Answer
A:COPE keeps corporate ownership while permitting controlled personal use. Enrollment can support stronger device management than most BYOD deployments.
Incorrect Answers
B:BYOD allows personal hardware to access corporate services under defined conditions; that is relevant to employee-owned device accessing corporate services but does not directly account for company-owned phone with limited personal use.
C:A prohibition policy denies corporate access from devices outside approved management and assurance when the underlying evidence concerns disallowing unassessed personal endpoints rather than the stated company-owned phone with limited personal use.
D:CYOD balances user preference with a supported procurement list in a setting defined by employee choice within approved corporate catalog; the observed issue is company-owned phone with limited personal use.
Question 213
Warehouse scanners must stay company-owned and run approved work applications without recreational app installation. Which enterprise mobility enrollment or ownership model best matches the case?
- Unmanaged personal device prohibition
- Corporate owned personally enabled
- Corporate owned business only
- Bring your own device
Explanation
Correct Answer
C:COBO emphasizes exclusively business use of enterprise-owned devices. Restrictions and lifecycle processes support tight operational control.
Incorrect Answers
A:A prohibition policy denies corporate access from devices outside approved management and assurance; this characterizes disallowing unassessed personal endpoints, whereas the reported condition is enterprise device dedicated to work.
B:COPE keeps corporate ownership while permitting controlled personal use; its distinguishing scope is company-owned phone with limited personal use, not the reported enterprise device dedicated to work.
D:BYOD allows personal hardware to access corporate services under defined conditions in a setting defined by employee-owned device accessing corporate services; the observed issue is enterprise device dedicated to work.
Question 214
Employees select a smartphone from a company-approved catalog, and the company supplies and owns the chosen model. Which enterprise mobility enrollment or ownership model best matches the case?
- Choose your own device
- Bring your own device
- Unmanaged personal device prohibition
- Corporate owned personally enabled
Explanation
Correct Answer
A:CYOD balances user preference with a supported procurement list. Ownership and personal-use permissions still need explicit policy definition.
Incorrect Answers
B:BYOD allows personal hardware to access corporate services under defined conditions; it handles employee-owned device accessing corporate services, while the decisive evidence in the question is employee choice within approved corporate catalog.
C:A prohibition policy denies corporate access from devices outside approved management and assurance for the specific concern of disallowing unassessed personal endpoints, not the requirement involving employee choice within approved corporate catalog.
D:COPE keeps corporate ownership while permitting controlled personal use when the underlying evidence concerns company-owned phone with limited personal use rather than the stated employee choice within approved corporate catalog.
Question 215
A regulated team cannot assess encryption or patch status on personal phones and decides they must not connect to confidential applications. Which enterprise mobility enrollment or ownership model best matches the case?
- Choose your own device
- Corporate owned business only
- Corporate owned personally enabled
- Unmanaged personal device prohibition
- Bring your own device
Explanation
Correct Answer
D:A prohibition policy denies corporate access from devices outside approved management and assurance. It should offer supported alternatives for business work.
Incorrect Answers
A:CYOD balances user preference with a supported procurement list in a setting defined by employee choice within approved corporate catalog; the observed issue is disallowing unassessed personal endpoints.
B:COBO emphasizes exclusively business use of enterprise-owned devices when analysts encounter enterprise device dedicated to work; this question instead describes disallowing unassessed personal endpoints.
C:COPE keeps corporate ownership while permitting controlled personal use when the underlying evidence concerns company-owned phone with limited personal use rather than the stated disallowing unassessed personal endpoints.
E:BYOD allows personal hardware to access corporate services under defined conditions; this characterizes employee-owned device accessing corporate services, whereas the reported condition is disallowing unassessed personal endpoints.
Question 216
Security must centrally enforce screen-lock settings, OS updates and lost-device actions on a managed fleet of tablets. Which mobile security management function best addresses the requirement?
- Unified endpoint management
- Mobile threat defense
- Enterprise mobility management
- Mobile device management
Explanation
Correct Answer
D:MDM applies device-level enrollment and configuration policy and can support remote actions subject to platform and ownership capabilities.
Incorrect Answers
A:UEM brings management of multiple endpoint classes into one policy and operational approach for the specific concern of common management across endpoint types, not the requirement involving centralized device configuration enforcement.
B:MTD evaluates device, app and network threat signals and can feed enforcement decisions; its distinguishing scope is mobile-focused threat detection telemetry, not the reported centralized device configuration enforcement.
C:EMM combines mobility security functions across enrollment, applications and information; its distinguishing scope is integrated governance of mobile apps and devices, not the reported centralized device configuration enforcement.
Question 217
A firm permits personal phones but wants policy applied only to managed work apps and their data, without full control of the phone. Which mobile security management function best addresses the requirement?
- Mobile application management
- Mobile device management
- Unified endpoint management
- Enterprise mobility management
Explanation
Correct Answer
A:MAM governs selected applications and corporate content, often through app-protection policy. It is useful where full-device enrollment is undesirable.
Incorrect Answers
B:MDM applies device-level enrollment and configuration policy and can support remote actions subject to platform and ownership capabilities; the operational difference is centralized device configuration enforcement versus the scenario's work-app-level protection without device control.
C:UEM brings management of multiple endpoint classes into one policy and operational approach; it handles common management across endpoint types, while the decisive evidence in the question is work-app-level protection without device control.
D:EMM combines mobility security functions across enrollment, applications and information; this characterizes integrated governance of mobile apps and devices, whereas the reported condition is work-app-level protection without device control.
Question 218
Administrators need an integrated program covering devices, managed applications and associated identity or content protections. Which mobile security management function best addresses the requirement?
- Mobile threat defense
- Unified endpoint management
- Mobile application management
- Enterprise mobility management
Explanation
Correct Answer
D:EMM combines mobility security functions across enrollment, applications and information. Exact features depend on the deployed platform.
Incorrect Answers
A:MTD evaluates device, app and network threat signals and can feed enforcement decisions for situations characterized by mobile-focused threat detection telemetry; the case points instead to integrated governance of mobile apps and devices.
B:UEM brings management of multiple endpoint classes into one policy and operational approach; it handles common management across endpoint types, while the decisive evidence in the question is integrated governance of mobile apps and devices.
C:MAM governs selected applications and corporate content, often through app-protection policy for situations characterized by work-app-level protection without device control; the case points instead to integrated governance of mobile apps and devices.
Question 219
IT must apply coordinated endpoint policies across smartphones, laptops and desktops rather than operate isolated management systems. Which mobile security management function best addresses the requirement?
- Mobile threat defense
- Unified endpoint management
- Mobile application management
- Enterprise mobility management
Explanation
Correct Answer
B:UEM brings management of multiple endpoint classes into one policy and operational approach. Platform-specific capabilities may still differ.
Incorrect Answers
A:MTD evaluates device, app and network threat signals and can feed enforcement decisions; this characterizes mobile-focused threat detection telemetry, whereas the reported condition is common management across endpoint types.
C:MAM governs selected applications and corporate content, often through app-protection policy; this characterizes work-app-level protection without device control, whereas the reported condition is common management across endpoint types.
D:EMM combines mobility security functions across enrollment, applications and information; the operational difference is integrated governance of mobile apps and devices versus the scenario's common management across endpoint types.
Question 220
Managed smartphones show risky network connections and suspicious apps and need mobile-specific behavioral threat detection. Which mobile security management function best addresses the requirement?
- Mobile device management
- Mobile application management
- Mobile threat defense
- Unified endpoint management
- Enterprise mobility management
Explanation
Correct Answer
C:MTD evaluates device, app and network threat signals and can feed enforcement decisions. It supplements OS protections and enterprise management.
Incorrect Answers
A:MDM applies device-level enrollment and configuration policy and can support remote actions subject to platform and ownership capabilities; that is relevant to centralized device configuration enforcement but does not directly account for mobile-focused threat detection telemetry.
B:MAM governs selected applications and corporate content, often through app-protection policy; this characterizes work-app-level protection without device control, whereas the reported condition is mobile-focused threat detection telemetry.
D:UEM brings management of multiple endpoint classes into one policy and operational approach; this characterizes common management across endpoint types, whereas the reported condition is mobile-focused threat detection telemetry.
E:EMM combines mobility security functions across enrollment, applications and information; that is relevant to integrated governance of mobile apps and devices but does not directly account for mobile-focused threat detection telemetry.