
2026年最新のALS-Con-201試験解答最新版Fast2test ALS-Con-201のPDF問題集をダウンロードせよ(122問題と解答)
無料2026年最新のSalesforce Consultant ALS-Con-201問題集を提供しております!Fast2test
質問 # 28
Choose 1 option.
Cumulus Pharma wants its field sales reps to quickly see whether an account is a target account in their assigned territory alongside other key attributes. Using the out-of-the-box Provider Card template, the team needs additional indicators so that targeted accounts display "Target" and non-targeted accounts display "Not Target." How should the Agentforce Life Sciences Consultant configure this requirement?
- A. Add an item group element to a section and apply record-level filters on the Provider Account Territory Info source object to show only targeted accounts.
- B. Add a repeater element to a section, bind it to the Targeted Account field from the Provider Account Territory Info source object, and configure filter conditions.
- C. Add an item group element to a section, include the Targeted Account field from the Provider Account Territory Info source object, and configure visibility conditions.
正解:C
解説:
Option C is correct because the requirement is to display a conditional indicator on the Provider Card based on the Targeted Account field. Salesforce Help states that Provider Cards consolidate account information from scattered objects and fields into a single interface. Salesforce also documents that, in the Provider Card template, admins can use data from Provider Account Territory Information, including the Targeted Account field, to show whether an account is a target account.
The correct pattern is to add an item group element to a section, include the Targeted Account field from the Provider Account Territory Info source object, and configure visibility conditions so the card shows the appropriate label. When the field value indicates that the account is targeted, the card can show "Target." When it is not targeted, a separate condition can show "Not Target." Option A is not correct because applying record-level filters to show only targeted accounts would hide non-targeted accounts rather than displaying both "Target" and "Not Target" states. Option B is not the best answer because a repeater element is used for repeating sets of records; this requirement is a single account-level indicator. Therefore, item group elements with visibility conditions are the right configuration for the Provider Card indicator.
=========
質問 # 29
Choose 1 option.
An Agentforce Life Sciences Consultant configured the Inquiry record page to provide a comprehensive history view. Users need to see a chronological list of all key events and changes associated with the inquiry.
Which step must the consultant take to expose this historical data on the Lightning record page?
- A. Add the Inquiry History related list to the page layout.
- B. Enable Field History Tracking on the Inquiry object and add the History component.
- C. Drag the Timeline component to the page and configure the component details.
正解:C
解説:
Option A is correct because Salesforce Help for setting up the Inquiry record page for Medical Inquiries explicitly states that, to view timeline details for inquiries, the consultant should drag the Timeline component to the page. The requirement in the question is to expose a chronological list of key events and changes associated with the inquiry. That is exactly the purpose of the Timeline component on the Medical Inquiries record page.
Salesforce also documents Enhanced Timeline for Life Sciences Cloud, explaining that the Enhanced Timeline component shows key events relating to a person or a record. This supports the use case of giving users a consolidated, chronological view of relevant inquiry activity, rather than requiring them to inspect multiple related lists or audit records separately.
Option B is not the best answer because field history tracking and the standard History component are used for field-level audit history, not the Life Sciences Medical Inquiries timeline experience. Option C is also incorrect because adding an Inquiry History related list would expose related records, but it would not provide the configured timeline component experience described in Salesforce's Medical Inquiries setup documentation.
Therefore, the consultant must drag the Timeline component onto the Lightning record page and configure its component details for the Inquiry record page.
質問 # 30
Choose 1 option.
A field sales rep is planning their route for the week. The system should recommend the specific days and times when a Healthcare Provider (HCP) is most likely to accept a visit, based on historical engagement data. This feature must be enabled in the Visit/Calendar settings.
Which setting supports this optimization?
- A. Configure Operating Hours on the Account.
- B. Set up Provider Best Time.
- C. Enable Best Time Settings.
正解:C
解説:
The correct answer is B because the requirement is to enable the Life Sciences visit and calendar setting that surfaces best-time recommendations for planning. Salesforce Help for Life Sciences Calendar states that users can schedule visits and other events while using best time recommendations. Salesforce also provides guidance for configuring filters to find best visit times, explaining that users can filter accounts by a healthcare professional's preferred engagement time to plan and schedule visits more effectively.
The key phrase in the question is that the feature must be enabled in Visit/Calendar settings. "Best Time Settings" is the configuration area that supports the optimization. Once enabled, the system can use historical engagement patterns and preferred engagement timing to help reps plan visits when HCPs are more likely to be available or receptive.
Option A is close in meaning, but "Set up Provider Best Time" describes the capability more generally rather than the setting in Visit/Calendar settings. Option C is incorrect because operating hours represent general availability windows for an account or location. Operating hours can help prevent scheduling at inappropriate times, but they do not provide intelligent recommendations based on historical engagement data. Therefore, the consultant should enable Best Time Settings.
=========
質問 # 31
Choose 1 option.
How often can Territory Management batch jobs be scheduled to execute automatically?
- A. Monthly
- B. Hourly
- C. Every 12 hours
正解:B
解説:
The correct answer is A because Salesforce Life Sciences Territory Management batch jobs can be scheduled with an hourly frequency. Salesforce Help for running Territory Management jobs states that, from the Life Sciences Commercial Admin Console, the job can be scheduled hourly, every selected hours, by selecting the hour from the dropdown. This confirms that hourly scheduling is a supported automatic execution option for Territory Management batch jobs.
Territory Management batch jobs are important because Life Sciences territory configuration affects field execution, account alignment, provider access, and downstream engagement processes. Scheduling these jobs automatically helps ensure that territory-related processing runs on a predictable cadence without requiring administrators to manually start each batch job. When the question asks how often the jobs can be scheduled to execute automatically, the available option that matches Salesforce's documented scheduling capability is Hourly.
Option B, Every 12 hours, may sound plausible because some enterprise batch processes use longer intervals, but it is not the best answer because Salesforce's documented configuration describes hourly scheduling and selecting the hour interval. Option C, Monthly, is also incorrect because monthly execution would be too infrequent for many territory-management operational updates and is not the option reflected in the documented batch-job scheduling guidance. Therefore, the consultant should identify Hourly as the correct scheduling frequency.
質問 # 32
Choose 1 option.
Cumulus Pharma wants to track email interactions and in-person visits as two distinct types of interactions. The system should count these separately to ensure field sales reps meet their target of six emails and three visits. The solution must use standard Activity Plan configuration objects to categorize these interactions based on the Visit Channel.
Which object defines these distinct interaction categories?
- A. Provider Activity Goal
- B. Provider Activity Plan Interaction
- C. Provider Activity Measure Type
正解:C
解説:
Option A is correct because Provider Activity Measure Type defines how engagement activities are measured and categorized in Activity Plans. Salesforce Help explains that an activity can be an interaction with a healthcare professional, such as a visit, and that a channel is the medium in which the interaction or activity occurs. This is exactly the requirement: Cumulus Pharma wants to distinguish email interactions from in-person visits so each channel can be counted separately against the field rep's targets.
Salesforce Help for creating Activity Plans also states that admins should verify that a provider activity measure type has been created to track provider engagement activities. This confirms that Provider Activity Measure Type is the setup object used to define what kind of activity is being measured.
Option B, Provider Activity Goal, is not correct because it represents the target or goal assigned to providers or reps, such as six emails or three visits. It does not define the activity category itself. Option C, Provider Activity Plan Interaction, is also not the best answer because the question asks which configuration object defines the distinct interaction categories. The measure type is the categorization layer that can use Visit Channel, such as Email or In-Person, to count interactions separately. Therefore, Provider Activity Measure Type is the correct answer.
=========
質問 # 33
Choose 1 option.
A field sales rep is creating a visit from the calendar. The rep notices that only Healthcare Provider (HCP) accounts are available in the selected target account list, even though Healthcare Organization (HCO) accounts are aligned to the territory and available elsewhere in the app.
What is the cause of this issue?
- A. The selected target account list is configured to include only HCP accounts.
- B. The Account record type configuration restricts which account types appear in the calendar in Account Management settings.
- C. The Account record type settings are configured to display only the HCP record type in Planner Administration.
正解:A
解説:
Option C is correct because the issue is isolated to the selected target account list, not to the overall availability of HCO accounts in the territory or application. Salesforce Life Sciences Cloud supports Lists and Filters so users can quickly identify a target group of accounts. These lists can be manually curated or filtered, meaning the accounts shown depend on the criteria or membership of the specific list being used. If only HCP accounts appear while HCO accounts are still aligned to the territory and visible elsewhere, the most likely cause is that the selected target account list itself includes only HCP accounts. Salesforce's Life Sciences Cloud Developer Guide describes Lists and Filters as a way to quickly identify target account groups, and the LifeScienceAccountList object represents account list types such as filter, static list, and routine list.
Option A is not the best answer because Planner Administration record type settings would more broadly control planner behavior, not only one selected target account list. Option B is also not the best answer because Account Management record type configuration would affect how account types are configured or displayed more generally. The question states that HCO accounts are aligned and available elsewhere, which eliminates a broad record type or account management restriction. The problem occurs only when using the selected target account list during visit creation. Therefore, the consultant should review and correct the target account list criteria or membership so that both HCP and HCO accounts are included when needed.
=========
質問 # 34
Choose 1 option.
After a remote call concludes, the operations director wants to verify that the interaction took place and review the engagement metrics. The data should be stored on the standard object used for tracking interactions in Agentforce Life Sciences.
Which object stores the details of the executed Remote Engagement?
- A. Remote Call
- B. Provider Visit
- C. Video Log
正解:A
解説:
Option B is correct. In Salesforce Life Sciences Cloud Remote Engagement, the standard object used for the executed video engagement details is the remote-call/video-call record. Salesforce's Life Sciences Developer Guide includes the VideoCall object for Remote Engagement and describes it as storing important information about the remote engagement, including its relationship to the associated provider visit. This aligns with the requirement to verify that the remote interaction occurred and review engagement metrics after the call concludes.
Provider Visit is related to the customer interaction and can represent the overall HCP visit context, but it is not the most precise object for the executed video-call details. The remote engagement session itself needs its own object because it can store video-specific information such as call status, timing, service details, and other remote-session metadata.
Option C, Video Log, is not the correct standard Life Sciences object name in the Salesforce documentation. "Video Log" sounds like a generic audit or logging object, but the documented Remote Engagement object is VideoCall. Since the answer options use "Remote Call" rather than "VideoCall," Remote Call is the closest and intended answer for the standard remote engagement execution record. Therefore, the consultant should use the Remote Call/VideoCall record to review the executed Remote Engagement details.
=========
質問 # 35
Choose 1 option.
A data analyst wants to query the total interaction target for a Healthcare Provider (HCP) for the current period. The analyst needs to understand the high-level association of an Account to an Activity Plan as the parent record and which child object contains the specific targets.
Which objects represent this association?
- A. Parent: Provider Activity Goal; Child: Provider Activity Goal Measure
- B. Parent: Assessment Task; Child: Assessment Indicator
- C. Parent: Activity Plan; Child: Account Goal
正解:A
解説:
The correct answer is B because the Provider Activity Goal object represents the parent-level association between a provider account and an activity plan, while Provider Activity Goal Measure stores the specific measurable targets associated with that goal. Salesforce's Life Sciences Cloud Developer Guide describes ProviderActivityGoal as storing progress toward the target for an account, including the percentage of the overall goal achieved by completed activities. Salesforce's Life Sciences standard objects also include ProviderActivityGoalMeasure, which represents the activity goal measure details.
In practical reporting and querying terms, the analyst should use Provider Activity Goal to identify the HCP/account's association to the plan period, and then query the related Provider Activity Goal Measure records to retrieve the specific target values, such as total interaction target, channel target, product target, or other measurable plan goals depending on configuration.
Option A is incorrect because Assessment Task and Assessment Indicator are used for assessment-style workflows, not for storing provider activity-plan target measures. They may capture structured assessment responses, but they do not represent activity-plan goal targets. Option C is incorrect because while Activity Plan is the high-level planning object, it is not the direct account-to-plan parent association described in the question, and "Account Goal" is not the specific Life Sciences child object used for provider activity target measures. Therefore, the correct parent-child pairing is Provider Activity Goal and Provider Activity Goal Measure.
=========
質問 # 36
Choose 1 option.
Cumulus Pharma implemented the Affiliations feature in Agentforce Life Sciences for Customer Engagement to map relationships between Healthcare Providers (HCPs) and Healthcare Organizations (HCOs). The Agentforce Life Sciences Consultant configured the Affiliation Reverse Role Mapping in the Admin Console to define how roles should translate, for example, Attending translates to Employing. However, users report that when they create a new Affiliation record, the system fails to automatically generate the record of the reverse relationship.
Which trigger handler must the consultant enable to complete this action?
- A. AffiliationReciprocalHandler
- B. HardAffiliationHandler
- C. AffiliationUniquenessHandler
正解:A
解説:
The correct answer is C because reverse affiliation creation is handled by the AffiliationReciprocalHandler. Salesforce Help for Life Sciences trigger handlers identifies AffiliationReciprocalHandler as the handler that manages reciprocal affiliations. The same documentation notes behavior related to reciprocal affiliations and affiliation type handling, which directly matches the scenario where a newly created affiliation should automatically create the reverse relationship.
Affiliation Reverse Role Mapping defines how the relationship role should translate between the original and reciprocal records. For example, if an HCP is "Attending" at an HCO, the reverse relationship may show the HCO as "Employing" or otherwise related to the HCP, depending on the configured mapping. However, defining the mapping alone does not execute the automation. The trigger handler must be active so that when users create a new Affiliation record, Salesforce can generate the reciprocal Affiliation record using the configured reverse role mapping.
Option A, AffiliationUniquenessHandler, is incorrect because uniqueness logic prevents duplicate or invalid affiliation records; it does not create the reverse relationship. Option B, HardAffiliationHandler, is also incorrect because it is not the handler identified for reciprocal affiliation generation. Since the missing behavior is automatic creation of the reverse affiliation, the consultant must enable AffiliationReciprocalHandler.
質問 # 37
Choose 1 option.
A Healthcare Provider (HCP) has a primary address in a zip code aligned to the San Francisco South territory but practices at a hospital located in the San Francisco North territory. The business requires the HCP to be automatically mapped to the San Francisco North territory based on the practice location.
Which assignment rule configuration meets this requirement?
- A. Assign the HCP to the San Francisco North territory and exclude the record from future assignment rules.
- B. Create a territory geo assignment rule that aligns the HCP based on the zip code of their primary address.
- C. Set up an affiliation assignment rule that aligns the HCP based on the relationship with the hospital.
正解:C
解説:
Option C is correct because the business requirement is based on the HCP's relationship with a hospital, not the HCP's primary address. Salesforce Life Sciences Cloud Affiliations help organizations understand and map relationships between Healthcare Providers and Healthcare Organizations. Salesforce Help also describes Territory Alignment for Affiliated Accounts, where affiliated accounts can be aligned to territories based on affiliation relationships. This fits the scenario: the HCP's primary address points to San Francisco South, but their practice relationship with a hospital points to San Francisco North.
Option A is not the best answer because manually assigning the HCP to San Francisco North and excluding the record from future assignment rules creates a one-off exception. That may work temporarily, but it does not meet the requirement for automatic mapping based on practice location and affiliation. Option B is incorrect because it would use the HCP's primary address zip code, which the scenario says is aligned to San Francisco South. That would produce the wrong territory.
An affiliation assignment rule aligns the HCP based on their relationship with the hospital, so the HCP can be mapped to San Francisco North when the hospital affiliation drives the business alignment. Therefore, the correct configuration is to set up an affiliation assignment rule based on the HCP-HCO relationship.
=========
質問 # 38
Choose 1 option.
A field sales rep wants to bring a Medical Science Liaison (MSL) into a scheduled remote visit with a Healthcare Provider (HCP) to answer a complex clinical question. The system must track the MSL's participation in the visit.
Which standard Visit Management action supports this requirement?
- A. Create a new Visit record for the MSL.
- B. Send the meeting link to the MSL by email.
- C. Add Visitors (Users) to a Visit.
正解:C
解説:
The correct answer is C because Salesforce Life Sciences Visit Management supports adding internal users as visitors to a visit. Salesforce Help for Add Internal Users as Visitors states that administrators can configure the visitors feature so field reps can record internal colleagues who participate in visits and automatically share visit data with them. This directly matches the requirement to include an MSL in the scheduled remote visit and track that person's participation.
The MSL is not the primary HCP attendee and does not need a separate visit record. Instead, the MSL is an internal participant supporting the visit. Using the standard Add Visitors (Users) to a Visit action keeps the visit record intact while documenting the MSL as a participating internal user. It also supports better compliance, collaboration, and reporting because the MSL's involvement is recorded against the actual visit.
Option A is incorrect because creating a separate Visit record would fragment the visit history and could cause duplicate or inconsistent reporting. Option B is incomplete because emailing the meeting link may help the MSL join the session, but it does not track the MSL's participation in the Life Sciences Visit Management data model. The correct standard action is Add Visitors (Users) to a Visit.
=========
質問 # 39
Choose 1 option.
Cumulus Pharma has configured and activated a new agent using the Life Sciences Field Sales template. However, when a field sales rep attempts to use the agent to generate a summary for a targeted Healthcare Provider (HCP), they are unable to access the feature. Reps must have the privileges required to interact with these capabilities.
Which permission set should the Agentforce Life Sciences Consultant assign to grant access to these Agentforce features?
- A. Access Life Sciences Customer Engagement Agentforce
- B. Agentforce Service Agent User
- C. Life Sciences Commercial User
正解:A
解説:
Option C is correct because Salesforce Help identifies "Access Life Sciences Customer Engagement Agentforce" as the permission required for Life Sciences Customer Engagement Agentforce capabilities. In the Salesforce Help reference for the Life Sciences "Generate Healthcare Provider Summary" action, Salesforce lists the required access as Access Life Sciences Customer Engagement Agentforce. It also notes that, to run flows associated with agent actions, users need the Run Flows app permission or access to the individual flows.
This directly matches the scenario. The Life Sciences Field Sales agent template has already been configured and activated, but the field sales rep cannot use the agent-generated HCP summary capability. That means the issue is not the existence of the agent or the template; it is the user's permission to access the Life Sciences Customer Engagement Agentforce features. Salesforce's Account Summarization permissions documentation also references Access Life Sciences Customer Engagement Agentforce as part of the permission setup for account summarization, alongside standard Life Sciences user permission sets.
Option A, Life Sciences Commercial User, is not specific enough to grant access to these Agentforce capabilities. Option B, Agentforce Service Agent User, relates to Agentforce service use cases and is not the Life Sciences Customer Engagement permission named in the documentation. Therefore, the consultant should assign Access Life Sciences Customer Engagement Agentforce.
質問 # 40
Choose 1 option.
Cumulus Pharma notices that synchronization transactions have failed, impacting sales users' ability to view recently created records offline in the Agentforce Life Sciences mobile app.
What should an Agentforce Life Sciences Consultant recommend to identify potential synchronization transaction failures?
- A. Leverage Simulation Mode to test transactions.
- B. Check Event Monitoring Logs in the Admin Console.
- C. Enable Send Warning Emails for sales users.
正解:A
解説:
The correct answer is C because Salesforce Life Sciences synchronization management guidance specifically positions Simulation Mode as the tool used to proactively identify and fix potential synchronization problems before they affect end users. Salesforce describes synchronization management as a way to ensure efficient synchronization by resolving errors quickly and using Simulation Mode to find potential problems before they impact users.
In this scenario, sales users are unable to view recently created records offline in the Agentforce Life Sciences mobile app because synchronization transactions have failed. Offline mobile availability depends on successful synchronization between Salesforce and the mobile app. A consultant should therefore recommend testing synchronization behavior in Simulation Mode, because it helps validate whether records, transactions, and configuration changes will synchronize successfully before users rely on them in the field.
Option A is not the best answer because Event Monitoring Logs are broader Salesforce security and activity logs; they are not the recommended Life Sciences-specific mechanism for proactively identifying synchronization transaction failures in the offline mobile synchronization process. Option B is also incorrect because warning emails notify users or administrators after certain conditions occur, but they do not test synchronization transactions or identify potential sync failures before users are affected. Simulation Mode is the most targeted and preventive administrative tool for this issue.
質問 # 41
Choose 1 option.
An Agentforce Life Sciences Consultant is designing the data model for a new product launch. Specific slide decks must be linked to the "Immunexis" product so that detailed analytics can be generated regarding which products are being detailed during visits. The solution must use the standard Agentforce Life Sciences for Customer Engagement data model.
Which object should the consultant use?
- A. Product Media Link
- B. Presentation Linked Page
- C. Presentation Page Product
正解:C
解説:
Option B is correct because Presentation Page Product is the standard Life Sciences Cloud object that links presentation content to products. Salesforce's Life Sciences Cloud Developer Guide states that PresentationPageProduct represents the link between a presentation page and a product, and may also include a connection to product guidance or product messages. This directly matches the requirement to link Immunexis to specific presentation pages or slide content so analytics can identify which products were detailed during visits.
Salesforce's Intelligent Content data model also includes Presentation, Presentation Linked Page, Presentation Page, Presentation Page Product, Product2, Life Science Marketable Product, Provider Visit, and visit-detailing objects. This confirms that Presentation Page Product is part of the standard content and detailing analytics architecture for Life Sciences Customer Engagement.
Option A, Presentation Linked Page, is not the best answer because it links pages within presentation structure, but it does not specifically represent the product association. Option C, Product Media Link, is not the documented standard object for connecting Life Sciences presentation pages to products. Salesforce also provides a Presentation Page Product API resource for creating or updating product and guidance associations for a presentation page, reinforcing that this is the intended object.
Therefore, the consultant should use Presentation Page Product.
質問 # 42
Choose 1 option.
At Cumulus Pharma, field sales reps report that the Next Best Action component is not visible on the account profile, even though the recommendation data is confirmed to be loaded and synced to mobile.
What is the cause of this issue?
- A. The page layout uses the Einstein Next Best Action component instead of the Life Sciences Next Best Action component.
- B. The Life Sciences Next Best Action strategy has not been activated, so recommendations cannot be rendered on the page.
- C. The user profile does not have permission to view the Next Best Action recommendation data.
正解:A
解説:
Option B is correct because Life Sciences Cloud for Customer Engagement uses Life Sciences-specific Next Best components for the mobile and account-profile experience. Salesforce's Life Sciences Next Best documentation explains that Next Best Action suggests timely actions such as visits and emails, and the Life Sciences Customer Engagement data model includes Life Sciences-specific recommendation objects such as Territory Account Recommended Action, Territory Account Product Message Score, and Territory Account Score. These are not the same as the generic Einstein Next Best Action component and strategy experience.
The question states that the recommendation data is already loaded and synced to mobile. That removes the most likely data-load or synchronization issue. If the data exists but the component is not visible on the account profile, the issue is most likely the wrong component placement. The page must use the Life Sciences Next Best Action component that is designed to render Life Sciences recommendations in the Life Sciences mobile app.
Option A is not the best answer because inactive strategy logic would generally prevent recommendations from being generated or returned, but the scenario confirms the recommendation data is present. Option C is also less likely because a permission problem would typically prevent access to the recommendation records or data, not specifically indicate that the component itself was configured incorrectly. Therefore, the consultant should replace the generic Einstein Next Best Action component with the Life Sciences Next Best Action component.
=========
質問 # 43
Choose 1 option.
At Cumulus Pharma, field sales reps use the Next Best Customer component on their iPads to prioritize and identify accounts for outreach. Reps report that when they sort recommendations by distance, the sorting does not work as expected because all accounts display a distance of 0. They have confirmed that location services are enabled on the iPad device.
What is the cause of this issue?
- A. The account primary address records are missing geolocation data, so the system cannot calculate distance correctly.
- B. Distance calculation requires the account to be aligned to the user's territory, and unaligned accounts show a distance of 0.
- C. The Next Best Customer component requires a manual refresh before distance-based sorting can be applied.
正解:A
解説:
The correct answer is A because distance-based sorting in the Next Best Customer mobile component requires geolocation data on the account's relevant address. Salesforce Help for configuring Next Best Customer settings for the mobile app states that, to ensure accounts are accurately sorted by distance, geolocation data must be captured for the primary address or preferred address. Salesforce Help also explains that if no preferred address is available, distance is calculated using the account's primary Contact Point Address.
The reps already confirmed that location services are enabled on the iPad, so the issue is not the mobile device's ability to determine the user's current location. The missing piece is the account-side location data. If the primary or preferred address does not contain valid latitude and longitude values, the component cannot accurately calculate the distance between the rep and the account. As a result, accounts may appear with a distance of 0 or behave incorrectly when sorted by distance.
Option B is incorrect because a manual refresh does not solve missing geolocation data. Refreshing the component may reload records, but it cannot calculate distance without valid address coordinates. Option C is also incorrect because territory alignment is important for determining which accounts are relevant to the rep, but the distance calculation itself depends on geolocation data. Therefore, the root cause is missing geolocation data on the account's primary or preferred address.
=========
質問 # 44
Choose 1 option.
Cumulus Pharma requires the Agentforce Life Sciences for Customer Engagement Account Summary to include historical data from the Account record and related Healthcare Provider and Contact Point Address records.
Which configuration defines the object relationships for this summary?
- A. Actionable Relationship Center
- B. Affiliation Alignment Rules
- C. Cross-Object Field History Graph
正解:C
解説:
Option A is correct because Account Summarization uses a cross-object graph to define which objects and relationships are included in the generated summary. Salesforce Help states that administrators can create cross-object graphs from a predefined Account Summarization template to provide a complete view of an account and its related objects. This directly matches the requirement to include Account data and related Healthcare Provider and Contact Point Address information in the summary.
The phrase "historical data" is also important. Salesforce Account Summarization setup includes configuring history tracking for the fields included in the template, so Agentforce can summarize recent changes from the selected objects and fields. The cross-object graph defines the relationship structure, while field history tracking provides the change history used in the summary.
Option B, Actionable Relationship Center, is not the best answer. Actionable Relationship Center is used to visualize related records and relationships, but the Account Summary configuration specifically relies on cross-object graphs. Option C, Affiliation Alignment Rules, is unrelated because those rules support territory alignment for affiliated accounts, not Account Summary object relationships. Therefore, the consultant should use a Cross-Object Field History Graph to define the Account, Healthcare Provider, Contact Point Address, and related-object structure used by Agentforce Account Summary.
=========
質問 # 45
Choose 1 option.
An Agentforce Life Sciences Consultant at Cumulus Pharma needs to configure Medical Inquiries to ensure a compliant workflow between departments. The requirement states that field sales reps must only be permitted to draft, sign, and submit inquiries, while Medical Science Liaisons (MSLs) must only be permitted to assign and respond to them.
What should the consultant configure on the Medical Inquiry object to enforce these specific user actions?
- A. Create a custom formula field to define the allowed actions based on the user's role and assigned permissions.
- B. Create record types for Sales and Medical roles with unique page layouts to restrict available buttons.
- C. Create a Flow action to dynamically evaluate user credentials during the Inquiry lifecycle.
正解:B
解説:
The correct answer is A from the available options, because the requirement is to control which user actions are exposed to different roles during the Medical Inquiry lifecycle. Salesforce Help for Medical Inquiries states that organizations can define relevant workflow actions for tasks users perform in the medical inquiry process, such as inquiry submission and assignment. Salesforce also describes a compliant role separation where field sales reps can submit medical inquiries, while Medical Science Liaisons can assign and respond to them.
The ideal Salesforce Life Sciences configuration pattern is to use Medical Inquiry workflow actions and workflow paths to control status transitions, actions, and permissions. However, among the provided answer choices, record types with role-specific page layouts is the only option that directly supports restricting the available buttons and actions by user role. This enables sales users to see only draft, sign, and submit actions, while MSL users see only assignment and response actions.
Option B is incorrect because a formula field can calculate or display logic, but it cannot enforce workflow actions or user interaction permissions by itself. Option C is also incorrect because a Flow action could add custom logic, but it is not the standard configuration approach for restricting Medical Inquiry lifecycle actions. Therefore, the best available answer is A.
=========
質問 # 46
Choose 1 option.
Cumulus Pharma's field sales reps use the Medical Insights feature in Agentforce Life Sciences for Customer Engagement to record insights from their engagements with Healthcare Providers (HCPs). Sales leadership determines that all reps in a territory can benefit from medical insights captured from HCPs in that territory.
Which out-of-the-box configuration makes it possible for reps in the same territory to collaborate on medical insights?
- A. MedicalInsightSharingHandler
- B. MedicalInsightTerritoryAvailabilityHandler
- C. MedicalInsightAvailabilityHandler
正解:A
解説:
Option B, MedicalInsightSharingHandler, is correct because the requirement is about collaboration and access to medical insight records by users in the same territory. Salesforce Help describes the Medical Insights tab as enabling users to view their own insights as well as insights captured by users with the same profile within their territories. That means Life Sciences Cloud supports territory-based visibility for Medical Insights so that relevant field users can collaborate around insights collected from HCP engagements.
The key word in the question is "collaborate." Collaboration requires record sharing, not merely record availability. MedicalInsightSharingHandler is the out-of-the-box configuration that aligns with sharing medical insight records across the appropriate users, such as reps associated with the same territory. MedicalInsightAvailabilityHandler is not the best answer because "availability" typically controls whether a feature, action, or object behavior is available in a given context; it does not directly describe record sharing between users. MedicalInsightTerritoryAvailabilityHandler is also not correct because the Salesforce-documented sharing behavior for Medical Insights is about viewing insights captured within the user's territories, and the named handler that most directly supports that requirement is the sharing handler.
Therefore, when Cumulus Pharma wants field sales reps in the same territory to access and collaborate on relevant HCP medical insights, the correct out-of-the-box configuration is MedicalInsightSharingHandler.
質問 # 47
......
ALS-Con-201試験解答問題集:https://jp.fast2test.com/ALS-Con-201-premium-file.html(122問題と解答)