Firestore Security Rules — Schema Design Flaw with Visibility Field
This PCDE practice question tests your understanding of design and implement database schemas. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
match /users/{userId} {
allow read, write: if request.auth.uid == userId;
}
match /messages/{messageId} {
allow read: if resource.data.visibility == 'public' || request.auth.uid == resource.data.senderId;
allow create: if request.auth.uid == resource.data.senderId;
allow delete: if request.auth.uid == resource.data.senderId || request.auth.token.isAdmin == true;
}
}
}
Refer to the exhibit. You are reviewing a Firestore security rules file. What is the main security flaw in the database schema design that these rules expose?
Exhibit
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
match /users/{userId} {
allow read, write: if request.auth.uid == userId;
}
match /messages/{messageId} {
allow read: if resource.data.visibility == 'public' || request.auth.uid == resource.data.senderId;
allow create: if request.auth.uid == resource.data.senderId;
allow delete: if request.auth.uid == resource.data.senderId || request.auth.token.isAdmin == true;
}
}
}
A
The rules do not protect against brute force attacks
Why wrong: Not specifically related to schema design flaw.
B
The senderId field is not indexed
Why wrong: Indexing is for performance, not security.
C
The delete rule allows admin to delete any message
Why wrong: Admin delete is a legitimate feature, not a flaw.
D
Users can set the visibility field, allowing them to make messages public
The create rule does not restrict the visibility value, so users can bypass intended privacy.
The answer is that users can set the visibility field, allowing them to make messages public. This is the core schema design flaw because the Firestore security rules for the create operation only validate that the senderId matches the authenticated user, but they impose no constraints on the visibility field itself. As a result, any authenticated user can create a document with visibility set to 'public', bypassing intended access controls and potentially exposing private messages to unauthorized readers. On the Google Professional Cloud Database Engineer exam, this scenario tests your ability to identify schema-level vulnerabilities rather than simple rule syntax errors—a common trap is focusing on authentication checks while ignoring unvalidated fields that control data exposure. Remember the mnemonic: "If a field controls access, the rules must lock it."
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Users can set the visibility field, allowing them to make messages public
Option D is correct because the Firestore security rules allow any authenticated user to set the `visibility` field on a message document. This means a user could change the visibility to 'public', making private messages accessible to all users regardless of the intended audience. The rules do not validate that the user setting the visibility is the sender or an admin, exposing a data access control flaw.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The rules do not protect against brute force attacks
Why it's wrong here
Not specifically related to schema design flaw.
✗
The senderId field is not indexed
Why it's wrong here
Indexing is for performance, not security.
✗
The delete rule allows admin to delete any message
Why it's wrong here
Admin delete is a legitimate feature, not a flaw.
✓
Users can set the visibility field, allowing them to make messages public
Why this is correct
The create rule does not restrict the visibility value, so users can bypass intended privacy.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The Google Cloud Professional Data Engineer exam often tests the misconception that indexing or brute force protection are security concerns in Firestore, when the real flaw is unvalidated field writes that bypass intended access control.
Detailed technical explanation
How to think about this question
Firestore security rules evaluate each read/write operation against the request's `auth.uid` and the document data. In this schema, the `visibility` field is not constrained by a `if request.auth.uid == resource.data.senderId` check, so any authenticated user can set it to 'public'. This is a common misconfiguration where developers treat a field like a flag without enforcing who can modify it, leading to unintended data exposure in multi-tenant applications.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design and implement database schemas — This question tests Design and implement database schemas — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Users can set the visibility field, allowing them to make messages public — Option D is correct because the Firestore security rules allow any authenticated user to set the `visibility` field on a message document. This means a user could change the visibility to 'public', making private messages accessible to all users regardless of the intended audience. The rules do not validate that the user setting the visibility is the sender or an admin, exposing a data access control flaw.
What should I do if I get this PCDE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PCDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCDE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.