Question 330
To prevent local console recovery options from bypassing administrative protections, which measure best meets the requirement?
- Core dump privacy controls
- Rescue-mode authentication
- Crontab persistence review
- Sudo I/O logging
- LUKS full-disk encryption
Explanation
Correct Answer
B:Bootloader passwords, encryption and physical controls narrow unauthorized offline system changes; this mechanism directly supports the requirement to prevent local console recovery options from bypassing administrative protections.
Incorrect Answers
A:Core-dump limits reduce storage exposure of credentials and in-process confidential material; that is useful when the task is to prevent application memory containing secrets from being written broadly to disk, not the stated requirement to prevent local console recovery options from bypassing administrative protections.
C:Cron schedules launch periodic activity that may represent legitimate maintenance or attacker persistence; its operational purpose is to identify unexpected scheduled commands running under service accounts, not to achieve the specific requirement to prevent local console recovery options from bypassing administrative protections.
D:When configured, sudo can retain input and output evidence useful for reconstructing sensitive changes; applying it would serve record privileged interactive sessions with contextual attribution without directly satisfying the goal to prevent local console recovery options from bypassing administrative protections.
E:Volume encryption protects offline data when key handling and unlock procedures remain secure; it addresses the different need to protect a Linux laptop's filesystem after physical device theft, leaving the requested ability to prevent local console recovery options from bypassing administrative protections unresolved.
Question 331
To enforce enterprise settings on a managed smartphone fleet, what control should be selected?
- Mobile device management enrollment
- COPE deployment
- BYOD policy
- COBO deployment
Explanation
Correct Answer
A:MDM enrollment establishes a management channel for policy, inventory and compliance enforcement; it supplies the specific control needed to enforce enterprise settings on a managed smartphone fleet.
Incorrect Answers
B:Corporate-owned personally enabled management retains device ownership with controlled user flexibility; that is useful when the task is to provide a company-owned handset that still permits approved personal use, not the stated requirement to enforce enterprise settings on a managed smartphone fleet.
C:Bring-your-own-device rules assign responsibility for permitted apps, support and corporate information handling; a team would select it to define privacy and business data boundaries when staff use personal phones, which does not provide the particular result to enforce enterprise settings on a managed smartphone fleet.
D:Corporate-only policy supports restricted applications and limited personal use on dedicated devices; its operational purpose is to reserve organization-owned phones exclusively for business activity, not to achieve the specific requirement to enforce enterprise settings on a managed smartphone fleet.
Question 332
To protect corporate app data on personally owned phones without full-device control, which security control is most appropriate?
- Mobile application management
- Mobile device management enrollment
- BYOD policy
- COBO deployment
Explanation
Correct Answer
A:MAM applies app-level protection and conditional access to enrolled applications; that is why it addresses the operational task to protect corporate app data on personally owned phones without full-device control.
Incorrect Answers
B:MDM enrollment establishes a management channel for policy, inventory and compliance enforcement; it could help someone trying to enforce enterprise settings on a managed smartphone fleet, but the problem is instead to protect corporate app data on personally owned phones without full-device control.
C:Bring-your-own-device rules assign responsibility for permitted apps, support and corporate information handling; that is useful when the task is to define privacy and business data boundaries when staff use personal phones, not the stated requirement to protect corporate app data on personally owned phones without full-device control.
D:Corporate-only policy supports restricted applications and limited personal use on dedicated devices; a team would select it to reserve organization-owned phones exclusively for business activity, which does not provide the particular result to protect corporate app data on personally owned phones without full-device control.
Question 333
To define privacy and business data boundaries when staff use personal phones, what would a mobile security administrator implement or use?
- BYOD policy
- Mobile application management
- COBO deployment
- COPE deployment
Explanation
Correct Answer
A:Bring-your-own-device rules assign responsibility for permitted apps, support and corporate information handling; its relevant protective or investigative effect is to define privacy and business data boundaries when staff use personal phones.
Incorrect Answers
B:MAM applies app-level protection and conditional access to enrolled applications; although relevant to protect corporate app data on personally owned phones without full-device control, it does not by itself achieve the required task to define privacy and business data boundaries when staff use personal phones.
C:Corporate-only policy supports restricted applications and limited personal use on dedicated devices; it could help someone trying to reserve organization-owned phones exclusively for business activity, but the problem is instead to define privacy and business data boundaries when staff use personal phones.
D:Corporate-owned personally enabled management retains device ownership with controlled user flexibility; that is useful when the task is to provide a company-owned handset that still permits approved personal use, not the stated requirement to define privacy and business data boundaries when staff use personal phones.
Question 334
To provide a company-owned handset that still permits approved personal use, which practice addresses that objective?
- Mobile application management
- COBO deployment
- COPE deployment
- Zero-touch enrollment
Explanation
Correct Answer
C:Corporate-owned personally enabled management retains device ownership with controlled user flexibility; the requested outcome is precisely to provide a company-owned handset that still permits approved personal use.
Incorrect Answers
A:MAM applies app-level protection and conditional access to enrolled applications; its mechanism supports protect corporate app data on personally owned phones without full-device control, while the requested control must be able to provide a company-owned handset that still permits approved personal use.
B:Corporate-only policy supports restricted applications and limited personal use on dedicated devices; the outcome it supports is to reserve organization-owned phones exclusively for business activity, whereas this scenario asks defenders to provide a company-owned handset that still permits approved personal use.
D:Provisioning links eligible devices to enterprise policy during first-run enrollment. This can help to automate corporate Android device management from initial setup, but it does not provide the particular mechanism required to provide a company-owned handset that still permits approved personal use.
Question 335
To reserve organization-owned phones exclusively for business activity, which tool, policy, or technique is appropriate?
- COPE deployment
- Apple Automated Device Enrollment
- COBO deployment
- Android Enterprise work profile
- Mobile device management enrollment
Explanation
Correct Answer
C:Corporate-only policy supports restricted applications and limited personal use on dedicated devices; this choice fits the scenario because the team must reserve organization-owned phones exclusively for business activity.
Incorrect Answers
A:Corporate-owned personally enabled management retains device ownership with controlled user flexibility; the technique works for situations involving provide a company-owned handset that still permits approved personal use, rather than this need to reserve organization-owned phones exclusively for business activity.
B:Automated enrollment ties supported devices to management without relying only on voluntary app installation; its mechanism supports enroll company-owned Apple hardware during activation under organizational control, while the requested control must be able to reserve organization-owned phones exclusively for business activity.
D:Work profiles create a managed container boundary with separate data and policy context; although relevant to isolate managed corporate applications from personal apps, it does not by itself achieve the required task to reserve organization-owned phones exclusively for business activity.
E:MDM enrollment establishes a management channel for policy, inventory and compliance enforcement; it could help someone trying to enforce enterprise settings on a managed smartphone fleet, but the problem is instead to reserve organization-owned phones exclusively for business activity.
Question 336
To manage organizational data with a privacy-conscious personally owned device model, what safeguard would be most applicable?
- Android Enterprise work profile
- User enrollment on iOS
- Zero-touch enrollment
- COBO deployment
Explanation
Correct Answer
B:User Enrollment separates managed identities and selected work resources without assuming complete device ownership; this mechanism directly supports the requirement to manage organizational data with a privacy-conscious personally owned device model.
Incorrect Answers
A:Work profiles create a managed container boundary with separate data and policy context; it addresses the different need to isolate managed corporate applications from personal apps, leaving the requested ability to manage organizational data with a privacy-conscious personally owned device model unresolved.
C:Provisioning links eligible devices to enterprise policy during first-run enrollment; its mechanism supports automate corporate Android device management from initial setup, while the requested control must be able to manage organizational data with a privacy-conscious personally owned device model.
D:Corporate-only policy supports restricted applications and limited personal use on dedicated devices; the outcome it supports is to reserve organization-owned phones exclusively for business activity, whereas this scenario asks defenders to manage organizational data with a privacy-conscious personally owned device model.
Question 337
To isolate managed corporate applications from personal apps, what is the relevant defensive action?
- Zero-touch enrollment
- Android Enterprise work profile
- Mobile application management
- Device compliance attestation
Explanation
Correct Answer
B:Work profiles create a managed container boundary with separate data and policy context; it supplies the specific control needed to isolate managed corporate applications from personal apps.
Incorrect Answers
A:Provisioning links eligible devices to enterprise policy during first-run enrollment; applying it would serve automate corporate Android device management from initial setup without directly satisfying the goal to isolate managed corporate applications from personal apps.
C:MAM applies app-level protection and conditional access to enrolled applications; the technique works for situations involving protect corporate app data on personally owned phones without full-device control, rather than this need to isolate managed corporate applications from personal apps.
D:Compliance posture reports feed access decisions alongside user authentication; its mechanism supports deny business access when a phone is unmanaged or below security policy, while the requested control must be able to isolate managed corporate applications from personal apps.
Question 338
To enable additional enterprise restrictions on company-owned Apple devices and to automate corporate Android device management from initial setup, which TWO measures should the defender select? Choose TWO.
- Supervised iOS enrollment
- Android Enterprise work profile
- Zero-touch enrollment
- COPE deployment
- Apple Automated Device Enrollment
Explanation
Correct Answers
A:Supervision extends permitted MDM controls after supported automated or local enrollment workflows; it satisfies the distinct requirement to enable additional enterprise restrictions on company-owned Apple devices within the multi-control task.
C:Provisioning links eligible devices to enterprise policy during first-run enrollment; it satisfies the distinct requirement to automate corporate Android device management from initial setup within the multi-control task.
Incorrect Answers
B:Work profiles create a managed container boundary with separate data and policy context; applying it would serve isolate managed corporate applications from personal apps without directly satisfying the goal to enable additional enterprise restrictions on company-owned Apple devices and to automate corporate Android device management from initial setup.
D:Corporate-owned personally enabled management retains device ownership with controlled user flexibility; the technique works for situations involving provide a company-owned handset that still permits approved personal use, rather than this need to enable additional enterprise restrictions on company-owned Apple devices and to automate corporate Android device management from initial setup.
E:Automated enrollment ties supported devices to management without relying only on voluntary app installation; its mechanism supports enroll company-owned Apple hardware during activation under organizational control, while the requested control must be able to enable additional enterprise restrictions on company-owned Apple devices and to automate corporate Android device management from initial setup.
Question 339
To automate corporate Android device management from initial setup, which control achieves the target outcome?
- Android Enterprise work profile
- Supervised iOS enrollment
- Zero-touch enrollment
- Device compliance attestation
Explanation
Correct Answer
C:Provisioning links eligible devices to enterprise policy during first-run enrollment; its relevant protective or investigative effect is to automate corporate Android device management from initial setup.
Incorrect Answers
A:Work profiles create a managed container boundary with separate data and policy context; a team would select it to isolate managed corporate applications from personal apps, which does not provide the particular result to automate corporate Android device management from initial setup.
B:Supervision extends permitted MDM controls after supported automated or local enrollment workflows; its operational purpose is to enable additional enterprise restrictions on company-owned Apple devices, not to achieve the specific requirement to automate corporate Android device management from initial setup.
D:Compliance posture reports feed access decisions alongside user authentication; it addresses the different need to deny business access when a phone is unmanaged or below security policy, leaving the requested ability to automate corporate Android device management from initial setup unresolved.
Question 340
To enroll company-owned Apple hardware during activation under organizational control, which solution should be adopted?
- Device compliance attestation
- Android Enterprise work profile
- Zero-touch enrollment
- Apple Automated Device Enrollment
- Supervised iOS enrollment
Explanation
Correct Answer
D:Automated enrollment ties supported devices to management without relying only on voluntary app installation; the requested outcome is precisely to enroll company-owned Apple hardware during activation under organizational control.
Incorrect Answers
A:Compliance posture reports feed access decisions alongside user authentication; that is useful when the task is to deny business access when a phone is unmanaged or below security policy, not the stated requirement to enroll company-owned Apple hardware during activation under organizational control.
B:Work profiles create a managed container boundary with separate data and policy context; a team would select it to isolate managed corporate applications from personal apps, which does not provide the particular result to enroll company-owned Apple hardware during activation under organizational control.
C:Provisioning links eligible devices to enterprise policy during first-run enrollment; its operational purpose is to automate corporate Android device management from initial setup, not to achieve the specific requirement to enroll company-owned Apple hardware during activation under organizational control.
E:Supervision extends permitted MDM controls after supported automated or local enrollment workflows; it addresses the different need to enable additional enterprise restrictions on company-owned Apple devices, leaving the requested ability to enroll company-owned Apple hardware during activation under organizational control unresolved.