In the context of designing solutions for ease of operations and automation, what is a key security and compliance goal?

Question

Options

• ATo minimize the use of encryption to enhance performance
• BTo implement robust access controls and data protection mechanisms
• CTo ignore compliance standards in favor of custom security policies
• DTo use a single layer of security for simplicity

• A
  14% (4)
• B
  76% (22)
• C
  3% (1)
• D
  7% (2)

Explanation

B is correct because when designing systems for operational ease and automation, the foundational security goal is always to enforce robust access controls (who can do what) and data protection mechanisms (encryption, masking, integrity checks) - these ensure that automated processes operate within defined security boundaries without exposing sensitive data.

Why the distractors fail:

• A is wrong because minimizing encryption to boost performance is a dangerous trade-off that violates data protection principles - modern encryption overhead is negligible and non-negotiable in compliant systems.
• C is wrong because compliance standards (SOC 2, ISO 27001, HIPAA, etc.) exist precisely to establish baseline security requirements; custom policies that ignore them create audit failures and legal risk.
• D is wrong because single-layer security (no "defense in depth") means one breach compromises everything - layered security is a core principle, not a complexity to avoid.

Memory tip: Think of it as the "Lock + Vault" rule - access controls are the lock (who gets in), and data protection is the vault (what's safe inside). Any answer that weakens either layer is wrong.

No community discussion yet for this question.