Explanation:

The Topic Catalog is a pre-built page in Experience Cloud that displays all the topics and their hierarchies in a single, organized view. Setting it up is a two-step process involving content creation and navigation.

Why D is Correct:
This accurately describes the two required steps:
Content Prerequisite:
You must first have at least one topic created in the Topics manager.
Navigation Action:
The Topic Catalog is accessed by adding the specific "More Topics" link from the navigation menu's component palette. This action creates a link to the built-in Topic Catalog page, which automatically displays all your topics.

Why the Other Options are Incorrect:

Why A is Incorrect:
This is incorrect because it specifies creating a subtopic as a prerequisite. While subtopics are great for organization, the absolute minimum requirement is a single parent topic. The "More Topic ink link" also uses incorrect terminology; the correct component is the "More Topics" link.
Why B is Incorrect:
This is partially correct in that you need topics, but it incorrectly states you must create a subtopic. A topic catalog can be created and will function with just parent-level topics. It also misses the crucial second step of adding the "More Topics" link to the navigation.
Why C is Incorrect:
"Topic Hierarchy" is not a specific setting that needs to be enabled. The hierarchy is an inherent property of how topics and subtopics relate. The requirement for "two subtopics" is also arbitrary and not a system requirement.

Reference:
Salesforce Help: Set Up a Topic Catalog - This article states: "To set up a topic catalog, create topics for your experience and add the More Topics link to your navigation menu."

Explanation

The issue described—where users are successfully created but receive no login credentials (welcome email)—is most commonly caused by a simple configuration setting within the Experience Cloud site's administration area being disabled.

B. The welcome emails were not enabled for the site. (Correct)
In an Experience Cloud site's Administration Workspace under the Emails section, there is a setting, typically called "Send welcome email" or a similar name, which is a checkbox that must be enabled.
If the site is active and users are added as members (by profile or permission set), the system will automatically send the login credentials (a welcome email with a "Set Password" link) only if this setting is checked. If it is not checked, the users are created, but the email is never triggered.

Detail of Incorrect Answers

A. The sender's email address was changed while it was pending verification and C. The sender's email address was changed and not verified.
If the sender's Organization-Wide Email Address was unverified, the emails would typically be blocked and appear in the email logs as failed to send, or be sent from a fallback Salesforce address. However, the system would still attempt to send the welcome email. The symptom here is that none of the users received the email, which points to the email not being triggered in the first place, not an issue with deliverability or sender verification.
D. The roles were not enabled for the users.
Roles are part of the security model and sharing settings for external users, but they do not prevent the initial creation of the user record or the triggering of the welcome email. A user can be successfully enabled without a defined role, but they still need a password to log in, which is provided by the welcome email.

Reference:
The requirement to manually enable the welcome email is a standard configuration step for Salesforce Experience Cloud sites.
Salesforce Help Documentation on managing emails and notifications for Experience Cloud Sites. The specific setting is typically found in Experience Workspaces $\rightarrow$ Administration $\rightarrow$ Emails $\rightarrow$ Welcome Email.

Explanation:

Universal Containers needs to organize content on their site so users can find and browse information easily. Salesforce offers three main topic types in Experience Cloud. Featured Topic lets admins highlight key topics on the homepage or navigation to drive attention to important content. Content Topic tags individual articles, posts, or files so they show up in search and topic pages. Navigational Topic builds a structured menu system so users can drill down into categories like “FAQs” or “Product Guides.” These three work together to make content discoverable and organized.

Why Option A Is Correct
Featured Topic is a real topic type. The admin marks a topic as featured in the site settings. It then appears in special components like the Featured Topics carousel or homepage banner to promote high-value content.

Why Option B Is Correct
Content Topic is the standard way to tag CMS content, Knowledge articles, or Chatter posts. Users see all items under a topic in one place. It powers search filters and topic detail pages.

Why Option D Is Correct
Navigational Topic creates a hierarchy in the site navigation menu. The admin builds parent and child topics so users can browse logically instead of searching everything.

Why Option C Is Incorrect
Trending Topic is not a topic type. Salesforce shows trending topics automatically based on views and engagement. You cannot create or assign it manually.

Why Option E Is Incorrect
Standard Topic is not an official type. All topics are either navigational, featured, or content-based. “Standard” is just a generic term.

References:
Salesforce Help – Topic Types in Experience Cloud
Trailhead – Organize Content with Topics

Explanation:

Universal Containers (UC) is building a do-it-yourself site for customers and prospects, featuring articles, manuals, FAQs, and community Q&A. To support this public, content-rich experience, UC should focus on:

🟩 C. Guest user and public access settings
These settings control what unauthenticated users (guests) can see and do on the site.
UC must configure object-level and record-level access via sharing rules, public visibility, and guest user profile permissions.
This ensures that FAQs, articles, and community questions are accessible without login.
🟩 D. Content Delivery Network (CDN)
A CDN improves site performance by caching static content (e.g., images, manuals, articles) across global edge servers.
It reduces latency and ensures fast load times for public users accessing the site from different regions.
Salesforce Experience Cloud supports CDN integration for public sites.

❌ Why the Other Options Are Incorrect

A. Public Site Connect
This is not a valid Salesforce feature. Likely a distractor or fictional name.
B. Document Library Model (DLM)
Not a standard Experience Cloud feature. Salesforce uses CMS, Files, and Knowledge for document and content management — not DLM.

Reference:
Salesforce Help – Guest User Access

Explanation:

B. Customer Community Plus
The Customer Community Plus license typically supports 20 custom objects per user. This is double the limit of the standard Customer Community license, making it a viable option for UC's requirement of "more than 10" custom objects. This license is generally for customers who need more advanced features, including the ability to use the full Salesforce sharing model (Roles and Sharing Rules).

D. External Apps
The External Apps license (often seen as a high-power, highly custom external user license) is designed for building comprehensive digital experiences that might be fully custom or serve as a dedicated portal for a large number of custom objects. The External Apps license can support up to 200 custom objects per user, far exceeding the 10-object limit and making it a strong fit for a complex, custom solution like the one described.

Incorrect Answers

A. Channel Account
This license is specifically for Partner (resellers, distributors, etc.) users, not Customer users, as required by the prompt. While a Partner license supports more custom objects than a standard Customer Community license (typically 10), it is intended for a different relationship type (B2B/channel management).

C. Commerce Portal
The term "Commerce Portal" is often a feature or a templated site type rather than a distinct core license SKU that meets the custom object count requirement. The license used to power a Commerce Portal is usually a variation of the Customer or Partner licenses, and the specific requirement is the ability to support the large number of custom objects. For high custom object needs, the Customer Community Plus or External Apps licenses are the dedicated choices for external users.