# Day one quiz

https://www.sanity.io/learn/course/day-one-with-sanity-studio/day-one-quiz.md

Let's test everything you've learned in this course by answering a few questions.

## Structured Content

**Question:** What's the best thing about Sanity being developer friendly?

1. Developers can work faster and get to go home earlier
2. Everyone is happier when developers are
3. Developers can create experiences tailored to content creators
4. Developers can make all the most important decisions on their own



**Question:** What does each element in a content model describe?

1. What something looks like
2. What something is
3. How something works
4. Who created it



## Sanity Studio

**Question:** Which of these is NOT a good reason to add validation rules?

1. They ensure consumers receive trustworthy content
2. They help guide the purpose of the content being created
3. It's good to force content creators to slow down
4. Guardrails are especially useful for new creators



**Question:** What's a good reason for making changes in your Sanity Studio?

1. Experimentation
2. Feedback from content creators
3. Intuition
4. Change is as good as a holiday



**Question:** When is a good time to create a custom form component?

1. As soon as possible
2. After exhausting built-in configuration options
3. Before reading the documentation
4. Just before bed time



## GROQ

**Question:** What is [] called in GROQ?

1. A square bracket pair
2. A filter
3. An index
4. Square bois



**Question:** What is {} called in GROQ?

1. A curly bracket pair
2. A projection
3. An index
4. Curly bois



**Question:** Which of the following is true in GROQ queries?

1. Filters must always specify a _type
2. The * indicates a query across all datasets
3. Projections help reduce over-fetching
4. You can write GraphQL inside a GROQ query



## App SDK

**Question:** Which front end library is Sanity App SDK designed for?

1. Tailwind CSS
2. Sanity UI
3. shadcn/ui
4. None (they're headless)



**Question:** What can App SDK apps do that Studio can't?

1. Multiplayer editing
2. Cross-project editing
3. Optimistic editing
4. AI-powered editing



## Compute

**Question:** Which one ISN'T a use case for Functions?

1. Triggering connected services
2. Preventing publishing
3. Invalidating caches
4. Updating search indexes



**Question:** Functions are deployed as part of

1. Sanity Studio
2. Sanity Functions
3. Sanity Blueprints
4. GROQ-powered webhooks