Determining security policies for cloud platform security should involve:

Question

Options

• AAssuming default configurations are always secure
• BIgnoring the shared responsibility model
• CAssessing the specific features and capabilities of the cloud platform
• DFocusing solely on perimeter defense mechanisms

• A
  7% (4)
• B
  5% (3)
• C
  85% (47)
• D
  2% (1)

Explanation

Determining security policies for a cloud platform requires assessing that platform's specific features and capabilities (C) because cloud environments differ significantly - AWS, Azure, and GCP each have unique identity models, network constructs, and service-level controls that must be understood before appropriate policies can be written. Generic policies applied without this understanding will have gaps.

Why the distractors fail:

• A is dangerous - default configurations are often permissive and optimized for ease of use, not security (e.g., public S3 buckets, open security groups).
• B ignores one of the foundational principles of cloud security: the shared responsibility model defines what the provider secures vs. what the customer must secure, and ignoring it creates blind spots.
• D - perimeter defense (firewalls, DMZs) is a legacy on-premises mindset. Cloud is identity-driven and perimeter-less; focusing solely on perimeter mechanisms leaves the attack surface largely unaddressed.

Memory tip: Think "Context before Controls" - you must understand your cloud platform's specific context (its capabilities, services, and constraints) before you can design controls. C is the only choice that starts from understanding rather than assumption or omission.

No community discussion yet for this question.