OCI Audit logs track API operations for security and compliance.
Invalid statement: Audit Logs are disabled by default (B): Audit Logs are enabled by default across all compartments in a tenancy—no manual activation is required. They automatically record all API activities.
Why A and C are valid:
Security-related events (A): Audit Logs capture user actions, making them critical for security monitoring.
Compartment-level display (C): Logs can be filtered and viewed by compartment or tenancy level via the Console or API.
Audit Logs are always active, with a 90-day retention period by default.
[Reference:OCI Audit Overview, , , ]
Question # 18
Which response contains rich information to process for analytics?
For analytics, the data source must provide detailed, actionable information.
Database Audit Logs (C): These logs contain rich data like user actions, SQL queries, timestamps, and security events, making them ideal for performance, security, and compliance analysis in Logging Analytics.
Why not A, B, or D?
Entity types (A): These are metadata definitions, not data for analytics.
Log Sources (B): These are configurations for log parsing, not the logs themselves.
Logging Analytic Entities (D): Entities are resource representations, not the data content.
Database Audit Logs offer the depth needed for meaningful insights.