To allow UC's customers to log in to CK's site, an Experience Cloud consultant should recommend establishing SSO between the two Experience Cloud sites by using one org as an identity provider and the other org as a service provider. SSO is a feature that allows users to authenticate with one system and access multiple systems without entering their credentials again. To use SSO between two Experience Cloud sites, you need to use one org as an identity provider (IdP), which is the system that verifies the user's identity and issues a security token. You also need to use the other org as a service provider (SP), which is the system that accepts the security token and grants access to its resources.

Two considerations for creating partner users and granting access are B and C. Partner users are external users who access your Experience Cloud site through a partner account. A partner account is an account that has the Is Partner checkbox enabled. To create partner users and grant access, you need to assign them a license type and a profile. Two license types that are suitable for partner users are Partner Community and Customer Community Plus. These license types allow partner users to access standard CRM objects, such as accounts, contacts, leads, opportunities, and cases, as well as custom objects and tabs. They also allow partner users to use roles and sharing rules to share records with other users.

To implement SAML 550 for the Experience Cloud site, the UC administrator should use thesite login URL as an endpoint where SAML assertion is made. SAML 550 is a protocol that allows users to authenticate with a third-party identity provider and access Salesforce resources without entering their Salesforce credentials.
The site login URL is the URL that users use to access the Experience Cloud site. By using the site login URL as an endpoint, the UC administrator can configure SAML settings to redirect users to the identity provider for authentication and then back to the Experience Cloud site.

The ExperienceBundle Metadata API allows you to retrieve, deploy, create, update, or delete an Experience Cloud site's metadata definition in a single API call. To use this API, you need to enable the "Enable ExperienceBundle Metadata API" setting in the Experience Cloud site's administration settings.

Three valid topic types are Featured Topic, Trending Topic, andStandard Topic. Topics are keywords or phrases that help users find and organize content in Experience Cloud sites. A Featured Topic is a topic that is manually selected by an administrator or moderator to be displayed prominently on the site. A Trending Topic is a topic that is automatically generated by an algorithm based on the popularity and recency of the content.
A Standard Topic is a topic that is created by users or administrators and can be assigned to any content.