Often, one permit is dependent on another, and businesses require a specific set of permits to do business. The City of Snaxboro would like to show its constituents all the permits required for different business types, so they know exactly what they need to apply for. What is the recommended approach for building out this functionality?

A. Create an OmniScript with all the applicable Business Types. Based on the Business Type selected, enable a conditional section to display all the associated permits that are required. Embed this OmniScript on the Experience Site for applicants to use by selecting the Business Type and viewing the associated permits.

B. Create a new Business Regulatory Authorization Type Dependency record by selecting the Parent Business Regulatory Authorization Type that must be applied first and the Dependent Business Regulatory Authorization Type that must be applied after getting the parent. Ensure the Show Dependent Permits section is available in the portal for applicants to view.

C. Create a custom object called "Permit Dependency" and make it a junction object between the Business Type object and Regulatory (§> Authorization Type object. Create a FlexCard that allows the use to select the Business Type from a picklist and display the associated Permit Dependency records. Embed this FlexCard on an Experience site for applicants to use.

D. Create a custom object called Permit Dependency and make it a junction object between the Business Type object and Regulatory Authorization Type object. Configure the Permit Dependency records and embed a list view of the Business Types on the Experience Site for applicants to click and review related dependencies.