Cloud Kicks (CK) wants to simultaneously delete a Supplier's record and all Supplier ltem__c records if a
partnership ends with a supplier.
What solution could an app builder use to meet the requirement?
The solution that an app builder should use to meet this requirement is master-detail relationship. A master-detail relationship is a type of relationship that creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a master-detail relationship between Supplier__c and SupplierItem__c objects, where Supplier__c is the parent object and SupplierItem__c is the child object. This way, when a Supplier__c record is deleted, all related SupplierItem__c records are also deleted automatically. Option A is incorrect because many-to-many relationship is not suitable for this requirement, as many-to-many relationship allows two objects to be linked in both directions through a junction object, but does not support cascading delete. Option B is incorrect because indirect lookup relationship is not suitable for this requirement, as indirect lookup relationship allows an external object to link with another object using an external ID field, but does not support cascading delete. Option C is incorrect because hierarchical relationship is not suitable for this requirement, as hierarchical relationship allows users to use a lookup field that links an object with itself, but does not support cascading delete.
Which three options art availably when activating a Lightning page from the Lightning App Builder?
Choose 3 answers
When activating a Lightning page from the Lightning App Builder, three options are available:
Assign the page to a combination of apps and profiles. This option allows users to specify which apps and profiles will see the custom Lightning page instead of the default page.
Make the page the org default. This option makes the custom Lightning page the default for all users in the org regardless of their app or profile.
Make the page the default homepage for specific apps. This option allows users to set different homepages for different apps in Lightning Experience. [Source]
An app builder received a request to extend record access beyond the organization-wide defaults configured. Which two features satisfy this requirement?
Choose 2 answers
Sharing rules and manual sharing are two features that can extend record access beyond the organization-wide defaults. Sharing rules are automatic rules that grant access to groups of users based on certain criteria, such as role, public group, or territory. Manual sharing is a manual way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy. Option B and C are not features that extend record access.
Northern Trail Outfitters wants to broadcast an email to 7,000 contacts Salesforce on a regular basis but realizes Salesforce is mass functionality has a limitation on the number erf emails that can be sent each day.
What action should the app builder take?
Research and evaluate products available on AppExchange to send mass emails is the action that the app builder should take to meet the requirement of broadcasting an email to 7,000 contacts in Salesforce on a regular basis. AppExchange is a marketplace where app builders can find products or solutions that can extend Salesforce functionality. There are many products on AppExchange that can send mass emails without hitting the Salesforce limit. Request Salesforce increase the number of maximum daily emails, develop Apex code and Lightning web component to send daily emails, and export Contacts to a CSV file and use an email client to send the emails are not valid or recommended actions.
Ursa Major Solar (UMS) uses Cases to track customer complaints, an Issue__c object to represent known problems with its solar panels, and a
Case_Issue__c junction object to relate known problems to customer complaints.
Periodically, UMS conducts audits which require the auditing users to view Case _Issue__c records.
Which access levels must be configured to allow UMS users to access Case _Issue_c records?
To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established:
D . Read-Only access on Case and Issue__c. Users need read-only access to both Case and Issue__c objects to view associated Case_Issue__c junction object records properly. This is because access to junction object records in Salesforce is determined by the user's access levels to the parent records in a relationship.
Steps to configure access:
Navigate to Setup Profiles or Permission Sets.
Select the profile or permission set of the auditing users.
Under Object Settings, adjust the permissions for Case and Issue__c to at least 'Read-Only'.
Ensure that users have visibility to the Case_Issue__c object itself.
This configuration allows users to view the details of cases and issues as they audit the junction object records.
