Explanation
A lead qualification model based on implicit prospect interest and explicit information provided by prospects requires the feature of Marketing Cloud Account Engagement Score and Grade. The score is a numerical value that measures the implicit interest of a prospect based on their engagement with marketing activities, such as opening emails, clicking links, and visiting landing pages. The grade is a letter value that measures the explicit fit of a prospect based on the information they provide, such as industry, company size, and job title. By combining the score and grade, marketers can segment and prioritize their prospects more effectively3.
References: 3: Scoring and Grading Prospects

Explanation
These are the default user roles that are included with Marketing Cloud Account Engagement1. They have different levels of access and permissions to perform various tasks in Marketing Cloud Account Engagement. You can also create custom roles from a default role or from scratch.

Explanation
According to the Salesforce documentation, the issue of none of the lead's Marketing Cloud Account Engagement information (score/grade) transferring over when Jim, a sales manager, converted a lead to a contact in Salesforce can be addressed by making sure that the administrator has mapped the lead fields to the contact fields in Salesforce. A field mapping is a feature that allows users to sync the data between Marketing Cloud Account Engagement and Salesforce fields, such as name, email, score, or grade. A field mapping can be configured by the administrator in the connector settings, and it can be customized for different objects, such as leads, contacts, or accounts. When a lead is converted to a contact in Salesforce, the Marketing Cloud Account Engagement information (score/grade) should transfer over to the contact record, as long as the lead fields and the contact fields are mapped correctly in the connector settings. If the fields are not mapped correctly, the Marketing Cloud Account Engagement information (score/grade) will not transfer over, and the contact record will not reflect the Marketing Cloud Account Engagement data. Therefore, the administrator needs to make sure that the lead fields and the contact fields are mapped correctly in the connector settings, and that the sync between Marketing Cloud Account Engagement and Salesforce is working properly.
Marketing Cloud Account Engagement only showing this information on the lead record, this information showing on the account record and not the contact, or the administrator needing to create lookup fields on the contact to see this from the lead are not the correct ways to address the issue of none of the lead's Marketing Cloud Account Engagement information (score/grade) transferring over when Jim, a sales manager, converted a lead to a contact in Salesforce, as they are either inaccurate, irrelevant, or unnecessary options for the field mapping or the data sync. References: Salesforce documentation

Explanation
According to the Salesforce documentation, the answer is false. There are some restrictions on how you assign custom users abilities. A custom user is a user who has a custom role assigned to them in Marketing Cloud Account Engagement. A custom role is a feature that allows users to create and assign custom permissions and access levels to other users in Marketing Cloud Account Engagement. A custom role can be created and managed by the administrator in the Admin tab in Marketing Cloud Account Engagement, and it can be assigned to new or existing users. A custom role can be assigned to a user by using different methods, such as editing an existing default role, assigning new users during the import process, or adding a batch of existing users using table actions. However, there are some restrictions on how you assign custom users abilities, such as:
* You cannot assign a custom user the ability to create or edit other users, roles, or connectors. This ability is reserved for the administrator only, and it cannot be delegated to a custom user.
* You cannot assign a custom user the ability to access or edit the data or settings of another user, unless the custom user is the manager of that user. A manager is a user who is responsible for overseeing and managing other users, and who can view and edit their data or settings. A manager can be assigned to a user in the user record, and they can have a custom role or a default role.
* You cannot assign a custom user the ability to access or edit the data or settings of a prospect, unless the custom user is the owner or the assigned user of that prospect. An owner is a user who created the prospect in Marketing Cloud Account Engagement, and who can view and edit their data or settings. An assigned user is a user who is assigned to the prospect in Marketing Cloud Account Engagement, and who can view and edit their data or settings. An owner or an assigned user can be assigned to a prospect in the prospect record, and they can have a custom role or a default role.
References: Salesforce documentation

Explanation
The limitations of connecting Marketing Cloud Account Engagement to a Salesforce Sandbox account are: if connected to a sandbox first, when you create your production connector, all prospects will not automatically queue to sync, and Marketing Cloud Account Engagement can't "wipe" data, so you will need to manually delete any prospects and data that is brought into your Marketing Cloud Account Engagement account from the sandbox connector before enabling the connector for your production instance. A Salesforce Sandbox account is a copy of your production environment that you can use for testing and development purposes.
Marketing Cloud Account Engagement Sandboxes are test versions of a Marketing Cloud Account Engagement Business Unit that you can provision within a Salesforce Sandbox. However, Marketing Cloud Account Engagement Sandboxes have some limitations that you need to be aware of before using them. One limitation is that if you connect Marketing Cloud Account Engagement to a Salesforce Sandbox first, and then create a production connector, the prospects in your Marketing Cloud Account Engagement account will not automatically sync with the production environment. You will need to manually sync them or use an automation tool to do so. Another limitation is that Marketing Cloud Account Engagement cannot erase the data that is brought into your Marketing Cloud Account Engagement account from the sandbox connector, such as prospects, fields, and assets. You will need to manually delete them before enabling the connector for your production instance, or else you will end up with duplicate or unwanted data in your Marketing Cloud Account Engagement account1112 References: 11: Marketing Cloud Account Engagement Sandboxes: What They Can, and Can't Do12: Use Marketing Cloud Account Engagement Sandboxes