The Salesforce Certified Experience Cloud Consultant (EX-Con-101) (Experience-Cloud-Consultant)

Three key features of Metadata API are A, B, and C. Metadata API is an API that allows you toretrieve, deploy, create, update, or delete customization information in your Salesforce org, such as custom objects, fields, tabs, or pages. Metadata API is ideal when multiple work streams are involved, because it allows you to manage changes across different environments and teams. Metadata API can be used programmatically as well as declaratively, because it supports both code-based tools and point-and-click tools for working with metadata. Metadata API is ideal for when the changes are complex, becauseit allows you to handle fine-grained customizations and dependencies.

The first step to create a site is to enable Digital Experiences in your org. This will allow you to access the Experience Cloud site creationwizard, where you can choose a template, a domain name, and a URL for your site.

Sharing rules allow you to extend sharing access to users in public groups, roles, or territories. You can use sharing rules to share records owned by realtors at DR with social workers at NMH, based on criteria such as record type, field value, or ownership.

UC should create two separate digital experiences for its different customer segments and employees. This will allow UC to provide different features, content, and branding for each experience, as well as control the access and visibility of records. For example, UC can create a customer service site for B2C customers and employees, where they can view and create cases, access knowledge articles, and chat with agents. UC can also create a partner portal for B2B customers and employees, where they can view and update billing information, access contracts, and work on low-severity B2C customer issues.

To support the sharing requirement of using advanced sharing rules for thecustom object, CK should grant two user license types to customers: Partner Community User and Customer Community Plus Login User. These license types allow customers to access custom objects and a subset of standard CRM objects, such as accounts, contacts, cases, and dashboards. These license types also support advanced sharing features, such as role hierarchy, sharing rules, manual sharing, and Apex sharing.

To give customers the ability to add authorized users toview usage, billing, and payment history, UMS should grant Delegated External User Administrator permission to customers. Delegated External User Administrator is a permission that allows customers to create new users or reset passwords for other customersin their own account. UMS can use Delegated External User Administration, which isa feature that allows UMS to assign specific users as delegated administrators who can manage external users in their own accounts.

To create a partner user from an enabled partner account, the correct sequence of steps is C. A partner user is a user who has access to your Experience Cloud site through a partner account. A partner account is an account that has the Is Partner checkbox enabled. To enable a partner user, you need to view the partner account contact, select Manage External User, select Enable Partner User, edit the user record to assign the correct role and profile, and save.

To prevent usability issues, CK should provision and activate CDN in those regions where traffic is high. A CDN is a network of servers that delivers cached static content from websites to users based on the geographic location of the user. By provisioning and activating CDN in high-traffic regions, CK can improve the performance and availability of their public site for their users.

Salesforce Content Delivery Network (CDN) is a feature that allows you to improve the performance of your site by caching static resources, such as images, JavaScript, and CSS files. However, changing the Salesforce CDN has some implications, such as:

Changing the Salesforce CDN impacts definitions of all Lightning Web Components used in public pages. You need to redeploy your components after changing the CDN to ensure that they work properly.

Changing the Salesforce CDN does not affect SAML SSO settings for all custom URLs in that domain. SAML SSO settings are independent of the CDN settings.

Changing the Salesforce CDN does not impact the AppExchange packages in the org that use Documents object. Documents object is not affected by the CDN settings.

Changing the Salesforce CDN does not overwrite LDS defaults. LDS defaults are not affected by the CDN settings.