You cannot create mark a document as a record through regular retention label (information government), the only way is to create a file plan in records management (which will be a retention label but with extra options such as "Mark items as record"). And the second options is to make this label as a default on that specific sharepoint folder, as publishing the label will not automatically apply it o files.

Answer is B & C (just because is asking for two answers/two steps to achieve this) A. Sensitivity Labels is used for different purposes. D. Create a retention policy can achieve this, but this would only be one step. E. Create a File Plan is an extra step in any process for retention policies. So this would be the third and first answer it the question would ask for 3 answers. F. Create a retention Lock this is not a thing.

Correct answer is B & C. There is no such thing as "Create a file plan". Using File plan tab, we create a "Retention Label" , so B is the right answer.

BC correct answer

Dont worry.. Selections are correct.. Create a label that mark items as records and set this label as default label for sharepoint contract library.. And that's it!

Answer AC To automatically mark all the contracts in the SharePoint Online site as records when they are uploaded to the Contracts document library, you need to perform the following two actions:

To be able to treat the contracts as records with need retention labels. To mark automatically mark the contracts with can place the retention label as default label in the a document library

Seems like B&C based on this as well: https://learn.microsoft.com/en-us/microsoft-365/compliance/declare-records?view=o365-worldwide

The correct answer is B&C.

Answer is B & C Configure a Retention Label, then apply it as a default to all uploads in the document library named contracts.

This is a tricky question. A Retention POLICY is used for LOCATIONS, like a site, a library or mailboxes (and much more!). A Retention LABEL is used at ITEM level, like documents. In this case I would initially say a Retention POLICY will do the job. BUT since a Retention POLICY is tied to a specific container, the content will loose the settings when moved to another location where the Retention POLICY isn't present. The question however isn't clear on this, so that's open for debate. Therefore B & C are the most viable options here. Also because you CAN'T combine a Retention LABEL with a Retention POLICY, only with a Retention LABEL POLICY. In real life though I would opt for a Retention POLICY, and apply it to the Contracts document library and be done with it.

Tricky one in my opinion...I would say you need the three actions: 1. Create a retention label 2. Create a retention policy 3. Configure a default label on the Contracts document library

B & D would make more sense.