In this scenario, a Lookup relationship is the most appropriate choice for relating the Audit custom object to the Account object. This relationship allows for flexibility, especially when it comes to data retention and access control requirements, as outlined by AW Computing ' s security team.

Lookup Relationship:

A Lookup relationship links two objects, allowing records from the custom Audit object to be associated with the Account object. Unlike a Master-Detail relationship, it offers greater flexibility in terms of record ownership, sharing, and visibility controls, which is particularly useful for sensitive data.

The Lookup relationship will enable administrators to set specific permissions, ensuring that only the audit team has access to the records, as required.

Additionally, records in the Lookup relationship are independent. Therefore, if the Account record is deleted, the Audit record can persist, aligning with the need to retain Audit records for 10 years.

Preservation and Access Control:

Given the 10-year retention requirement, the independence of records under a Lookup relationship is ideal. It ensures that Audit records are not automatically deleted when an associated Account record is removed.

Access to Audit records can be restricted to the audit team by setting up custom sharing rules or permissions, which is achievable through the Lookup relationship ' s flexible sharing model.

Incorrect options:

Master-Detail: In a Master-Detail relationship, the detail (child) records are dependent on the master (parent) record. Deleting an Account would automatically delete any associated Audit records, which would conflict with the retention requirement.

Many-To-Many: This type of relationship involves a junction object to associate multiple records from both sides. It is not necessary in this case, as the requirement is a one-to-many relationship from Account to Audit records.

Self: A self-relationship would allow records within the Audit object to be related to each other. This does not apply to linking the Audit object to the Account object.

In conclusion, the Lookup relationship provides the necessary flexibility for data preservation and access control, making it the optimal choice for this requirement.

The Campaign Member option is only available for Update when using Data Import Wizard. This means that you can use Data Import Wizard to update existing campaign members with new or modified information, but you cannot use it to create new campaign members from a spreadsheet. To create new campaign members from a spreadsheet, you need to use other tools such as Data Loader, Import Wizard for Leads and Contacts, or Manage Members button on the campaign page. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_members_adding_parent.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.data_importer.htm & type=5

The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org’s Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm & type=5

Three reasons CK should utilize Data Categories when creating articles in Knowledge are:

Data Categories help organize the Knowledge base content displayed. Data categories are logical groupings of articles that reflect your business needs and processes. You can create a data category group and assign it to one or more article types, and then create data categories and subcategories within that group. Data categories help you organize your articles by topic or criteria and make them easier to find and browse by your users or customers.

Data Categories provide a way to secure access to the Knowledge base content. Data category visibility is a setting that determines which data categories users can access based on their profiles or permission sets. You can use data category visibility to control access to your articles based on their data categories and ensure that only relevant and appropriate content is displayed to different users or customers.

A Knowledge article can be tagged to more than one Data Category. A Knowledge article is a document that provides information or answers to common questions or issues. A Knowledge article can be tagged to one or more data categories within each data category group that is assigned to its article type. This allows you to classify your articles by multiple criteria and make them searchable and accessible by different users or customers.

A cross-filter lets you filter records based on related objects and their fields. For example, you can filter accounts that have at least one opportunity from this year and at least one completed activity in the last 30 days. References: https://help.salesforce.com/s/articleView?id=sf.reports_cross_filters.htm & type=5

Tableau CRM is a product that allows you to create complex dashboards with supporting charts based on data from a variety of sources, including Salesforce data and external data sources. Tableau CRM uses an analytics platform that stores data in datasets and lets you explore and visualize data using lenses and dashboards. You can also use artificial intelligence and machine learning features to discover insights and make predictions from your data. Tableau CRM is integrated with Salesforce and can be accessed from various apps and objects. References: https://help.salesforce.com/s/articleView?id=sf.bi_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.bi_data_overview.htm & type=5