Free Google Professional Data Engineer Actual Exam Questions - Question 5 Discussion
various analysts. You want to make this data readable but unmodifiable by analysts. At the same
time, you want to provide the analysts with individual workspaces in the same project, where they
can create and store tables for their own use, without the tables being accessible by other analysts.
What should you do?
C. This makes sense because giving viewer access on the shared dataset plus editor rights only on each analyst’s own dataset keeps their workspaces private and the shared data read-only.
Option C sounds right; individual datasets keep their tables private and shared one is read-only.
C imo makes the most sense here. Giving each analyst editor rights only on their own dataset ensures their work stays private, while the shared dataset stays read-only with viewer access. Options like B or D either give too broad access or don’t isolate personal data properly. A lacks the individual dataset separation that the question is asking for. This setup keeps everything clean and controlled, which is exactly what you want when multiple analysts are involved but shouldn’t mess with each other’s tables.
Makes sense that it’s C, since giving each analyst editor rights only on their own dataset keeps their work isolated. Also, since they have viewer access just on the shared dataset, it prevents accidental changes there. Option A and D fall short because they don’t separate individual workspaces properly, and B’s project-level editor role is way too open for personal datasets. C fits the need for both shared access and personal sandboxing perfectly.
Option C seems right because it gives view-only access to the shared dataset and lets each analyst edit only their own dataset. Option B looks risky since giving Data Editor role at project level is too broad.