The Complete Strapi™ Course with Plugins and Deployment - Lifecycle Hooks Exercise: Part 1 (Challenge)

The video tutorial addresses an issue in a blog application where the API does not return post authors due to admin users being private by default. To solve this, a new Author content type is created, mirroring admin users but not private. Lifecycle hooks are used to automatically sync admin users with authors and assign authors to posts. The tutorial provides a step-by-step guide and an exercise to implement this solution.

What is the main issue with the current API setup in the blog application?

• The API does not support user authentication.

• The API is too slow to respond.

• The API returns incorrect post content.

• The API does not return post authors.

Why are admin users not returned by the API by default?

• They are not part of the API schema.

• They are not stored in the database.

• They are not linked to any posts.

• They are considered private for security reasons.

What is the purpose of creating a new Author content type?

• To replace the admin users entirely.

• To provide a non-private version of admin users for the API.

• To enhance the security of the application.

• To simplify the database schema.

How are lifecycle hooks used in this solution?

• To notify users of new posts.

• To delete old posts from the database.

• To automatically create and sync Author entities with admin users.

• To manually update the database.

What happens when a new post is created in the admin panel?

• The post is assigned to the admin user who created it.

• The post is left without an author.

• The post is assigned to a random author.

• The post is automatically assigned to the corresponding Author entity.

Which fields are considered relevant for the new Author content type?

• Username, role, and email.

• First name, last name, email, and username.

• First name, last name, role, and user status.

• Email, role, and user status.

What additional relation is added to the Author content type?

• A many-to-many relation with other authors.

• A one-to-many relation with posts.

• A one-to-one relation with the admin user it mirrors.

• A one-to-one relation with the post content type.