Universal Containers (UC) has a customized repository that represents lots of different
apps or projects. UC currently is trying to shift from the org development model to the package
development model to manage changes. In the org development model, each developer starts
their work within their own personal sandbox.
When it comes to choosing development environments, what should a Salesforce architect
recommend?
Which two ways should a developer working on a data loading integration that operates
between different Salesforce environments insert multiple related records in one call or
transaction?
Choose 2 answers
Universal Containers are concerned that after each release, reports and dashboards
seem to roll back to previous versions. Executives spend many hours crafting these dashboards to perfectly meet their needs, and are now questioning the Salesforce platform's ability to save things, even data records.
What can the Salesforce architect advise to stop the rollbacks from happening?
Universal Containers is having trouble deploying metadata from SIT to UAT. UAT is
complaining that it does not recognize some new Salesforce metadata types to be deployed. The deployment from Dev to SIT worked perfectly
What could be the problem?
Universal Containers (UC) has been using Salesforce Sales Cloud for many years
following a highly customized, single-org strategy with great success so far.
What two reasons can justify a change to a multi-org strategy?
Choose 2 answers
Currently there are no comments in this discussion, be the first to comment!