Questions › Root Cause Analysis › Top-MNC
Diagnose a sudden drop in policy compliance for enterprise analytics workspace
- Root Cause Analysis
- Top-MNC
- Easy
- 10 min
Problem Statement Description
You are investigating an enterprise analytics workspace where newly onboarded users are suddenly showing a lower policy compliance rate. These users may be creating dashboards, querying datasets, sharing reports, exporting data, or configuring workspace access while operating under company policies for data governance, privacy, security, and approved usage.
The drop is specific to new users, so the issue may involve onboarding, permissions, policy education, default settings, workflow changes, instrumentation, or a real change in user behavior. Your task is to diagnose what is happening before proposing any fixes.
Frame the investigation as an RCA: clarify the metric, confirm the anomaly, isolate the affected population, inspect recent changes, generate hypotheses, and identify what evidence would prove or disprove each one. Focus on separating a true compliance problem from a measurement, logging, segmentation, or policy-classification issue.
The experience should consider:
- How “policy compliance” is defined, including numerator, denominator, eligible actions, and time window
- Whether the drop is isolated to new users by tenure, role, geography, workspace type, company account, plan, or onboarding path
- Instrumentation checks for event logging, policy-violation tagging, user identity mapping, and compliance rule changes
- Recent product, onboarding, permission, data-access, admin-policy, or analytics-workflow changes
- User journey points where new users may misunderstand or bypass required compliance steps
- Hypotheses for both real behavior changes and measurement artifacts
- Evidence needed from dashboards, logs, audit trails, support tickets, admin feedback, and experiment history
- Immediate mitigation considerations while the root cause is still being validated
Your goal is to present a structured diagnostic approach that helps the team determine why compliance dropped, how severe and widespread the issue is, and what evidence should guide the next action without jumping prematurely to a fix.
What this question tests
- Root Cause Analysis
- Metric Decomposition
- Hypothesis Testing
- Decision Discipline
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Root Cause Analysis questions
- A launch in AI writing assistant caused complaints from first-time buyers. Find the likely causeTop-MNC · Root Cause Analysis · Easy
- Latency and error reports increased in profile and identity flow. Prioritize the investigationTop-MNC · Root Cause Analysis · Easy
- Diagnose a sudden drop in conversion for content recommendation feedTop-MNC · Root Cause Analysis · Easy
- Diagnose a sudden drop in risk reduction for payments dispute centerTop-MNC · Root Cause Analysis · Easy
- Diagnose a sudden drop in operational throughput for student learning streaksTop-MNC · Root Cause Analysis · Easy
- Diagnose a sudden drop in learning completion for live event discoveryTop-MNC · Root Cause Analysis · Easy
All Root Cause Analysis questions · Product manager interview questions by skill area