What happens if a language is deleted from Experience Builder?
Answer(s): D
According to the Localization page, localization is a feature that allows you to create and manage content in different languages for your B2B Commerce site. Localization can be used to support multilingual users and customers on your site. To add or delete languages for your site, you need to use Experience Builder in CC Admin. Experience Builder is a tool that allows you to create and edit web pages for your B2B Commerce site using drag-and-drop components and settings.What happens if a language is deleted from Experience Builder is that the content is no longer visible but is not deleted. Deleting a language from Experience Builder removes it from the list of available languages for your site and hides the content that was created or translated in that language. However, the content is not permanently deleted from your org and can be restored if you add the language back to Experience Builder. Therefore, option D is correct. Options A, B, and C are false because they imply that the content is permanently deleted from your org when you delete a language from Experience Builder, which is not true.
Localization, Localization Overview
Northern Trail Outfitters(NTO's) is ready to move their store from Sandbox to Production.Which two components does the admin need to consider as part of the change sets?
Answer(s): B,C
According to the Deploy Your Storefront page, deploying your storefront is a process that allows you to move your B2B Commerce site from one Salesforce org to another, such as from sandbox to production. Deploying your storefront can help you test, validate, and launch your site in different environments. To deploy your storefront, you need to use change sets in Salesforce Setup. Change sets are tools that allow you to migrate metadata components from one org to another using inbound and outbound connections. Two of the components that an admin needs to consider as part of the change sets are Site.com (from Experience Builder) and custom objects and fields. Site.com(from Experience Builder) component allows you to migrate the web pages that you created or edited for your B2B Commerce site using Experience Builder in CC Admin. Custom objects and fields component allows you to migrate the custom data structures that you created or modified for your B2B Commerce site, such as product categories, catalogs, price lists, etc. Therefore, options B and C are correct. Options A, D, and E are false because they are not components that an admin needs to consider as part of the change sets for deploying your storefront. Process builder flows, triggers, and platform events are features that can be used to automate business processes or actions for your B2B Commerce site, but they are not required or specific for deploying your storefront.
Deploy Your Storefront, Deploy Your Storefront Overview
Which three features are needed in a scratch org definition file to deploy and enable B2B Commerce?
Answer(s): B,C,D
Which two features are needed in a scratch org definition file to deploy and enable B2B Commerce?
Answer(s): A,D
According to the Scratch Orgs page, scratch orgs are temporary Salesforce environments that you can use for development, testing, or training purposes. Scratch orgs can help you create and test new features or configurations for your B2B Commerce site without affecting your production org. To create a scratch org, you need to use a scratch org definition file in Salesforce CLI or Visual Studio Code. A scratch org definition file is a JSON file that specifies the features and settings that you want to enable or disable for your scratch org. Two of the features that are needed in a scratch org definition file to deploy and enable B2B Commerce are Communities and B2B Commerce. Communities feature allows you to create and manage communities for your B2B Commerce site in your scratch org. B2B Commerce feature allows you to install and use the B2B Commerce managed package in your scratch org. Therefore, options A and D are correct. Options B, C, and E are false because they are not features that are needed in a scratch org definition file to deploy and enable B2B Commerce. Advanced reports, scratch orgs are not supported, and order management are features that can be used to enhance or extend your B2B Commerce site functionality, but they are not required or specific for deploying and enabling B2B Commerce.
Scratch Orgs, Scratch Orgs Overview
What mechanism can the administrator use to migrate store settings from one store to another?
Answer(s): B
Post your Comments and Discuss Salesforce B2B-COMMERCE-ADMINISTRATOR exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the B2B-COMMERCE-ADMINISTRATOR content, but please register or login to continue.