The Complete Strapi™ Course with Plugins and Deployment - Configuring Core Routes

The video tutorial explains the concept of routes in Strappy, focusing on how they serve as endpoints for API requests. It covers the automatic generation of routes for CRUD operations and details two ways to customize these routes: modifying core routes and creating custom ones. The tutorial provides an example of customizing a tag route, explaining the use of a router config object to adjust route settings like prefix, only, and except. It also discusses the role of policies, middlewares, and the auth key in route configuration. The session concludes with a brief mention of creating new routes in the next lecture.

What is the primary role of routes in Strappy?

• To serve as endpoints for API requests

• To handle user authentication

• To store data

• To manage database connections

How can Strappy routes be customized?

• By updating the server configuration

• By altering the user interface

• By changing the database schema

• By modifying existing routes or creating custom ones

What is the purpose of a router config object in Strappy?

• To define database models

• To configure server settings

• To customize existing routes

• To manage user sessions

What does the 'prefix' key in a router config object do?

• It changes the database connection

• It modifies the route path

• It alters the user permissions

• It updates the server logs

How does the 'only' key function in route customization?

• It specifies routes to enable

• It specifies routes to disable

• It changes the route's HTTP method

• It enables all routes by default

What happens when the 'auth' key is set to false in a route config?

• The route becomes private

• The route bypasses Strappy's JWT authentication

• The route is logged

• The route is deleted

Which of the following is NOT a component associated with Strappy routes?

• Controllers

• Database triggers

• Policies

• Middlewares