Objective and core distinction
Conventional data roles divide responsibilities without fixing every organization’s job titles. Database administrators commonly manage database operations, permissions, backup and recovery. Data engineers design and maintain ingestion, integration, cleaning and transformation pipelines. Data analysts explore data, build analytical models and communicate useful insights in reports. Some work overlaps, and one employee may perform several roles. A role question should identify the required deliverable and the affected layer. “It uses data” is not enough to classify all activity as analysis. Conversely, a person called an analyst can carry out an engineering task; in that task they are performing the corresponding responsibility.
Worked example
Fictional case:a municipal arts project has three requests. First, it needs a tested database recovery plan. Second, it must integrate registrations from several sources and standardize their fields. Third, it wants to explain participation by neighbourhood in a report. Route the requests by work:recovery planning maps to database administration; integration and transformation map to data engineering; the analytical explanation/report maps to data analysis. This does not prevent collaboration. The analyst may explain the report’s data needs to the engineer, and the administrator may manage appropriate access to the stores. The output of the reasoning is a responsibility map, not a rule that three named people must be hired.
Changed condition and misconception
Now a report contains fewer rows than expected. Do not assign a repair solely from that symptom. Missing source access, an ingestion mapping failure, an incorrect model relationship and a visual filter can all affect visible rows through different layers. A good investigation isolates the affected operation. If source permissions and the database are healthy but a verified pipeline mapping prevents loading, changing a downstream chart is not a repair of that mapping. If the loaded data is correct and the visual filter is wrong, the task changes. Role matching requires the actual diagnosed condition, not a generic preference for one team.
Transfer check
Transfer check:a single employee reviews database privileges in the morning, maintains a cleaning pipeline at noon, and produces a decision report in the afternoon. Must every task have the same conventional role because the employee is the same? Check basis:no. Describe the responsibility for each task and the expected deliverable. Then ask who has authority and competence in that organization rather than inventing a universal staffing rule. For a separate problem, write the evidence you would want before routing a missing-data incident. Distinguish the initial symptom from the identified failed layer. Use the linked tasks to practice routing different requests rather than memorize personal names.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
Explore job roles in the world of data - Training | Microsoft Learn