Final answer:
M:N relationships and multivalued attributes are typically handled in RDBMS by normalizing them into separate tables with one-to-many relationships and single-valued attributes to maintain database integrity and support efficient queries.
Step-by-step explanation:
The question of whether M:N relationships and multivalued attributes should be implemented in a Relational Database Management System (RDBMS) is not strictly true or false. It is dependent on the specific requirements of the database system and the design goals. However, it is generally recommended to normalize M:N relationships into two one-to-many relationships with a junction table in between to maintain referential integrity and to support efficient querying. Meanwhile, multivalued attributes can be challenging, as RDBMS are designed to work with single-valued attributes. These are usually broken down into separate tables to uphold the principles of normalization.
For instance, if we have a database of Students and Courses where students can enroll in multiple courses and courses can have multiple students, we would implement an intermediary table (like "Enrollments") to properly represent this M:N relationship. Similarly, if a student can have multiple email addresses, this should be represented in a separate table rather than as a multivalued attribute in the Students table.