The confirmation request after triggering a delete action (e.g. objects from course, questions from test, accounts from the system, memberships from course) should be done via an interruptive modal.
This has the advantage that you can see in the background where you triggered the action.

To provide optimal information for users when deleting elements, the following must apply:
The modal consists of a title (A), a message box (B), a listing of the previously selected elements (C) and two buttons (D):

• TITLE (A): The title is composed as follows: "Delete [number of selected items] [type of item]" (f.e. Delete 12 Questions)
• MESSAGEBOX (B): A Confirmation Messagebox is used and clarifies the consequence of the action, it does not(!) just ask for "Are you sure you want to delete". Suggestion: "You're about to delete these [number of selected items] [type of items]. As a result, these [type of items] no longer exists in the [type of container]." (f.e. You're about to delete these 12 questions. As a result, these questions no longer exists in the test.")
• LISTING (C): A "Descriptive Listing" is recommended for the listing. Lists here which items have been previously selected. This helps users to decide whether the right items are deleted or not. The listing is done alphabetically.
  • The listing consists of 3 indicators:
    • Primary Identifier: most significant property (e.g. title, name).
    • Secondary Identifier: Visual feature that helps to better recognize if you have selected the right objects (e.g. Icon, Letter Avatar)
    • Featured Property (optional): If Primary and Secondary Identifier are not sufficient for the distinction, another property is used, which clarifies the distinction (e.g. Username, Question Type).
  • Properties are separated with a Pipe | (already in use in forum, presentation table)
• Buttons (D): With a primary button "Delete [type of items]" (z.B. Delete Questions) the action can be executed and confirmed, with a default button "Cancel" the action is canceled and you return to the content page with the selected items.

Addtional:

1. The labels should work in both plural and singular. I.e. if only 1 entity is deleted, the title, the message box and the button should be singular (Delete Object instead of Delete Objects).
2. In order to have a suitable Sec. identifier, the existing icons are checked to see if there is a suitable one (example: delete mail distribution list). We should define that Primary Identifier MUST, Sec. Identified SHOULD and Featured Properties OPTIONAL is defined, so that cases that have no matching icons can act without icons.