Which combination of features should be considered when designing centralized logging and monitoring for hybrid multicloud environments? (Select two)

Question

Options

• AIntegration capabilities with different cloud providers' native monitoring tools
• BA single, cloud-provider-specific tool for all environments
• CReal-time alerting and automated incident response
• DManual log analysis processes for security incidents

• A
  77% (41)
• B
  15% (8)
• D
  8% (4)

Explanation

In hybrid multicloud environments, integration capabilities (A) are essential because logs and metrics span AWS, Azure, GCP, and on-premises systems - a centralized solution must ingest data from all of them without blind spots. Real-time alerting and automated incident response (C) is equally critical because manual processes cannot keep pace with the volume and velocity of events across distributed infrastructure.

B is wrong because a single cloud-provider-specific tool creates vendor lock-in and cannot natively monitor competing cloud platforms - the exact opposite of what "hybrid multicloud" requires. D is wrong because manual log analysis is too slow, error-prone, and unscalable for modern security incidents; automation is a baseline expectation, not a luxury.

Memory tip: Think "hybrid = heterogeneous + fast." Heterogeneous means you need cross-provider integration (A), and fast means you need real-time automation (C). Any answer suggesting "single vendor" or "manual" immediately conflicts with the hybrid multicloud premise.

No community discussion yet for this question.