How does using a centralized logging solution support compliance goals in a multicloud environment?

Question

Options

• ABy ensuring that logs are only stored in on-premises environments
• BThrough consistent log format and retention policies across environments
• CBy limiting access to logs to senior management
• DThrough decentralized management of logs to reduce complexity

• A
  17% (9)
• B
  74% (40)
• C
  6% (3)
• D
  4% (2)

Explanation

Option B is correct because compliance frameworks (SOC 2, HIPAA, PCI-DSS, etc.) require organizations to demonstrate consistent, auditable records - a centralized logging solution enforces uniform log formats and retention schedules across all cloud providers, making audits tractable and policies enforceable regardless of which vendor's infrastructure generated the event.

Why the distractors fail:

• A is wrong because multicloud compliance doesn't require on-premises storage - cloud-native or third-party SIEM solutions are fully acceptable, and mandating on-prem would actually undermine multicloud flexibility.
• C is wrong because compliance requires appropriate access controls and audit trails, not restriction to senior management - security teams, auditors, and automated systems all need log access.
• D is wrong because decentralization is the problem centralized logging solves; inconsistent log silos across clouds make compliance reporting fragmented and error-prone.

Memory tip: Think of centralized logging as a single source of truth for auditors - compliance is about proving what happened, when, and who did it uniformly across all environments. "Consistent + Centralized = Compliant."

No community discussion yet for this question.