26. To delete event 42 the app sends:
- DELETE /rest/v1/events?id=eq.42
- GET /rest/v1/events?delete=42
- PATCH /rest/v1/events?id=42&remove
- POST /rest/v1/delete/42
Answer: A) DELETE /rest/v1/events?id=eq.42
Explanation: Filters select the rows to delete.
MCQs / Computer Science / Supabase: Cloud Data Tier for Android
35 multiple-choice questions on Supabase: Cloud Data Tier for Android from Computer Science, each with the correct answer and, where available, a teacher's explanation. Read through them to revise the chapter, then practise the same questions one by one to test yourself.
Answer: A) DELETE /rest/v1/events?id=eq.42
Explanation: Filters select the rows to delete.
Answer: C) To keep them out of source control
Explanation: local.properties is not committed to Git.
Answer: D) Header, payload, signature
Explanation: The signature proves the token was issued by the server.
Answer: C) The publishable key (sbpublishable…)
Explanation: The publishable key only identifies the project; RLS controls access.
Answer: A) usermetadata
Explanation: Profile fields such as fullname go into usermetadata.
Answer: D) Prefer: return=representation
Explanation: Without it, an insert returns an empty 201 response.
Answer: C) Anyone with the publishable key can read and change it
Explanation: Always enable RLS on tables exposed through the API.
Answer: B) Relational (SQL tables)
Explanation: Supabase = PostgreSQL; Firestore = NoSQL documents.
Answer: B) Storage buckets
Explanation: Storage holds files in buckets.
Answer: A) Runs the request on a background thread and delivers the answer to the callback on the main thread
Explanation: enqueue() is asynchronous; execute() is synchronous and must never run on the main thread.
Previous Page 2 of 2
Practise Supabase: Cloud Data Tier for Android MCQs