Model Meta class options in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does the ordering option in Django's Model Meta class do?

Consider a Django model with a Meta class that includes ordering = ['-created_at']. What effect does this have when querying the model?

A It filters query results to only include records where <code>created_at</code> is not null.

B It sorts query results by the <code>created_at</code> field in descending order by default.

C It sets the default database index on the <code>created_at</code> field.

D It disables ordering on the <code>created_at</code> field.

💡 Hint

Think about how query results are returned when you don't specify an order explicitly.

The ordering option in the Meta class tells Django to sort query results by the specified fields by default. A minus sign - means descending order.

❓ component_behavior

intermediate

How does the unique_together Meta option affect a Django model?

Given a model with unique_together = [('first_name', 'last_name')] in its Meta class, what behavior does this enforce?

A It creates a database index on <code>first_name</code> and <code>last_name</code> but does not enforce uniqueness.

B It makes both <code>first_name</code> and <code>last_name</code> unique individually.

C It ensures that the combination of <code>first_name</code> and <code>last_name</code> is unique across all records.

D It allows duplicate combinations of <code>first_name</code> and <code>last_name</code> but restricts duplicates in either field alone.

💡 Hint

Think about uniqueness constraints involving multiple fields together.

The unique_together option enforces that no two records can have the same combination of the specified fields.

📝 Syntax

advanced

What is the correct way to specify a verbose name for a Django model using Meta options?

Choose the option that correctly sets the singular and plural verbose names for a Django model.

A

class Meta:
    verbose_name = 'Person'
    verbose_name_plural = 'People'

B

class Meta:
    verbose_name = ('Person', 'People')

C

class Meta:
    verbose_names = {'singular': 'Person', 'plural': 'People'}

D

class Meta:
    verboseName = 'Person'
    verboseNamePlural = 'People'

💡 Hint

Look for the exact attribute names Django expects in the Meta class.

Django expects verbose_name and verbose_name_plural as separate string attributes in the Meta class.

❓ state_output

advanced

What is the effect of setting abstract = True in a Django model's Meta class?

Consider this model Meta option: abstract = True. What happens when you run migrations and query this model?

A No database table is created for this model; it is used only as a base class for other models.

B A database table is created but it cannot be queried directly.

C The model is ignored completely by Django and cannot be used.

D The model creates a table with only the fields defined in the Meta class.

💡 Hint

Think about inheritance and reusable model parts.

Setting abstract = True means the model is a base class. Django does not create a table for it but other models can inherit its fields.

🔧 Debug

expert

Why does this Django model raise an error during migration?

Given this Meta class: class Meta: ordering = 'name' What error occurs and why?

Django

class Meta:
    ordering = 'name'

A No error; the model migrates successfully.

B SyntaxError because the Meta class is missing a colon.

C ValueError because 'name' is not a valid field in the model.

D TypeError because ordering must be a list or tuple, not a string.

💡 Hint

Check the data type expected for the ordering option.

The ordering option must be a list or tuple of strings. A single string is invalid and causes a TypeError.