The Complete Strapi™ Course with Plugins and Deployment - Policies

The video tutorial explains the concept of policies in Strappy, detailing their function, scope, and how they are associated with routes. It covers the three types of policies: global, plugin, and API-specific, and how they are structured and referenced. The tutorial demonstrates creating a custom policy using the CLI, attaching it to a route, and testing it. It also explores the policy context, configuration, and how to reuse policies with different configurations. The session concludes with a brief mention of the Strappy object, setting the stage for the next lesson.

What is the primary purpose of policies in Strappy?

• To define API endpoints

• To manage database connections

• To execute functions before a request reaches a route

• To handle user authentication

Which of the following is NOT a scope of policies in Strappy?

• User policies

• API policies

• Plugin policies

• Global policies

Where are global policies located in a Strappy application?

• Inside the source policies folder

• Inside the API folder

• Inside the plugins folder

• Inside the config folder

How are plugin policies referenced in Strappy?

• plugin:identifier

• plugin::identifier

• plugin-identifier

• plugin.identifier

What is the first step in creating a custom policy in Strappy?

• Editing the configuration file

• Creating a new file in the policies subfolder

• Running the Strappy server

• Modifying the database schema

What happens if a custom route points to a non-existing controller?

• The application will crash

• The application will not run

• The route will be automatically created

• The route will be ignored

What does the policy context include?

• Database schema

• API endpoints

• Request and user information

• Server configuration

What error occurs if a request is not from an authenticated user?

• 403 Forbidden

• 500 Internal Server Error

• 401 Unauthorized

• 404 Not Found

How can a policy be made to check for different user roles?

• By hardcoding different roles

• By modifying the database

• By using a configuration object

• By creating multiple policies

What is the benefit of using a configuration object in a policy?

• It reduces memory usage

• It increases server speed

• It allows for dynamic role checking

• It simplifies the code