Salesforce ADM-201 Practice Test Questions, Exam Dumps

Practice Exams:

View All

ADM-201 Salesforce Practice Test Questions and Exam Dumps

Question 1:

When does inline editing update the value of a field in a system that supports this feature?

A. The field is saved/updated
B. When the record is saved/updated
C. When the return key is pressed
D. None of the above

Correct Answer: A

Explanation:

Inline editing refers to the ability to modify a field's value directly from a list or form view without having to open the full record or form. This is a commonly used feature in modern web applications and user interfaces such as Salesforce, Microsoft Dynamics, and other CRM or enterprise platforms. Inline editing significantly improves user efficiency by reducing the number of clicks and page transitions needed to make small changes.

In systems that support inline editing, the update behavior typically revolves around immediate or near-immediate field updates once the user interacts with and confirms the change. The key mechanism that triggers the update can vary slightly depending on the interface design and platform, but broadly speaking, the following applies:

Option A, “The field is saved/updated,” is correct because inline editing generally commits the value as soon as the edit is confirmed—this may occur when the user clicks out of the field, presses Enter, or clicks a save button within the editing context of that specific field. The emphasis is that the change is committed on a per-field basis, not necessarily requiring the entire record to be saved or updated. This behavior allows for quicker, more modular updates and aligns with the core philosophy of inline editing.

Option B, “When the record is saved/updated,” would be more applicable to form-based editing or batch editing, where all fields are edited and then saved as a single transaction. Inline editing is distinct in that it commits changes immediately at the field level, without waiting for a full record save.

Option C, “When the return key is pressed,” may apply in some systems but is not a universal behavior. For example, some interfaces may require a user to click a checkmark or simply blur (click away from) the field. Therefore, while pressing Enter may work in certain contexts, it’s not the guaranteed trigger in all implementations. Thus, it is not the most correct or generalizable answer.

Option D, “None of the above,” is incorrect because Option A is valid and describes the standard behavior in most modern systems that support inline editing.

To summarize, inline editing updates the field once the user completes their action on that specific field, which is commonly understood as when the field itself is saved or confirmed. It offers a lightweight alternative to editing a full record, making it especially useful in list views or dashboards where speed and efficiency are important.

Question 2:

Is it true that a company using Custom Fiscal Years cannot utilize the standard forecasting feature?

A. True
B. False

Correct Answer: A

Explanation:

In Salesforce and similar enterprise platforms, fiscal year settings play a critical role in how revenue, forecasting, and reporting are managed. There are two types of fiscal year configurations available:

Standard Fiscal Years: These are based on a typical 12-month calendar and follow regular patterns (e.g., quarters that begin in January, April, July, and October). This model is predefined and works seamlessly with most out-of-the-box features like standard forecasting, dashboards, and reports.
Custom Fiscal Years: These allow organizations to define unique fiscal periods that do not follow the standard calendar format. For instance, a business may operate on a 4-4-5 retail calendar, use nonstandard quarter start dates, or define fiscal years based on operational cycles that differ from the Gregorian calendar.

While Custom Fiscal Years provide the flexibility that some organizations need for alignment with their internal accounting practices, they also come with important limitations—one of which is the incompatibility with standard forecasting tools.

Let’s break down why Option A (True) is correct:

The standard forecasting feature in platforms like Salesforce is built around the assumption of a standard fiscal year. It uses predefined logic and timelines that align with the standard 12-month calendar to generate forecasts, set quotas, and produce performance metrics.
When a company enables Custom Fiscal Years, they are essentially overriding the standard structure, which disrupts how the forecasting engine interprets time-based data. Because of this, standard forecasting becomes unavailable. Users who need forecasting with Custom Fiscal Years must use custom solutions such as:

Custom forecasting models
Custom objects and reports
Third-party integrations

Salesforce documentation explicitly states that Custom Fiscal Years are not supported by the standard Collaborative Forecasts feature. This limitation exists because custom periods don’t align with the hardcoded logic behind the standard forecasting framework.
This restriction is crucial for decision-makers to understand before enabling Custom Fiscal Years. Once enabled, switching back is complex and may require developer support, so the decision should not be made lightly.

Option B (False) is incorrect because it implies that companies can use the standard forecasting tools with Custom Fiscal Years, which is not accurate. Enabling Custom Fiscal Years disables that functionality unless workarounds or custom forecasting solutions are implemented.

To conclude, while Custom Fiscal Years offer flexibility for unique financial reporting requirements, they do prevent the use of standard forecasting tools, making Option A (True) the correct answer. Organizations considering this switch should plan carefully to ensure they are prepared to handle forecasting through custom configurations.

Question 3

Which of the following items is not considered a standard object in Salesforce?

A. Opportunities
B. Solutions
C. Job Applicants
D. Accounts
E. Campaigns

Correct Answer: C

Explanation:

Salesforce offers a wide range of standard objects—predefined objects that come out-of-the-box with any Salesforce organization. These standard objects are foundational to key functionalities such as managing leads, accounts, contacts, opportunities, campaigns, and more. However, Salesforce also allows the creation of custom objects, which are designed by users or developers to suit specific business needs that are not met by standard functionality.

Let’s examine each option to determine which is not a standard object:

A (Opportunities): This is a standard object in Salesforce. It represents potential revenue-generating deals and is closely tied to accounts, contacts, and stages in the sales process. It allows sales teams to track deal progress and forecasting.
B (Solutions): Though this object is now deprecated in favor of the newer Knowledge object, Solutions was originally a standard object used for storing frequently asked questions or problem-resolution content. It is still considered standard, though its usage is diminishing.
C (Job Applicants): This is not a standard object in Salesforce. It is typically part of a custom-built recruiting or human resources app within Salesforce. Salesforce does not natively include an object called "Job Applicants" in its standard schema. If an organization is using Salesforce for recruiting purposes, they would have had to create this object themselves or use a third-party app such as Salesforce for HR or Applicant Tracking Systems (ATS) that build on the Salesforce platform.
D (Accounts): This is one of the core standard objects in Salesforce. Accounts typically represent companies or individuals a business deals with, and they are central to most Salesforce CRM implementations.
E (Campaigns): This is also a standard object used in Salesforce's marketing functionality. Campaigns allow users to manage outbound marketing efforts like emails, ads, and events and to associate leads and contacts with those efforts for tracking effectiveness and ROI.

Therefore, only C (Job Applicants) does not fall under the standard object category. It represents a custom object, either created by an admin or delivered through a third-party application.

To recap:

Standard objects are those created and supported by Salesforce by default.
Custom objects are user-defined and used to meet specific business processes not addressed by standard objects.
"Job Applicants" is a clear example of a use-case-specific object that does not exist in the native Salesforce schema unless added manually.

Question 4:

Which of the following options are included as features of the Salesforce Service Cloud product?

A. Opportunities
B. Knowledge
C. Entitlements
D. Campaigns
E. Quotes

Correct Answer: B, C

Explanation:

Salesforce offers a range of cloud-based products tailored to different business functions. The Service Cloud is specifically designed for customer service and support operations. It includes tools that enable service agents to resolve customer issues efficiently, manage service contracts, offer self-service resources, and deliver consistent customer experiences across various channels such as phone, email, live chat, and social media.

Let’s examine each option to determine whether it falls under the Service Cloud umbrella:

A (Opportunities): This is part of the Sales Cloud, not the Service Cloud. Opportunities are used to track sales deals and revenue pipelines. While this object may be visible across various Salesforce implementations, it is not a core feature of Service Cloud.
B (Knowledge): Correct. Salesforce Knowledge is a key Service Cloud feature. It allows organizations to create and manage a repository of articles that service agents and customers can use to find answers. Knowledge base articles support faster case resolution, enable self-service, and reduce agent workload. It is integrated into cases, portals, and chat to provide contextual support content.
C (Entitlements): Correct. Entitlements are a standard feature within the Service Cloud that allow organizations to define and track the type of support a customer is entitled to based on service contracts, SLAs, or warranties. It helps service teams monitor whether cases are being resolved within agreed-upon service levels, making it a crucial component for managing customer expectations and compliance.
D (Campaigns): This is part of the Sales Cloud or Marketing Cloud. Campaigns are used to plan, execute, and track marketing efforts like events, emails, and advertisements. They are not part of the Service Cloud's core functionalities, which are focused on support, not lead generation or marketing.
E (Quotes): Like Opportunities, Quotes belong to the Sales Cloud. They allow sales reps to create detailed pricing proposals related to Opportunities. Service Cloud users do not typically engage with Quotes, as their focus is on customer support rather than sales negotiation or order management.

In summary, the Service Cloud provides tools that are focused on delivering and managing customer service. Key features include Cases, Knowledge, Entitlements, Service Console, Live Agent, Omni-Channel Routing, and integration with telephony systems. Among the given options, Knowledge (B) and Entitlements (C) are directly tied to the Service Cloud and are central to its functionality.

Question 5:

Do locale settings determine how users see date formats, time formats, and number formats in Salesforce?

A. True
B. False

Correct Answer: A

Explanation:

In Salesforce and other enterprise systems, locale settings are part of a user's personal preferences that affect how information is displayed, but not how it is stored. These settings are particularly important in global organizations where users are spread across different countries, each with distinct standards for formatting dates, times, numbers, and currencies.

Let’s explore what locale settings specifically control:

Date Formats:
Locale settings adjust the format in which dates appear. For example:

In the United States (locale: English - United States), a date might be displayed as MM/DD/YYYY.
In the United Kingdom (locale: English - United Kingdom), the same date would appear as DD/MM/YYYY. This ensures that users view dates in a format they are culturally and regionally accustomed to, reducing confusion and misinterpretation—especially important in transactional or scheduling scenarios.

Time Formats:
Locale settings also define how time is displayed—either in 12-hour (AM/PM) or 24-hour format. For example:

U.S. locale: 3:45 PM
German locale: 15:45 These adjustments improve clarity and align with users’ expectations based on their region.

Number Formats:
Numerical presentation also varies by locale, including the use of:

Decimal separators: A period (.) in the U.S. vs. a comma (,) in many European countries.
Thousand separators: A comma (,) in the U.S. vs. a period (.) or space in others. For example:
U.S. locale: 1,234.56
German locale: 1.234,56

These settings do not affect the underlying data storage, meaning Salesforce still stores data in a universal format that can be translated based on each user’s preferences. This separation between data representation and data storage ensures consistency and accuracy across a global system.

Option A (True) is correct because locale settings do control how date formats, time formats, and number formats appear to the user.

Option B (False) is incorrect because it implies that locale settings have no effect on display formatting, which is factually untrue and would misrepresent how Salesforce handles user-specific presentation of data.

In conclusion, locale settings play a critical role in the user experience by ensuring that dates, times, and numbers appear in a format that is intuitive and familiar to users based on their region. This customization enhances usability and reduces errors in interpretation—making A (True) the correct and accurate answer.

Question 6:

If the organization's default locale is set to US English, does this mean every user must use US English as their locale, and they cannot change it?

A. True
B. False

Correct Answer: B

Explanation:

In Salesforce, the company locale is a system-wide default that sets the initial format for elements like date, time, and numbers when new users are created. However, this setting does not mean individual users are permanently bound to it. Users are given the ability to personalize their own locale settings, which is an essential feature for organizations operating in multiple regions around the world.

When an administrator creates a Salesforce organization, they select a default company locale—for example, English (United States). This default defines how dates appear (e.g., MM/DD/YYYY), how time is shown (e.g., 12-hour vs. 24-hour), and how numbers are formatted (e.g., commas and decimal points). However, this default only applies at the moment a user is first created. Once a user logs in, they have the ability to go into their personal settings and choose a different locale that better matches their regional preferences.

For instance, someone based in Germany could change their locale to German (Germany), which would alter the format of dates to DD.MM.YYYY, switch the time display to 24-hour format, and use a comma as the decimal separator. These personalized changes apply only to that user’s interface and do not affect the data or how other users see information.

Therefore, the idea that all users are forced to use the company locale with no ability to change it is incorrect. The system is specifically designed to allow for flexibility, recognizing that not every user will be operating in the same region or with the same formatting preferences. This flexibility enhances usability and prevents confusion, especially in global teams.

To summarize, the company locale is simply a starting point. It does not restrict or override a user’s ability to choose their own locale settings. Users can change their language, time zone, and regional formatting independently from the system default. This makes option B the correct choice.

Question 7:

If a company’s fiscal year aligns with the Gregorian calendar, is it required to use Custom Fiscal Years in Salesforce?

A. True
B. False

Correct Answer: B

Explanation:

In Salesforce, fiscal year settings determine how financial reporting periods are structured within the system. There are two main types of fiscal years available: Standard Fiscal Years and Custom Fiscal Years. Understanding when each is used is key to managing sales and financial reports effectively.

The Gregorian calendar is the calendar system most widely used around the world. It divides the year into 12 months starting from January and ending in December. A fiscal year that follows this calendar would either match the calendar year exactly (January through December) or begin in another month (e.g., starting in July and ending the following June) but still follow a regular, monthly structure.

If your company uses a regular, structured fiscal calendar—whether it matches the calendar year (January to December) or starts in another month but still follows a consistent monthly pattern—you can use Salesforce’s Standard Fiscal Year setting. This standard setup supports fiscal years that start in any month and span 12 months, without requiring customization.

Custom Fiscal Years in Salesforce are only necessary when a company uses a non-standard fiscal structure. Examples include:

Fiscal years that do not align with standard calendar months.
4-4-5 accounting calendars (where each quarter consists of two 4-week months and one 5-week month).
Fiscal periods with irregular lengths or special segmentation.

When Custom Fiscal Years are enabled, administrators can define each fiscal period manually. However, enabling this feature comes with limitations—it disables some standard Salesforce forecasting and reporting features, and once activated, it cannot be turned off.

Because the question states that the fiscal year follows the Gregorian calendar (which is regular and predictable), there is no need to use Custom Fiscal Years. The Standard Fiscal Year setup is sufficient and simpler to manage.

Therefore, option A (True) is incorrect because it assumes Custom Fiscal Years are required when they are not. Option B (False) is the correct answer because companies following the Gregorian calendar can and should use the Standard Fiscal Year unless they have more complex needs.

To summarize, if your company's fiscal year follows the Gregorian calendar in structure and consistency, you do not need Custom Fiscal Years. Standard Fiscal Years are entirely adequate, making option B the correct choice.

Question 8:

What must be done in order to enable the multi-currency feature in Salesforce?

A. Contact Salesforce.com
B. Check the Enable Multi-currency checkbox in your Chatter profile
C. Operate your business in at least two different countries
D. You cannot enable this feature once you've implemented Salesforce

Correct Answer: A

Explanation:

The multi-currency feature in Salesforce is designed for organizations that operate in multiple countries or regions and need to manage transactions in more than one currency. This feature allows users to work with various currencies, track exchange rates, and maintain accurate financial records for global operations.

However, enabling multi-currency is not something that Salesforce system administrators can do directly from the Setup menu. Unlike other configuration options, enabling multi-currency has significant implications for how data is handled across the platform—especially in objects like Opportunities, Quotes, Reports, and Forecasts. Because of this, you must contact Salesforce support to have the feature enabled.

Let’s review why the other options are incorrect:

Option B is incorrect because enabling multi-currency is not done through a user’s Chatter profile. Chatter is a collaboration tool in Salesforce and has no relation to currency settings.

Option C is misleading. While companies that use multi-currency typically do operate in multiple countries, Salesforce does not require geographic proof or conditions about a company’s location before enabling the feature. The need is based on business operations, not geography.

Option D is also incorrect. You can enable multi-currency even after Salesforce has been implemented, although it is a major change and should be planned carefully. Once enabled, the feature cannot be turned off, and it affects how currency-related data is stored and displayed. For this reason, enabling it after implementation may require data migration, testing, and updates to existing reports and processes.

To enable multi-currency, an organization administrator must open a case with Salesforce support, who will assess the request and assist in activating the feature. After it's enabled, administrators can define corporate currency, add additional currencies, set exchange rates, and assign currencies to user profiles and records.

In summary, the multi-currency feature is a powerful tool for global organizations, but enabling it requires contacting Salesforce support directly due to its technical complexity and irreversible impact. Therefore, the correct answer is A.

Question 9:

Which Salesforce feature ensures that the converted currency amount remains fixed on closed opportunities, even if exchange rates change later?

A. Locale
B. Company Profile
C. Multi-currency
D. Advanced Currency Management
E. None of the above

Correct Answer: D

Explanation:

In Salesforce, when an organization operates with more than one currency, it is crucial to maintain accuracy in financial reporting—especially for historical data such as closed opportunities. This is where Advanced Currency Management becomes essential.

By default, when multi-currency is enabled in Salesforce, exchange rates are defined at the corporate level and apply uniformly across records. However, if those exchange rates are ever updated (for example, due to currency fluctuations), past opportunity records—such as closed deals—might reflect the new rates. This creates inaccuracies because the value at the time of the deal no longer matches what's displayed. To prevent this, Advanced Currency Management is used.

Advanced Currency Management allows organizations to manage dated exchange rates. This means:

You can define exchange rates that are effective during specific date ranges.
Salesforce will use the appropriate exchange rate based on the close date of an opportunity.
Once the opportunity is closed, its converted amount remains locked and historically accurate, regardless of any future changes to exchange rates.

Let’s evaluate the other options:

A (Locale): This setting determines the user’s display preferences for date, time, and number formats. It does not influence currency locking or exchange rate behavior.
B (Company Profile): While this contains information like the corporate currency, time zone, and default locale, it doesn’t provide functionality for locking currency values.
C (Multi-currency): Enabling multi-currency allows the use of multiple currencies across Salesforce records. However, it alone does not lock converted values. Without Advanced Currency Management, exchange rate changes affect all records, including historical ones.
E (None of the above): This is incorrect because D (Advanced Currency Management) is the correct answer.

To summarize, Advanced Currency Management is the only feature in Salesforce that allows you to apply dated exchange rates and preserve the integrity of converted currency amounts on closed opportunities. This is critical for financial reporting and forecasting in organizations dealing with international currencies. Therefore, the correct answer is D.

Question 10:

Do user interface settings in Salesforce apply universally to all users within an organization?

A. True
B. False

Correct Answer: A

Explanation:

In Salesforce, User Interface (UI) settings refer to the configurations that determine how the platform appears and behaves for users across the organization. These include features like:

The ability to enable or disable the collapsible sidebar
Display of related lists in separate sections
Showing inline editing for records
Enabling hover details or related list hover links
Activating or hiding certain UI elements like the Salesforce Classic menu or tab styles

These settings are found under Setup > User Interface, and they apply globally to the entire organization. This means that when an administrator enables or disables a UI feature, it affects all users in the org, not just a single profile or individual user. That’s why these are referred to as organization-wide settings.

These settings do not offer granular control per user or profile. For example, if the “Enable Collapsible Sidebar” option is turned on in the User Interface settings, then all users will see the collapsible sidebar feature available in their UI, assuming they’re using the relevant interface (e.g., Salesforce Classic).

This contrasts with Profile or Permission Set-based settings, which control user access to objects, fields, and tabs on an individual basis. Unlike those, UI settings are not controlled by permission sets or roles and are not user-specific.

There are some exceptions to how different UI elements behave per user—such as what tabs they see, or which apps are available—but these are managed through App Settings, Page Layouts, and Profiles, not through the main User Interface configuration.

It’s also worth noting that these UI settings affect both Salesforce Classic and Lightning Experience, though not all settings apply to both interfaces. As of recent updates, many of these global UI settings have become less relevant for users fully migrated to Lightning Experience, where the Lightning App Builder offers more flexibility for customizing user views.

To summarize, the User Interface settings are organization-level controls that apply to all users within the Salesforce org. They are not customizable at the individual level through settings or preferences. Therefore, the correct answer is A.