nerdexam
CompTIA

CAS-003 · Question #22

A security analyst is reviewing the corporate MDM settings and notices some disabled settings, which consequently permit users to download programs from untrusted developers and manually install…

The correct answer is E. Containerization F. Signed applications. MDM containerization creates separate device profiles for developers and standard users, while signed application enforcement prevents untrusted app installs on the standard profile.

Technical Integration of Enterprise Security

Question

A security analyst is reviewing the corporate MDM settings and notices some disabled settings, which consequently permit users to download programs from untrusted developers and manually install them. After some conversations, it is confirmed that these settings were disabled to support the internal development of mobile applications. The security analyst is now recommending that developers and testers have a separate device profile allowing this, and that the rest of the organization's users do not have the ability to manually download and install untrusted applications. Which of the following settings should be toggled to achieve the goal? (Choose two.)

Options

  • AOTA updates
  • BRemote wiping
  • CSide loading
  • DSandboxing
  • EContainerization
  • FSigned applications

How the community answered

(14 responses)
  • B
    7% (1)
  • C
    14% (2)
  • E
    79% (11)

Why each option

MDM containerization creates separate device profiles for developers and standard users, while signed application enforcement prevents untrusted app installs on the standard profile.

AOTA updates

OTA updates govern how device firmware and operating system patches are delivered wirelessly and have no effect on restricting or permitting installation of third-party applications from untrusted sources.

BRemote wiping

Remote wiping is a data-protection control used to erase device contents after loss or theft and does not influence which applications users are permitted to download or install during normal operation.

CSide loading

Sideloading describes the capability being governed here, but toggling it as a single global setting cannot create the per-group distinction the analyst requires - that separation is achieved through containerization, which controls the context in which sideloading is allowed.

DSandboxing

Sandboxing restricts what a running application can access on the device to contain potential damage, but it operates after installation and does not gate whether an untrusted app can be downloaded or installed in the first place.

EContainerizationCorrect

Containerization allows the MDM platform to assign separate isolated profiles to different user groups - developers receive a container profile that permits sideloading and untrusted installs, while standard users are placed in a restricted container where such permissions are blocked, directly satisfying the requirement for per-group policy separation.

FSigned applicationsCorrect

Requiring signed applications enforces cryptographic trust validation at install time, ensuring that only apps bearing valid signatures from recognized developers can be installed on the standard user profile, which directly prevents the untrusted developer installs the analyst wants to eliminate.

Concept tested: MDM containerization and signed app enforcement per profile

Source: https://learn.microsoft.com/en-us/mem/intune/apps/app-protection-policy

Topics

#side loading#MDM profiles#application control#containerization

Community Discussion

No community discussion yet for this question.

Full CAS-003 Practice