Advanced-Administrator Exam Results

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.

Opening the flow in Debug mode and running it as another user allows simulating how the flow behaves for different users with different permissions and settings. This can help identify any issues related to user

Two considerations that the administrator should remember about roll-up summary fields are:

Roll-up types include COUNT, SUM, and AVG. A roll-up type is a function that determines how the data from the child records is aggregated and displayed on the parent record. The available roll-up types are COUNT, which counts the number of child records; SUM, which adds up the values of a numeric field on the child records; AVG, which calculates the average value of a numeric field on the child records; MIN, which displays the lowest value of a field on the child records; and MAX, which displays the highest value of a field on the child records.

Roll-up summary fields are created on the master side of a master-detail relationship. A master-detail relationship is a type of relationship that links two objects together such that the master object controls certain behaviors of the detail object, such as security and deletion. A roll-up summary field is a type of field that displays a value that is calculated from child records related to a parent record. Roll-up summary fields can only be created on the master object of a master-detail relationship or on a lookup relationship if it is set as required.

The other two options are incorrect because:

Roll-up summary fields do not prevent the conversion of a master-detail relationship to a lookup. They only prevent it if they reference a formula field that includes another relationship.

Rollup fields are not calculated prior to save. They are calculated after save and may take some time to update.

References: &type=5 &type=5

The PARENTGROUPVAL function is a formula function that returns the value of a parent group in a report. It can be used to compare values across different groupings and show relative performance. In this case, the administrator can use this function to show the lead source effectiveness for each country by calculating the percentage of leads from each lead source divided by the total number of leads for each country. References: orce.com/s/articleView?id=sf.reports_formulas_parentgroupval.htm&type=5