2.3. Data Roles & Responsibilities

💡 First Principle: Modern data platforms are too complex for one person to master—they require specialized roles like positions on a sports team. Just as a quarterback, lineman, and receiver each bring essential but different skills to football, data professionals divide responsibilities across infrastructure, pipelines, analysis, and modeling. Each role focuses on a different stage of the data lifecycle, and confusion between roles leads to gaps in your data platform.

What happens without clear role separation? The database administrator who also builds dashboards creates security vulnerabilities because they lack time for proper access controls. The analyst forced to build ETL pipelines produces fragile code that breaks in production. Understanding who does what prevents these failures.

Scenario: A company is building a new data platform. Someone must provision and secure the database servers. Someone else must build pipelines to move data from source systems. A third person must build dashboards for executives. A fourth must build machine learning models. These are four distinct skill sets.

Understanding data roles helps you identify which Azure tools each role uses.

Database Administrator (DBA)

• Focus: Health, Security, and Availability of database systems
• Responsibilities:
  • Install, configure, and patch database servers
  • Manage backups and disaster recovery
  • Control user access and permissions
  • Monitor performance and troubleshoot issues
  • Ensure uptime and SLA compliance
• Azure Tools: Azure SQL Database, Azure Portal, Azure Monitor, Azure Backup
• Key Concern: "Is the database running, secure, and recoverable?"

Data Engineer

• Focus: Pipelines, Integration, and Data Flow
• Responsibilities:
  • Design and build data pipelines (ETL/ELT)
  • Ingest data from diverse sources
  • Clean, transform, and prepare data for analysis
  • Optimize data storage and partitioning
  • Ensure data quality and lineage
• Azure Tools: Azure Data Factory, Azure Synapse Analytics, Azure Databricks, Azure Data Lake
• Key Concern: "Is the right data getting to the right place at the right time?"

Data Analyst

• Focus: Insights, Visualization, and Business Intelligence
• Responsibilities:
  • Query and explore data to find patterns
  • Build reports and dashboards
  • Create data models for self-service BI
  • Communicate findings to stakeholders
  • Answer business questions with data
• Azure Tools: Power BI, Azure Synapse (SQL queries), Excel
• Key Concern: "What does the data tell us about the business?"

Data Scientist

• Focus: Advanced Analytics and Machine Learning
• Responsibilities:
  • Build predictive models (ML/AI)
  • Perform statistical analysis
  • Experiment with algorithms
  • Deploy models to production
  • Extract insights from unstructured data
• Azure Tools: Azure Machine Learning, Azure Databricks, Python/R notebooks
• Key Concern: "Can we predict future outcomes from historical data?"

Visual: Data Roles in the Data Lifecycle

Comparative Table: Data Roles

⚠️ Exam Trap: Confusing Data Engineer and Data Analyst is heavily tested. The Engineer builds the pipes; the Analyst drinks from them. If a question mentions "building ETL pipelines," the answer involves Data Engineer, not Analyst.

Key Trade-Offs:

• Specialization vs. Flexibility: Large organizations have distinct roles; small teams may combine responsibilities.
• Build vs. Analyze: Engineers build infrastructure; Analysts use it. Different skill sets and tools.

Reflection Question: A company's sales dashboard suddenly shows incorrect revenue numbers. Which role is responsible for investigating whether the issue is (a) the database being down, (b) the data pipeline failing, or (c) the dashboard calculation being wrong?