Data Analytics, Visualization, and Security Operations
This domain combines query/serving tools, visualization, and governance. For analytics, know Hologres (real-time, PostgreSQL-compatible, federated queries into MaxCompute), AnalyticDB (high-concurrency OLAP), and Quick BI for dashboards. For security and operations, know Resource Access Management (RAM) for identity and permissions, MaxCompute project-level and table-level authorization, data masking/desensitization, audit logging, and DataWorks Data Quality and lineage for operational control.
Traps: candidates assume granting a RAM user a console role automatically grants data access - data permissions are separate and must be granted on projects/tables. They confuse masking (hiding values at query time) with encryption at rest. They forget that audit logs are how you investigate who accessed what, and they treat Quick BI row-level permissions as automatic rather than configured. Another trap is assuming cross-project access works without explicit authorization or a package.
Worked example: an analyst needs a dashboard but must not see customer phone numbers. Grant the RAM user read access to the specific table, apply a masking rule on the phone column, build the Quick BI dataset on the masked view, and verify via audit logs that access is recorded. Granting console login alone would fail the data-access requirement.
Rule of thumb: identity (RAM) ≠ data permission (project/table grants) ≠ protection (masking/encryption) ≠ observability (audit logs). Treat them as four separate layers when answering.