Platform-App-Builder 無料問題集「Salesforce Certified Platform App Builder」

（A）Add a Twitter Quick Action to the mobile navigation.

（B）Add an AppExchange Lightning Component to the mobile app.

（C）Add a formula field to the Contact page layout.

（D）Add the Twitter component to mobile view Lightning pages.

（A）Cannot add fields to page layouts.

（B）Cannot create lookup relationships.

（C）Cannot see existing relationships between objects.

（D）Cannot create formula fields.

（A）Include Surveys as a Case related list

（B）Case Validation Rules

（C）Guided Action Flows on the record page

（D）Add Path to the top of the Case layout

（A）Decimal places and character limits

（B）Multiple currencies

（C）Field-Level Security

（D）Record type picklist value assignments

（E）Validation Rules

（A）Make the record type hidden to support users; update sharing roles to private.

（B）Create permission set group for Case that includes Platinum and Diamond record types.

（C）Update the organization-wide defaults to private for Case.

（D）Update the support team profile to remove the Bronze record type.

（A）Create a master-detail relationship held on Applicant__c to Application__c

（B）Create a master-detailrelationship field on Application__c to Open.Position__c

（C）Create a master-detail relationship field on Applicant__c to Apphcabon_c

（D）Create a master-detail relationship on Open_Position__c to Application__c

（A）Update the custom field's Field Level Security in setup to allow the agent read-only access to the field.

（B）Create a new profile to allow for read-only access to the field via Field Level Security and assign it to the agent

（C）Create a permission set that allows read-only access to the field via Field Level Security and assign it to the agent.

（D）Update the Customer Service Profile already assigned to the agent to allow for read-only access to the field via Field Level Security

（A）An open-source custom development

（B）An open-source unmanaged package

（C）An unmanaged package from AppExchange

（D）A managed package from AppExchange

（A）Create a master-detail relationship from Testimonial__c to Accountand a lookup relationship from Testimonial__c to Contact.

（B）Make both the Contact and Account fields required on the Testimonial__c object and create lookup relationships fromTestimonial__c to Contact and to Account.

（C）Create a lookup relationship from Testimonial__c to Account and a master-detail relationship from Testimonial__c to Contact.

（D）Make Testimonial__c a junction object between Account and Contact using master-detail relationships.

（A）Email relay to the configured host enabled.

（B）Email configured for SMTP authentication.

（C）Email deliverability set to system email only.

（D）Email deliverability set to no access.

（A）Dynamic Action

（B）Dependent Picklist

（C）Field Update

（D）Global Picklist Value Set

（A）Update the account search layout's view filter settings.

（B）Update the account search filter fields.

（C）Update the account search layouts accounts tab columns displayed.

（D）Update the account search layouts search results columns displayed.

（A）Activities

（B）Path

（C）Chatter

（D）Highlights panel

（A）Create a Text filed for the original Invoice Number and an AutoNumber field for the Salesforce Invoice Number.

（B）Create an AutoNumber field and migrate the Invoices

（C）Create a Text field, then change it to AutoNumber after the migration.

（D）Create a Text field and mark it as a unique external ID field.

（A）Allowingthe end user to choose the record type

（B）Redirecting the end user to the detail page of the target object

（C）Specifying the fields and layout of the action.

（D）Pre-Defining field values on the target object.

（A）All profiles

（B）Internal profiles

（C）Standard profiles

（D）No profiles

（A）Create both customer and dealer as accounts, create account teams on each account and associate the dealer records with the parent account.

（B）Create a single account record, add each rep as a contact and create a custom dealer object.

（C）Create a single parent record, add each rep as a contact to the parent account and add each dealer as a child record.

（D）Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.

（A）Use a private sharing model granting record access using custom setting; manage field access with record types and page layouts

（B）Use a private sharing model granting record access using custom setting; manage field access with page layouts and field level security

（C）Use a private sharing model granting record access using hierarchy; manage field access with record types and field-level security

（D）Use a private sharing model granting record access using hierarchy; manage field access with field-level security

（A）Process Builder

（B）Flow Builder

（C）Scheduled Apex

（D）Escalation rules