Online Access Free Advanced-Administrator Exam Questions

No.# It should be B

No.# C,D are correct answers

You need to use the Advanced-Administrator training guide to pass this exam. It is helpful.

No.# https://help.salesforce.com/s/articleView?id=sf.changesets_best_practices.htm&type=5

After you upload a change set, you can't change its contents. If you need to add dependent components to a change set you already uploaded, clone the change set, add the dependent components, and then upload it again.

No.# B & C should be correct

No.# D is the correct answer

No.# A and D should be correct

No.# Answer should only be B. The contact is NOT linked to an account
Contacts that aren't linked to an Account are always private, regardless of your organization's sharing model. Only the owner of the contact, System Administrators, or users with "View All" for Contacts, or "View All Data" can view personal contacts.

No.# Answer A is Correct, just some typo's as following (Please rectify):
Current/Incorrect version: A. CASE( Lead_Score__c 10, "Cold", 20, "Warm", 30, Hot, "Null")

Correct version: A. CASE( Lead_Score__c, 10, "Cold", 20, "Warm", 30, "Hot", "Null")

No.# In Salesforce, the role hierarchy allows automatic sharing of records with users higher up in the hierarchy. However, this automatic sharing only takes place if the option ‘Grant Access Using Hierarchies’ is enabled in the sharing settings for the object in question.
If a sales manager cannot view a contact held by a salesperson below him/her in the role hierarchy, the most likely reason is that the contact sharing settings have the option ‘Grant Access Using Hierarchies’ disabled. This prevents the automatic sharing of contacts along the role hierarchy.

No.# Change sets: Non possono essere utilizzati per distribuire metadati da un'organizzazione Developer Edition a un'altra. Change sets sono utilizzabili solo tra organizzazioni collegate tramite una relazione di produzione o sandbox.
Data Loader: È uno strumento utilizzato per caricare e esportare dati, non metadati.
per cui CD

No.# Answer C

I got a high score of 94%,
Thanks very much and I will prepare more exam with your appreciate product.

No.# To effectively manage the merging of duplicate account records in Salesforce, which also have associated contacts with the same name, the correct sequence of steps is:

**D. Merge the duplicate accounts and then merge the duplicate contacts.**

Here's the rationale for this approach:

1. **Merge the Duplicate Accounts First**: Merging the accounts first is crucial because it simplifies the subsequent steps by consolidating all related records (like opportunities, contacts, etc.) under a single account. Salesforce allows you to merge up to three duplicate accounts at one time. During this process, you can choose which account to retain as the master record and what specific field values should be preserved.

2. **Then Merge the Duplicate Contacts**: After the accounts are merged, you should then proceed to merge the contacts. Since each account had a contact with the same name, these contacts might now be linked to the newly merged account, depending on your configuration and the specifics of the record linkage. Merging the contacts ensures that there are no redundant contact records in the system, which helps maintain clean data and reduces confusion.

Here’s why the other options are less appropriate:

- **A. Merge the duplicate contacts and then merge the duplicate accounts.**
- This approach could complicate the process because merging contacts first does not address the hierarchical nature of account and contact relationships in Salesforce. Accounts serve as a parent record to contacts, so it’s generally more logical and systematic to start merging at the account level.

- **B. Merge the duplicate accounts and check the box that optionally merges the duplicate contacts.**
- While this option sounds convenient, Salesforce does not actually offer an automatic "check a box" option to merge contacts while merging accounts. Each type of record (accounts, contacts) must be merged separately through their respective merge interfaces.

- **C. Merge the duplicate...

No.# I Agree
When considering the implementation of Salesforce Shield, particularly Shield Platform Encryption, AW Computing should be aware of the implications on system functionality and data handling processes. Here are some key considerations:

**C. Paused flows can cause data to be saved in an unencrypted state.**

This is an important consideration because:

- **Paused Flows and Encryption**: If your organization utilizes Salesforce Shield, particularly Platform Encryption, it’s crucial to understand how paused flows handle data. When a flow is paused, the state of the data being processed might be saved temporarily, which could potentially be in an unencrypted form. This can pose a security risk if sensitive data is involved. Knowing this can help in planning how to manage paused states and ensure compliance with data protection policies.

**A. Einstein Lead Scoring is available on encrypted fields.** (This statement is incorrect)
- Einstein Lead Scoring typically does not support encrypted fields due to the nature of the machine learning models requiring access to actual data values to make predictions. Encrypting fields can restrict the ability of certain Salesforce features, like Einstein, to access or utilize the data fully.

**B. Encrypted fields are able to be referenced in flows.** (This statement is technically correct but simplistic)
- While you can reference encrypted fields in flows, there may be limitations on how you can use them, especially concerning any operations that require decrypting the value, such as comparisons or data manipulations within the flow.

**D. Shield Platform Encryption can be used with custom metadata types.** (This statement is incorrect)
- Salesforce Shield Platform Encryption does not typically extend to custom metadata types. Custom metadata types store configuration data, not operational data, and thus the encryption options for these types are usually not the same as for standard or custom objects.

Thus, option **C** is...

No.# Given the scenario where an administrator has created a screen flow to change the record type of an Account from "Internal Customers" to "External Customers" (or vice versa), and considering the sharing rules and profile settings described, the impact on the Sales user's record access after running this flow would be:

**A. Record Access remains the same.**

Here's the reasoning:

- **Record Type Change**: Changing the record type of an Account does not inherently affect the ownership or the sharing settings of the record. Since record types are used primarily to organize and display different page layouts and available picklist values, the fundamental access to the record under Salesforce's security model (which includes ownership, role hierarchy, sharing rules, and profile permissions) remains unchanged.

- **Sharing Settings**: The sharing settings for Accounts are set to Public Read Only. This setting ensures that all users within the organization can at least read all Account records, regardless of the record type. Since the Sales profile already has access to the "External Customers" record type, and the Accounts are publicly readable, the Sales users will maintain their read access irrespective of the record type.

The other options are incorrect based on how Salesforce's security and access settings work:

- **B. A new record owner will be assigned.**
- Changing a record type via a flow does not involve changing the ownership of the record unless explicitly defined within the flow's logic, which is not a standard action when merely changing record types.

- **C. Edit access will be lost to the record.**
- Since the sharing model is set to Public Read Only, edit permissions are not governed by the record type but by the profile and permission settings specific to the user. The screen flow changing the record type doesn’t affect edit permissions directly unless the profile or permission set restricts edit capabilities based on record type, which is not in...

No.# When implementing advanced currency management in Salesforce for AW Computing, which deals with customers in multiple countries, there are specific considerations that need to be taken into account. Here are two key points:

1. **A. When a currency is added to an organization's list of supported currencies, it cannot be deleted.**
- This is an important consideration because once a currency is added to Salesforce, it remains in the system even if it is no longer used. This could lead to clutter or confusion if many currencies are added without careful planning. Administrators need to be thoughtful about which currencies they add, as removing them later is not straightforward.

2. **D. Once enabled, advanced currency management cannot be disabled.**
- Enabling advanced currency management (also known as Dated Exchange Rates) in Salesforce is a significant decision because once it's turned on, it cannot be disabled. This feature allows for managing exchange rates historically over different time periods, which is crucial for organizations dealing with transactions in multiple currencies over time. However, the irreversible nature of this decision means it requires careful consideration and planning before implementation.

The incorrect options are:

- **B. Historical trend reports will only use the last dated exchange rate.**
- This statement is incorrect because one of the main features of advanced currency management is the ability to use historical exchange rates. Salesforce allows you to specify different exchange rates for different dates, and reports can use these historical rates, not just the last dated exchange rate.

- **C. Opportunities will only display sales in the customer's localized currency.**
- This is incorrect because Salesforce allows for the display of opportunity amounts in both the organization’s default currency and the opportunity’s currency. Advanced currency management enhances this by allowing historical currency rate managem...

No.# For the requirement to automatically create an Invoice record with associated Invoice_Line_Item__c records for each product on an Opportunity when it closes as won, the best option to implement this is:

**D. Use an Opportunity that calls a Flow.**

Here's a step-by-step explanation for choosing this option:

- **Flow**: A Flow in Salesforce is a powerful tool for automating complex business processes without writing code. It can handle logic that includes creating and updating multiple records based on specific conditions. For this scenario, a Flow can be designed to trigger when an Opportunity is marked as 'Closed Won'. The Flow would then create an Invoice record and iterate through each Opportunity Product associated with the Opportunity to create corresponding Invoice_Line_Item__c records. This ensures that all necessary data from the Opportunity and its products are correctly transferred to the new Invoice records.

- **Triggering the Flow**: The Flow can be triggered automatically from the Opportunity object. This can be configured using Process Builder or a Flow Trigger (depending on the Salesforce setup), which listens for the specific condition of an Opportunity closing as won.

The other options are not as well-suited for the described requirements:

- **A. Use Einstein Next Best Actions.**
- Einstein Next Best Action is generally used for suggesting actions to users, not automatically executing data-intensive back-end processes like creating records based on business logic.

- **B. Use an Opportunity Approval process.**
- An approval process is used for gaining approval on records before proceeding with further actions. While it could be part of a larger workflow, on its own, it doesn’t handle the creation of new records based on the approval of an opportunity.

- **C. Use a custom button on the Opportunity.**
- A custom button could initiate a Flow or other process but would require manual intervention by the user to click the button. This does n...

No.# To enable a sales representative at AW Computing to give read/write access to an Account and its related records to a teammate while they are on vacation, the best option provided is:

**A. Add the Manual Sharing button to the page layout.**

Here’s why this option is appropriate:

- **Manual Sharing**: This feature allows record owners to share their records with other users manually. By adding the Manual Sharing button to the page layout of the Account object, the sales rep can grant another user access to a specific account and its related records with the specified access level (read/write in this case). This method is straightforward and does not require administrative intervention each time a rep needs to share records temporarily.

The other options do not directly address the need to share specific records temporarily:

- **B. Include the mate on the Opportunity Team.**
- Adding a colleague to the Opportunity Team would provide access to specific opportunities, but it does not necessarily grant access to the Account or all related records. This is more specific to opportunities and does not comprehensively cover access to all related records.

- **C. Create an ownership-based sharing rule.**
- Ownership-based sharing rules are generally used to automate sharing based on the owner of the records and certain criteria. This approach is not suited for temporary, ad-hoc access needs because it is not flexible enough to handle one-off or short-term access requirements.

- **D. Enable public groups for sharing.**
- While using public groups can be a way to manage sharing rules more effectively, it does not provide a solution for temporary sharing of specific records by the record owner. Public groups are typically used in conjunction with sharing rules for broader and more permanent access settings.

Therefore, **A. Add the Manual Sharing button to the page layout** is the best option to meet the requirement. This allows the sales rep to directly control ...

No.# To ensure that only employees can access their own records on the customer object and not their managers at Universal Containers, given that the Organization-Wide Defaults (OWD) are set to private, the most effective and direct approach is:

**A. Uncheck Grant Access using Hierarchies in Sharing Settings.**

Here’s why this option is suitable:

- **Grant Access Using Hierarchies**: Salesforce includes a default setting where managers in the role hierarchy can access records owned by their subordinates. This setting is typically enabled by default for standard and custom objects. If the goal is to ensure that managers do not have access to their employees' records, the administrator should uncheck this option for the custom object in question. This will override the default behavior and ensure that managers cannot access records owned by their direct reports unless explicitly granted by another sharing mechanism.

The other options are less relevant for the specific need to restrict manager access:

- **B. Verify that Allow Search is unchecked on the custom object.**
- While unchecking "Allow Search" would prevent the records from appearing in search results, it does not inherently restrict access to the records if someone navigates to them directly or if they have a direct link. This option doesn’t provide the necessary access control on its own.

- **C. Uncheck Allow Users to Access Privacy Data on each profile.**
- This option is not standard in Salesforce and does not directly correspond to controlling access to specific records based on hierarchy. It seems to be a misunderstanding of Salesforce features or possibly a custom implementation.

- **D. Enable Hide Personal Information in User Management Settings.**
- This option relates to hiding personal information across the user interface but does not impact access control to specific records or override hierarchical access settings.

Therefore, the correct and effective action to take is **A. Uncheck ...