In my earlier posts, I have written about solution types, solution deployment etc . When we talk about solutions , we might need to go the real practical aspects of it when we start using it or suddenly face some issues about solutions or solution deployment

Suppose you are designing a managed solution that will be deployed to another part of the business. Users may want to customize specific parts of the solution after the solution is installed. Which capability represents a managed property that users can configure. Below are the only properties which can set for the entity

and when we look at OOB entities, nothing can be changed

Hence it does not have the ability to change the display name of a system entity, or reassign a system dashboard or to rename a web resource, but can have the ability to add forms to a custom entity

You create a Publisher and add entities to a solution.
What are two outcomes of this action?
then there would not be any change to the name for existing custom entities that you add to a solution, however option sets that you create as part of the solution use the prefix that indicates the publisher and the name for custom entities that you create as part of the solution use the prefix that indicates the publisher

When we try to delete an entity we can delete the entity only when the entity is part of an unmanaged solution and another unmanaged entity has a lookup field to the entity on one form, or the entity is part of a managed solution and no other items are dependent upon the entity., or the entity is system-defined and no other items are dependent upon the entity. In short the custom entity can be deleted if its part of un managed solution and does not have any dependency on it like the entity is custom and uses a system-defined global option set. Here the option set has dependency on the entity but entity does not have dependency on the option set

Again you plan to delete a custom entity from an unmanaged solution. there is not no need to you must delete the solution that contains the entity or you can only delete the entity from managed solutions or you must delete all records related to the entity from the database. You must remove any dependencies with other objects.

Below are exclusive two statements are for managed solutions and not unmanaged solutions. You cannot export the solution and When you remove the solution, all components items included in the solution are removed.

You export five modified system security roles from a development environment as an unmanaged solution. You solution into a production environment. then the system security roles in production will be overwritten with the settings imported from the solution.

You install a unmanaged solution named SolutionA that has a dependency on another unmanaged solution named SolutionB. In this case I do not think SolutionB and all components that are not dependencies of SolutionA are removed as well as the system prevents you from deleting Solution B and SolutionB and all related components are removed. But the container for SolutionB is removed, but all its components remain.

You can not add following objects to solution – Goals, Queues, Subjects, Duplicate detection rules, system settings

You are a system administrator for an organization that relies solely on an ISV solution for Microsoft Dynamics 365. Your instances are scheduled to be updated. I think two approaches for this would be test the update in your sandbox environments prior to updating production and contact your ISV provider, and follow their recommendation for this update

You have a sandbox instance being used for development purposes at your organization. The URL for this instance https://contosoSBXDEV.crm.dynamics.com. The instance will now be used to test third-party ISV Solutions. You need to ensure that the instance URL will be https://contosoISVtesting.crm.dynamics.com.. Then  you need to edit the URL on the instance properties.