Given a Scenario, Analyze and Explain the Use Cases and Considerations When Using Managed vs. Unmanaged Packages. DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   A development team wants to share a set of custom fields and a workflow rule with another internal team, who will then modify them to fit their own processes. There is no plan for future updates. Which package type is most appropriate?

   • AManaged package, because it allows upgrades if needed later.
   • BManaged package, because it provides a namespace.
   • CUnmanaged package, but only if the components are not modified.
   • DUnmanaged package, because it allows the receiving team to modify the components and there is no need for upgrades.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   What is a key difference between a managed package and an unmanaged package in Salesforce?

   • AUnmanaged packages require a namespace prefix, while managed packages do not.
   • BManaged packages cannot be installed in sandboxes, while unmanaged packages can.
   • CManaged packages support upgrades and protect components, while unmanaged packages do not support upgrades and allow direct modification.
   • DManaged packages are free, while unmanaged packages require a fee.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A Salesforce developer created a custom Lightning Web Component (LWC) and wants to share it with a colleague in another org. The colleague will need to edit the component's JavaScript and HTML files to integrate it with their own design system. The developer will not provide any updates. What is the most appropriate way to share the component?

   • AEmail the LWC's JavaScript and HTML files to the colleague.
   • BCreate a managed package and provide it to the colleague.
   • CCreate a managed package, but unlock the LWC for the colleague.
   • DCreate an unmanaged package and provide the installation link to the colleague.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   What is a key limitation of an unmanaged package?

   • AIt requires a namespace prefix.
   • BIt protects components from modification by subscribers.
   • CIt cannot be installed in a production org.
   • DIt does not support versioned upgrades from the publisher.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A vendor is deciding between a managed and an unmanaged package for a new product. The product will be sold on the AppExchange, and the vendor plans to release major upgrades twice a year. The vendor also wants to allow subscribers to customize the product's page layouts and add their own fields to its custom objects. What is the most appropriate package type and configuration?

   • AManaged package with all components locked to protect the product.
   • BManaged package with the custom objects and page layouts left unlocked.
   • CManaged package, but only if the vendor also provides the source code to subscribers.
   • DUnmanaged package, because it allows subscribers to customize page layouts and add fields.
   Reveal Solution Discussion Select an answer first