매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Salesforce Certified Platform Administrator Exam 온라인 연습
최종 업데이트 시간: 2026년03월30일
당신은 온라인 연습 문제를 통해 Salesforce Plat-Admn-201 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Plat-Admn-201 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 148개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
There are two primary ways to display different picklist values to different groups of users. The first, and most common, is using Record Types (Option C). A single picklist field can have its available values filtered at the Record Type level. By creating a "Sales" record type and a "Marketing" record type, the admin can select which values are visible for each. These record types are then assigned to the respective users' profiles. The second method (Option D) involves using different Page Layouts and two separate picklist fields. In this scenario, the admin creates two distinct fields (e.g., "Sales Category" and "Marketing Category") and places only the relevant field on the page layout assigned to that specific team. This is less common but effective if the data needs to be stored in entirely different buckets.
Option B is incorrect because profiles themselves do not filter picklist values; they only control which record types a user can access.
정답:
Explanation:
Agentforce is designed to handle sophisticated, multi-step business processes that traditionally require human intervention. In a sales organization, a primary use case is Automating Lead Qualification. Unlike basic web bots (Option C) that follow a rigid, pre-defined script, an Agentforce agent can engage in natural language conversations with prospects. It can ask relevant discovery questions, handle objections, and determine if a lead meets the company’s "Qualified" criteria based on the information provided. Once qualified, the agent can autonomously update the Salesforce record or even book a meeting for a human sales representative. While AI can assist with content, "automating all marketing content" (Option B) is overly broad and typically handled by specialized marketing tools. Generating cold calls (Option A) involves voice technology and legal complexities that are not the core focus of the Agentforce platform's digital agent capabilities. Lead qualification represents a high-value, repeatable process that perfectly leverages the agent's ability to reason and interact with Salesforce data.
정답:
Explanation:
To ensure data integrity and guide sales reps through a structured process, a Platform Administrator should use a combination of tools. Opportunity Path (Option C) provides a visual representation of the stages and allows the admin to highlight "Key Fields" and "Guidance for Success" for each stage, making it clear what information is needed to progress. To enforce the entry of that data, Validation Rules (Option D) are used to prevent a user from moving to the next stage if specific fields are blank (e.g., AND(IsChanged(StageName), IsBlank(Discovery_Notes__c))). Additionally, marking fields as required on the Page Layout (Option A) ensures that the most fundamental data points are always captured. While Flow (Option B) can perform many tasks, it is not the primary way to mark fields as "required" in the UI. "Guided Selling" (Option E) is a specific term often associated with Salesforce CPQ rather than standard Opportunity management. Using Path, Validation Rules, and Page Layout requirements provides a robust framework for managing the sales lifecycle effectively.
정답:
Explanation:
To allow users to post snapshots of dashboard components and engage in discussions about data directly on the dashboard, the Platform Administrator must enable Feed Tracking for dashboards. In Salesforce, Chatter Feed Tracking allows changes to records and interactions to be tracked and shared in the Chatter feed. For dashboards specifically, enabling this feature allows users to "Follow" a dashboard and use the "Post to Feed" functionality on individual dashboard components. This is highly effective for management teams who want to call out specific successes or areas of concern by tagging team members in a post that includes the visual chart. Reporting snapshots (Option A) are used for historical trend reporting, not social sharing. Downloading charts (Option B) is a manual file-handling process rather than an integrated social feature. Setting the "View Dashboard As" (Option C) determines data visibility but does not control Chatter functionality.
정답:
Explanation:
Generative AI models are inherently probabilistic, meaning they do not produce the exact same output every time, even when given the same input. When a Platform Administrator uses the Prompt Builder to test a template, each "Preview" or "Test" execution initiates a fresh, unique call to the Large Language Model (LLM). Because the LLM considers a range of linguistic possibilities and probabilities for each word it generates, the resulting text will vary slightly (or significantly) with each iteration. This behavior is expected and is a core characteristic of generative AI. To ensure consistent and high-quality results, administrators must refine their instructions to be as specific as possible, narrowing the LLM's range of creative interpretation.
Options A, C, and D are incorrect because the Prompt Builder is designed to provide real-time feedback from the actual LLM to help administrators debug and perfect the prompt's logic before it is deployed to end-users or agents.
정답:
Explanation:
When a single object like Campaigns needs to support different "types" of marketing initiatives that require different fields or picklist values, the correct architectural solution is to use Record Types and Page Layouts. By creating distinct record types for "Email," "Trade Show," and "Webinar," the Platform Administrator can assign a unique Page Layout to each.
For example, the Trade Show layout might include fields for "Booth Number" and "Travel Costs," while the Webinar layout might include "Webinar URL" and "Platform Provider." This ensures that users only see the fields that are relevant to the specific type of campaign they are running, improving data quality and the user experience. While adding a custom field (Option B) would allow for categorization, it wouldn't hide irrelevant fields for different initiatives. Campaign Hierarchies (Option D) are used for relating parent and child campaigns but do not manage the specific data entry requirements for different initiative types.
정답:
Explanation:
When a field is removed from a page layout, the field itself is not deleted from the database; it is simply no longer displayed to the user. To restore it, the most direct method is to use the Page Layout Editor, find the field in the Fields Palette at the top of the editor, and drag it back onto the layout (Option D). This is the standard "undo" action for layout changes. Alternatively, if the layout has undergone many complex changes and the admin wants to revert to a known good state, they could restore it from a Sandbox (Option B) by redeploying the layout metadata.
Option C is incorrect because the Recycle Bin is for deleted records or fields, not for layout configurations.
Option A is a workaround that involves creating a new layout based on another, but it is not a direct way to "restore" the specific layout being edited.
정답:
Explanation:
Tasks and Events are both part of the Activity object, but they often require different picklist values for the standard Subject field. To achieve this, the Platform Administrator must manage the picklist values for the Subject field specifically for each record type or activity type. In the Object Manager, under the Activity object (or Task/Event objects individually in some setups), the admin should edit the Subject field. Because Task and Event are distinct entities with their own picklist value sets for the Subject field, the admin can add "Schedule Site Visit" and "Send Contract" to the Task Subject list and "Site Visit" and "Ride Along" to the Event Subject list. This ensures that when a user creates a Task, they only see task-related subjects, and when they create an Event, they see event-related subjects.
Option D is incorrect because it would mix all values together, causing confusion for the users.
Option A (Predefined Field Values) is used to set a single default value for a field when an action is clicked, but it does not manage the available list of options in a picklist.
정답:
Explanation:
In the Salesforce Lightning Experience, the Highlights Panel at the top of a record page is controlled by the Compact Layout. The compact layout determines which fields (up to 7) appear in the record header and in the hover-over details. To add a new custom field to this area, the Platform Administrator must go to the Object Manager for Accounts, select Compact Layouts, and either edit the existing primary layout or create a new custom one. After adding the custom text area field to the "Selected Fields" list and saving, the field will immediately appear in the Highlights Panel for users. It is a common misconception that the standard Page Layout editor (Option D) controls the highlights panel; while the page layout controls the "Details" section and "Related Lists," it does not manage the header area.
Option B might make the field easier to find in the details section but will not place it in the highlights panel.
정답:
Explanation:
When an AI agent like Agentforce transfers a conversation to a human support representative, the goal is a "warm handoff" where the rep can see exactly what the customer and the AI discussed. If reps are complaining about a lack of context, the most common administrative cause is that the Conversation History component (or Agent History component) has not been added to the Case Lightning Record Page. Without this component on their page layout, the rep sees the newly assigned case but cannot see the transcript of the preceding chat session. To resolve this, the Platform Administrator should use the Lightning App Builder to add the relevant history component to the Case page used by the support team.
Option D is less likely if escalation is working but context is missing.
Option A would prevent users from using Agentforce features but wouldn't specifically hide the transcript of a finished AI interaction. Ensuring the UI includes the conversation history is critical for maintaining high customer satisfaction during handoffs.
정답:
Explanation:
When users click the "New Report" button, they are presented with a list of Report Types, which act as templates determining which objects and fields are available for the report. Often, an org has many standard report types that are irrelevant or confusing to the average user. To "limit the kinds of reports" and simplify the user experience, a Platform Administrator can use the Select Report Types to Hide feature in the Report and Dashboard Settings. By hiding unnecessary or redundant report types, the admin ensures that users only see the specific templates that align with company reporting standards. This reduces the risk of users creating inaccurate reports using the wrong data models. Report Folder Sharing (Option B) controls who can view or edit existing reports, but it does not restrict the creation of new ones from specific templates. While creating Custom Report Types is a way to define what data is available, the specific act of "limiting" the visible list is handled by the "Hide" functionality.
정답:
Explanation:
The Activity Timeline is a standard Lightning component that displays open tasks, upcoming events, and past activities (like logged calls or sent emails) in a chronological view. If this timeline is missing from an Account page, it is usually because the component has been removed from the Lightning Record Page layout. To fix this, the Platform Administrator should open the Account record in the Lightning App Builder. From the list of standard components on the left, the admin must drag the Activities component onto the page canvas―typically in the right-hand column or a dedicated tab. Once the page is saved and activated, the timeline will be visible to users. Visibility of the timeline is a layout configuration, not a specific "Edit access" permission (Option B). Running a report (Option C) might confirm if data exists, but it won't fix the UI issue. There is no "button" for the Activity Timeline in the Object Manager (Option D); it is managed strictly as a component within the App Builder.
정답:
Explanation:
In Flow Builder, the most efficient and user-friendly way to handle dynamic user interfaces is through Component Visibility. This feature allows an administrator to set logic on individual screen components (like a picklist) so they only appear when specific criteria are met. In this scenario, the administrator would select the "Specific Search Engine" picklist component within the Flow Screen and configure its visibility to show only when the "Lead Source" screen component equals "Search Engine." This provides a "clean" user experience where the form adapts in real-time to the user's input without requiring the user to navigate to a new screen or trigger a validation error. Validation rules (Option D) are reactive and only tell the user they made a mistake after they try to save, whereas conditional visibility is proactive.
Option B is inefficient as it would require multiple screens and complex branching logic, whereas component visibility handles everything within a single screen element.
정답:
Explanation:
In Salesforce, a many-to-many relationship allows each record of one object to be linked to multiple records of another object and vice versa. This is achieved by using a Junction Object. A junction object is a custom object that sits between the two objects you want to relate. To implement this correctly, the administrator must follow two specific steps: first, create the custom object to serve as the "junction"; second, create two Master-Detail relationship fields on that new junction object. One master-detail field points to the first custom object, and the second points to the other. Because these are master-detail relationships, the junction record's visibility and deletion behavior are controlled by its parents. This structure allows for powerful reporting and roll-up summaries on both parent objects. Using simple lookup relationships (Option D) would not enforce the strict data integrity or the specific roll-up capabilities that define a true many-to-many relationship in the Salesforce architecture.
정답:
Explanation:
Agentforce SDR (Sales Development Representative) is an AI agent designed to autonomously engage with prospects to nurture leads and accelerate the sales pipeline. A core functionality of this agent is its ability to interact with potential customers by answering their specific questions about products or services. Crucially, these responses are grounded in company data, meaning the agent retrieves relevant information from the Salesforce Knowledge base, product catalogs, or other internal resources to provide accurate, brand-aligned answers. This ensures that the agent provides high-quality, trustworthy information without the "hallucinations" common in non-grounded AI. While the agent helps in lead qualification and nurturing, its primary value in an ecommerce or sales support context is providing immediate, context-aware assistance. It is not intended to replace humans in complex price negotiations (Option B) or serve purely as a coaching tool (Option C), but rather to act as a front-line digital worker that scales the sales team's reach by handling information-seeking queries autonomously.