Question 1
What is the main purpose of using token authentication in DRF?
To convert model instances into JSON
To limit number of requests per user
To paginate large responses
To allow clients to authenticate using a token instead of credentials each time
Question 2
Which of these throttle classes limits requests from unauthenticated users in DRF?
UserRateThrottle
AnonRateThrottle
ScopedRateThrottle
DefaultThrottle
Question 3
What is required to enable pagination for all API views when using DRF?
Setting DEFAULT_FILTER_BACKENDS
Using only function-based views
Adding a pagination class under DEFAULT_PAGINATION_CLASS and defining PAGE_SIZE
Adding pagination settings inside urls.py
Question 4
What happens when a user exceeds the allowed request limit defined by DRF throttling?
The request is rejected with a throttle error response
DRF allows the request but logs a warning
The request is delayed until a free slot appears
DRF switches to a different throttle class automatically
Question 5
Which setting defines how many requests authenticated and anonymous users are allowed to make?
PAGE_SIZE
DEFAULT_AUTHENTICATION_CLASSES
DEFAULT_PERMISSION_CLASSES
DEFAULT_THROTTLE_RATES
Question 6
Why might token authentication and throttling be applied together in the same API?
To manage user identity and also limit excessive request usage
To remove the need for database migrations
To remove the need for serializers
To disable pagination in some endpoints
There are 6 questions to complete.