Advanced Administrator Flashcards
The Chief Marketing Officer (CMO) at FinTrust Solutions wants to ensure that the status field on Opportunities with a ‘High Priority’ status can only be edited by members of the Marketing Team. What is the best way for the admin to go about fulfilling this requirement?
Add a validation rule to the Opportunity object.
In this scenario, we are restricting access. And since this refers to specific record access (Opportunity records with High Priority status), we can create a validation rule that shows an error message when the Status field is changed from High Priority to something else while the user making changes isn’t a member of the Marketing Team profile. This validation rule will be added to the Opportunity object.
Permission Sets cannot be used in this situation because we aren’t adding access. Criteria-based sharing rules apply to record access, but in our case we’re only restricting changes on a specific field and not the entire Opportunity record.
Ethan, the Salesforce Administrator at Cloudzoid Tech, has created three custom objects: Transaction, Line Item, and Statement. Line Item is related to both Statement and Transaction as their detail object in two master-detail relationships. Ethan is planning to create a fourth custom object, Dispatch, and have Line Item as its detail object in another master-detail relationship. Will he be able to successfully create this relationship?
No, because a custom object (as the detail) can only have two master-detail relationships.
A custom object can only have 2 master-detail relationships, but this applies to the detail object only. Since Line Item already has both Statement and Transaction as its parent objects, the limit has been reached. Adding the Dispatch object as another parent would not succeed.
Cloudzoid Tech recently experienced a significant increase in API callouts and is concerned about potential performance issues. As the company’s Salesforce admin, Ethan needs to gain insights into the API call trends to identify potential bottlenecks and optimize the system performance. Which feature should the admin use to monitor and analyze API call activities and trends?
Event Monitoring.
Event Monitoring provides valuable insights into user behavior, system performance, and login trends within the org. It captures event data such as logins, logouts, API calls, and more. This data can be used to analyze usage patterns, troubleshoot issues, and optimize performance. Unlike Debug Logs and Login History, which focus on specific aspects of data tracking, Event Monitoring offers a comprehensive solution for monitoring and analyzing various events within the org.
FinTrust Solutions is required to comply with regulations wherein the data stored in the Price field must be retained for 3 years. With the org almost reaching its data storage limit at this time, will the admin be able to use Field Audit Trail to accomplish this?
Yes, because Field Audit Trail and Field history tracking data do not count against data storage limits.
Field Audit Trail allows you to establish a policy for preserving historical field history data, so it is valuable for adhering to industry regulations pertaining to audit capabilities and data retention like in this example. Field history tracking data and Field Audit Trail data don’t count against the org’s data storage limits, so the admin in this question can use it with no worries.
Ethan, the Salesforce Administrator at Cloudzoid Tech, wants to gather feedback and suggestions from the customer community to improve their products and services. He decides to enable the Ideas feature. Which of the following capabilities are associated with using Salesforce Ideas? (Choose 2)
1.) Allow customers to vote on and prioritize their favorite ideas.
2.) Allow customers to submit feedback and suggestions on the community.
With Salesforce Ideas, customers can submit their feedback and suggestions
directly to the community by posting. Once posted, it also allows the rest of the
customers to vote on and prioritize their favorite ideas through the capability to vole on ideas submitted by others. This voling mechanism helps prioritize ideas
based on popularity, making ii easier for the organization lo identify the most valuable suggestions - similar lo Salesforce’s very own IdeaExchange.
Salesforce has a native mass delete feature that can help when the administrator needs to delete multiple records at the same time. Which of the following can be
mass-deleted using this feature? (Choose 4)
Cases, Leads, Activities, Accounts
Billy is a Service Manager from the Computing Department. He has recently been assigned to the IT Department. Cloudzoid Tech’s Salesforce Admin would have to change Billy’s role to confirm this department transfer. What will happen to the sharing rules relating to Billy’s old and new role?
The sharing rules will be automatically recalculated.
During the role change, sharing rules will be automatically recalculated. Sharing Rules for any related objects like parent objects will also be recalculated and there is no need for the admin to trigger this manually. Recalculation also happens with changes to groups and territories, not just user roles.
Clara and Jim are two users at Cloudzoid Tech. They both handle Project records, but need to be assigned to two different default record types for the Project object. How can the System Admin accomplish this? (Choose 2)
1.) Create two Profiles with different default record types for the Project object
2.) Assign Clara and Jim to each of the Profiles
Permission Sets cannot be used to set the default record type. This can only be done through Profiles, and you can only set one default record type per Profile. This ask would need the admin to create one Profile for Jim and another for Clara – each with different default record types.
Where can an admin and an end user go to confirm the default record type for a specific object?
As an admin, you can check your user’s default record type from their Profile: “Setup > Profiles > check the user’s Profile”
As the end user, default record types according to personal preferences may be set from Personal Settings: “Personal Settings > Set Default Record Types”
At Cloudzoid Tech, the sales team frequently handles Opportunities and Accounts. Ethan, the administrator, wants to improve data quality since he has been getting reports of new Opportunity records associated with inactive Accounts. What can Ethan do to achieve this goal?
Set up a lookup filter on the Opportunity object so the list only shows active Accounts when users are on it.
To prevent the creation of opportunity records associated with inactive accounts, Ethan can implement a lookup filter on the Opportunity object. By setting this up, the list of available accounts shown when users are associating opportunities will be limited to active accounts.
While validation rules and Apex triggers can be used to enhance data quality as well, the lookup filter specifically addresses the goal in this scenario: restricting account selection based on predefined criteria. Creating a custom picklist field does not involve the relationship between Account and Opportunity, so it wouldn’t be a good solution for this.
Jason, Cloudzoid Tech’s security coordinator, would like to use the Security Health Check to identify and fix potential vulnerabilities in the org’s security settings. Which of the following are required for Jason to be able to use Health Check? (Choose 2)
1.) View Setup and Configuration
2.) View Health Check
Health Check is an evaluation of an org’s Salesforce setup to ensure it’s working well. Managers in a company’s security team (or the admin) can use it to review configuration, security, data quality, performance, integrations, and more. The goal is to identify any issues, optimize processes, and ensure the org aligns with best practices.
The system permission that allows viewing Health Check is “View Health Check”. In turn, this permission has a prerequisite as well: “View Setup and Configuration”.
Name 2 facts about Salesforce login history.
1.) You can specify filters and fields to create Login History custom list views.
2.) The login history record is downloadable.
The Login History page shows up to 20,000 records of user logins for the past 6 months, but if you need to see more, it is downloadable in CSV or GZIP file. Filters and fields can be specified to create Login History custom list views.
Ethan, the admin at FinTrust Solutions, is troubleshooting an issue with a possible Flow or custom Apex class that’s causing unexpected behavior in the system. He wants to analyze the detailed execution steps to identify whether the root cause is from the Flow or the Apex class. What tool or feature should he use to capture and review the detailed execution steps?
Debug Log.
Debug logs are designed to capture detailed event sequences, system behavior, and debug information when investigating issues. For this scenario, debug logs would provide insights into the order of operations, evaluated conditions, and actions taken by the system when user actions trigger Flows or Apex classes.
A sales agent accidentally deleted 75 records by mistake 12 days ago. What is the best way for the admin to retrieve the deleted records?
Use the Data Loader’s “Export All” feature.
In this scenario where a significant number of records (75) were accidentally deleted, records are stored in the Recycle Bin for up to 15 days. Since this happened 12 days ago, we know that they should still be recoverable from the Recycle Bin.
While records can be manually undeleted from the recycle bin, dealing with 75 records individually could be time-consuming and inefficient. By using the “Export All” feature from Data Loader, the administrator can quickly retrieve all of the soft-deleted records and have them available for further actions.
Ethan is the admin at Cloudzoid Tech, and he was tasked to optimize the company’s way of managing duplicate records. He understands that there are matching rules that come with the org by default – which of the following are examples of standard matching rules in Salesforce? (Choose 3)
1.) Standard Contact Matching Rule
2.) Standard Account Matching Rule
3.) Standard Lead Matching Rule
Standard matching rules are predefined matching rules that come with Salesforce by default. They are designed to help organizations identify and manage duplicate records across different standard objects like Accounts, Leads, and Contacts. When enabled, these matching rules evaluate incoming data to check if they match existing records based on specified criteria, such as email addresses or names.
