ADX-201E 無料問題集「Salesforce Lightning Experience Administrative Essentials for New Admins Extended」

（A）Create public groups for each project team and send the email alert to the project group.

（B）Configure a queue for the project team and have members view the queue's list view.

（C）Use sharing rules to automatically share with the individual users in the project team.

（D）Move the project users to the same role and send the email alert to everyone in the role.

（A）Change the duplicate rule to report Instead of alert so the message is avoided.

（B）Add a secondary matching rule to the duplicate rule to match on the associated customer.

（C）Update the matching method on the rule from fuzzy to exact for First Name and Last Name.

（D）Include the Email field to the existing matching rule for a more exact match.

（A）Check the user profile permissions on the Opportunity object to see if they have permission to delete.

（B）Advise the user to mark the duplicate opportunity Closed Lost and keep it in the system.

（C）Change the user's profile to System Administrator so they have full permissions to delete object records.

（D）Run a report of all opportunities to identify other possible duplicates.

（A）View Setup Audit Trail

（B）Developer Console

（C）Field History Tracking

（D）Debug Log

（A）Debug Logs

（B）Login History

（C）Identity Verification History

（D）Setup Audit Trail

（A）Lookup

（B）Master-Detail

（C）Self

（D）Many-To-Many

（A）The label of Location may have been changed.

（B）The users profile needs create access to Location.

（C）Location has a master-detail field to Account.

（D）Data Loader should only be used with standard objects.

（A）Include the active and prior inactive flow version in the Change Set.

（B）Deployment the flow, with the Metadata API instead of Change Sets

（C）Activate the flow manually after deployment.

（D）Ensure there is an active flow version in the sandbox.

（A）visualforce Page

（B）Roll-Up Summary

（C）Formula Fields

（D）Lightning Component

（A）Bucket fitters

（B）The 'Show Unique Count*

（C）PREVGROUPVAL function

（D）PARENTGROUPVAL Function

（A）Update Record elements should be placed inside the flow loop.

（B）The running user of a flow is the user that last saved the flow.

（C）Update record elements should be placed outside the flow loop.

（D）Use a Get Record component instead of hard coding record IDs.

（A）Refresh the full copy sandbox daily.

（B）Test changes in a shared sandbox.

（C）Review the setup audit trail prior to changes.

（D）Build automation and validation rules using screen flows.

（A）Create a screen flow to pull all related opportunities onto one page.

（B）Configure Split Lit Views.

（C）Implement Service Console.

（D）Enable Subtab Record Browsing in the Setup menu.

（A）A forecast can be either revenue-based or quantity-based.

（B）Opportunity Split data cannot be viewed in a forecast.

（C）The default forecast categories cannot be customized.

（D）A single org can have up to six different types of forecasts.

（A）Add the sales rep's IP address to the trusted IP ranges.

（B）Generate a temporary identity verification code for the rep.

（C）Delegate multi-factor identification to the sales rep.

（D）Instruct the sales rep to log in from the company's VPN.

（A）Use matching names for global publisher layouts and Outlook publisher layouts.

（B）Plan your deployments around the production and sandbox maintenance schedules.

（C）Make sure change sets are limited to 10,000 files.

（D）Be sure to test only after business hours the data after deployment.

（E）Make sure to deploy all dependent components.

（A）Custom Profile

（B）Permission Set

（C）Account Teams

（D）Permission Set Group