PDE Storing the Data Practice Question
A mobile app uses Firestore to store user profiles. The app allows offline data creation and syncing when connectivity resumes. Which Firestore feature should the developer enable?
⚠ Common exam trap
Candidates often confuse Firestore's client-side offline persistence with server-side replication or caching features like multi-region replication or Cloud Memorystore, which are not designed for client-side offline data creation and syncing.
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
✓
Enable offline persistence in the Firestore client SDK
Firestore's offline persistence feature allows the client SDK to automatically cache data locally on the device. When the app creates or modifies data while offline, the SDK stores the changes in a local queue and syncs them with the Firestore backend once connectivity is restored. This is the correct and built-in mechanism for offline data creation and syncing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set up a Firestore trigger to cache data in Cloud Memorystore
Why it's wrong here
Cloud Memorystore is an in-memory cache for server-side workloads and does not provide Firestore's client-side offline persistence or automatic sync on reconnection. It is tempting because caching improves read performance, but offline writes with later synchronisation require enabling Firestore's offline persistence in the client SDK.
- ✓
Enable offline persistence in the Firestore client SDK
Why this is correct
Enabling offline persistence in the Firestore client SDK caches data locally, so the app can create profiles without connectivity and automatically synchronise queued writes once the connection resumes, matching the offline creation and syncing scenario.
- ✗
Use Cloud Storage signed URLs for offline access
Why it's wrong here
Cloud Storage signed URLs grant time-limited access to individual objects and provide no local write queue or automatic conflict-resolving synchronisation. It is tempting because signed URLs enable offline-friendly downloads, yet Firestore's offline persistence is the feature that queues local writes and syncs them when connectivity returns.
- ✗
Enable Firestore multi-region replication
Why it's wrong here
Multi-region replication duplicates data across regions for disaster recovery and availability, not for storing writes made while offline. Offline persistence is the feature that caches pending writes locally and replays them on reconnection; multi-region replication would be chosen for geographic redundancy, not client-side offline sync.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 747 original PDE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PDE 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 PDE exam.