Which of the following is a potential risk when a program runs in privileged mode?

Question

Options

• AIt may serve to create unnecessary code complexity
• BIt may not enforce job separation duties
• CIt may create unnecessary application hardening
• DIt may allow malicious code to be inserted

• A
  4% (1)
• B
  8% (2)
• C
  4% (1)
• D
  85% (22)

Explanation

Running in privileged mode grants a program elevated system access - often unrestricted access to hardware, memory, and OS functions - which means malicious code that executes within that context inherits those same privileges, making D correct. An attacker who injects or exploits code in a privileged process can cause far greater damage than in a restricted one: think kernel exploits, rootkits, or full system compromise.

Why the distractors are wrong:

• A (code complexity) - Privilege level has no bearing on how complex the code is; complexity is a design/architecture concern.
• B (job separation / separation of duties) - This is a policy and access-control concept enforced through user roles and permissions, not a direct consequence of a program running in privileged mode.
• C (application hardening) - Hardening reduces attack surface; it isn't a risk, and privilege mode doesn't create more of it.

Memory tip: Think of privileged mode like giving a program a master key to the building. If someone slips a pickpocket into that program (malicious code), they now have the master key too - that's the risk. The other options describe design or policy issues, not the security consequence of elevated execution rights.

No community discussion yet for this question.