Development-Lifecycle-and-Deployment-Architect Sample Questions Answers

Program team and executive sponsors are two user groups that an architect should recommend to join the COE. A program team is a group of people who are responsible for managing and delivering the Salesforce projects and initiatives. They can provide the COE with the technical expertise, best practices, and project management skills. An executive sponsor is a senior leader who supports and advocates for the Salesforce program. They can provide the COE with the strategic direction, business alignment, and funding support.

The best solution to address the problem of user testing taking a long time due to data setup is to include automated sample data during deployment. This way, the users can have realistic and consistent data to test the functionality and performance of the system. Assigning more users to create test data, testing data creation being outside the scope of continuous integration, or training business users to create test data more efficiently are not effective solutions, as they still require manual effort and may result in inconsistent or inaccurate data.

The best strategy to delete the day’s test data in a partial copy sandbox every night is to execute a batch job that deletes all records created on the day. This way, you can automate the process of cleaning up the test data and avoid manual work. Manually deleting all records individually is time-consuming and error-prone. Creating a new developer copy sandbox every night is unnecessary and wasteful, as developer copy sandboxes have limited storage and functionality. Refreshing the sandbox every night is also not feasible, as partial copy sandboxes have a refresh interval of 5 days.

The creation and execution of Release Management processes are the responsibility of the Dev/Build Team and the Center of Excellence. The Dev/Build Team is in charge of developing, testing, and deploying the changes to the system, while the Center of Excellence is in charge of defining and managing the best practices, standards, and governance for the system. The Steering Committee is a group of senior stakeholders that provides strategic direction and oversight for the project, but does not create or execute the Release Management processes. The End Users are the people who use the system, but do not create or execute the Release Management processes.

Using continuous integration with automation testing is a development practice that will help to reduce the amount of bugs, as it allows the code to be built and tested frequently and automatically. Encouraging the development team to do peer code review is a development practice that will help to reduce the amount of bugs, as it allows the code to be checked and improved by other developers. Incorporating test-driven development into the project structure is a development practice that will help to reduce the amount of bugs, as it requires the developers to write tests before writing code and ensure that the code meets the test criteria. Enabling the development team to be self-organizing is not a development practice that will help to reduce the amount of bugs, as it does not directly affect the quality of the code. Enabling a short and timely feedback loop with customers is not a development practice that will help to reduce the amount of bugs, as it does not directly affect the quality of the code.

A product owner is responsible for defining the scope and prioritizing the backlog of the project. A product owner can help the COE manage the scope creep between the different projects by aligning the business goals and ensuring the value delivery. A scrum master, a release manager, and a change manager are not directly involved in scope management.

The most important factor to consider before recommending Performance testing is the number of concurrent transactions, as this will affect the response time and throughput of the system. Option A is not relevant, as unit tests are used to verify the functionality and quality of the code, not the performance. Option B is not related, as Apex Hammer failures are used to check the compatibility of the code with new platform releases, not the performance. Option C is not helpful, as debug log entries are used to troubleshoot errors and issues, not the performance.

Building an Apex framework to deploy CPQ records and using an open source SFDX plugin and version control are two best practice recommendations an architect should propose to allow UC to deploy CPQ features as part of their CI/CD process. Building an Apex framework to deploy CPQ records is a good practice, as it allows the architect to automate the deployment of the configuration SObjects that drive the business logic of CPQ, and to avoid manual steps or errors. Using an open source SFDX plugin and version control is another good practice, as it allows the architect to leverage the benefits of the Salesforce DX development model, such as source-driven development, modular packaging, and team collaboration. Using a third-party product or data loader to deploy CSV files are not best practices, as they can introduce additional costs, dependencies, or risks to the deployment process.

Multiple triggers on the same object can cause conflicts and performance issues. Multiple unit test failures can indicate poor code quality and lack of maintenance. Duplicated logic across Visualforce pages and Apex classes can lead to inconsistency and redundancy.

 Refreshing a Partial Copy sandbox every weekend and including an appropriate sandbox template will allow UC to train the users on samples of production data and delete all the data generated during the training session at the end of the week. Loading data using data loader is not necessary if the sandbox template includes the relevant data. Developer Pro sandboxes have limited storage and may not be able to accommodate the data needed for the training.

The best way to stop the rollbacks from happening is to ensure report metadata is exported daily and that it is merged into the developer branches before the next release. This way, the reports and dashboards will be up to date and consistent across all environments. Using a third-party data warehouse is not a solution, as it does not address the root cause of the rollbacks. Removing the executive’s ability to change reports is not a good practice, as it limits their flexibility and autonomy. Backing up and reimporting the reports before and after the release is not a reliable or scalable solution, as it can introduce errors and inconsistencies.

Kanban can help clarify whether value is being delivered to the business by using metrics, like lead time and throughput, which increase transparency. Lead time measures how long it takes to complete a work item from the time it is requested, and throughput measures how many work items are completed in a given time period. These metrics can help the business stakeholders see the progress and performance of the development teams, and align their expectations with the reality. Kanban does not respond to unplanned work and changes by dropping everything and jumping on the new request, as this would disrupt the flow and quality of work. Kanban does not make use of the Salesforce Agile Accelerator, as this is a tool for managing agile projects. Kanban does limit work in progress, but this is not the main reason why it can help clarify whether value is being delivered to the business.

 The following issues could be affecting their deployment times:

• The number and complexity of Apex tests will have a large impact on the deployment time, as the tests will take longer to run and consume more resources.
• Some components such as profiles, custom junction objects, and fields take longer to process than others, as they have more dependencies and validations to check.
• Users are working in the org during deployment can affect users and the deployment, as they can lock records or metadata components that are being deployed, causing errors or delays.

The evidence that can support the CTO’s claims is a burndown chart showing the team misses their forecast sprint after sprint. This indicates that the team is overcommitting and not able to deliver the work they planned. The definition of done, the Kanban board, and the burndown chart showing the team finishes early are not relevant to the CTO’s claims, as they do not reflect the actual progress and performance of the team.

Refreshing a sandbox during the release preview window to ensure they have the upcoming release is a step that the team at UC should take to prepare for the new Salesforce release, as it allows them to test their application in an environment that matches the production environment after the upgrade. Running regression tests in an upgraded sandbox to detect any issues with the upgrade is also a step that the team at UC should take to prepare for the new Salesforce release, as it helps them to verify that the existing functionality is not affected by the new features or changes introduced by the upgrade. Reviewing the release notes for automatically-enabled features and technical debt is also a step that the team at UC should take to prepare for the new Salesforce release, as it helps them to understand the impact and benefits of the new features or changes, as well as to identify and resolve any technical debt that may cause issues or conflicts with the upgrade. Contacting Salesforce to schedule a time to upgrade the full sandbox is not a step that the team at UC should take to prepare for the new Salesforce release, as it is not possible to request a specific time for the upgrade of the full sandbox, which is determined by Salesforce and depends on the release window and the pod assignment. Upgrading any SOAP integrations to the newest WSDL as early as possible is not a step that the team at UC should take to prepare for the new Salesforce release, as it is not necessary to upgrade the SOAP integrations to the newest WSDL, unless they want to use the new features or fields introduced by the upgrade. The SOAP integrations will continue to work with the previous WSDL versions, as they are backward compatible.

Three areas that should be tested as part of data migration are: data transformation against source system, contact association with correct account, and account and lead ownership. These areas can help ensure that the data is migrated correctly and accurately, and that the relationships and ownership are preserved. Lead assignment is not an area that should be tested as part of data migration, as it is a business process that is triggered after the data is migrated. Page layout assignments is also not an area that should be tested as part of data migration, as it is a configuration setting that is independent of the data. See Data Migration for more details.

Presenting the feature requests at a Center of Excellence meeting and creating the backlog or priority list in a project management tool are two options that can help to get feedback and prioritize the requests. A Center of Excellence meeting can provide a forum for discussing the business value, feasibility, and impact of the requests with the stakeholders. A project management tool can help to track, organize, and prioritize the requests based on the agreed criteria.

 The best release strategy for creating a new report to support an urgent client request is to utilize the daily release process. The daily release process is designed for small and quick changes that do not require extensive testing or approval. The daily release process can create the report directly in a full sandbox and then deploy it to production. The major and minor release processes are more suitable for large and complex changes that require more testing and approval. The major and minor release processes should not create the report directly in production, as this may cause errors or conflicts.

The best environment for developing a new feature in an org with unlocked packages is a scratch org with the package code that will be changed and its dependencies. A scratch org is a source-driven and disposable deployment of Salesforce code and metadata that is fully configurable and can be created quickly. A scratch org can also install unlocked packages and their dependencies, which can help ensure compatibility and functionality of the new feature. A Developer Pro sandbox is not a good option, as it is not source-driven and can have outdated or conflicting data and metadata.

The testing of the JavaScript part of the Aura component can be tested in the Jest framework and the Apex controllers can be tested using test classes. The testing can be viewed in the lightning.force.com/c/jasminetests.app URL. The page loads and runs Jasmine test and writes pass/fail information to the screen. The Lightning test service AppExchange package is not required for testing Aura components, but for testing Lightning web components. The $T test helper object is not a valid object for testing Lightning components.

Active Process Builders are configuration items that should be covered by executable tests, as they can have complex logic and actions that affect the behavior and performance of the application. Validation Rules, Workflow Rules, and Case Assignment Rules are also configuration items, but they are simpler and less likely to cause errors or conflicts. Therefore, they can be verified by manual testing or declarative tools.

Aura accessibility tests can be called in JSTEST and WebDriver Test environments. JSTEST is a JavaScript testing framework that runs on Node.js and can be used to test Aura components. WebDriver Test is a Selenium-based testing framework that can be used to test the user interface and accessibility of Aura components. ACCTEST and AuraDriver Test are not valid environments for calling Aura accessibility tests.

 DevPro1 cannot be cloned because it is on a different version from Production, as it was upgraded to preview for the next Salesforce major release two weeks ago. Therefore, the architect should recommend creating a new DevPro2, and migrating metadata from DevPro1. This way, the second work stream can work on the Service Cloud requirements in a separate sandbox, without affecting the Sales Cloud dev team. Asking the second work stream team to work on the same DevPro1 sandbox would create conflicts and dependencies between the two teams, and would not allow them to release at different times. Pushing back on the requirements because adding another work stream will bring some risks with it would not be a good option, as the business needs might be urgent and important.

 The sfdx force:source:retrieve command is used to retrieve the metadata from an org to a local project directory. However, before running this command, the developer needs to create a project using the sfdx force:project:create command, and then navigate to the project directory using the cd command. If the developer hasn’t done these steps, they will get the error message: “This command is required to run from within an SFDX project”. The -n option is not required for the sfdx force:project:create command, as it will prompt the developer to enter a project name interactively. The developer can create the project within VSCode and run the command in a separate terminal, as long as they are in the same project directory.

 Three advantages of using the SFDX are: can store code on a local machine, or a version control system; can create scratch orgs; and can install application metadata from a central repository. These advantages can help improve the development experience, as they allow developers to work with source-driven development, use ephemeral and configurable environments, and access metadata components from a shared location. Can quickly deploy metadata using Execute Anonymous is not an advantage of using the SFDX, as Execute Anonymous is a feature of the Developer Console that allows running Apex code, not deploying metadata. Can use native Deployment Rollback Tool to quickly revert to prior state is also not an advantage of using the SFDX, as there is no such tool in the SFDX. See [Salesforce DX] for more details.

Load testing is the type of testing that will help UC measure the page response time. Load testing simulates the expected number of concurrent users and measures how the system performs under normal load conditions. Unit testing, system integration testing, and stress testing are not designed to measure the page response time.

 The success criteria for data migration and the manual and automated data validation approaches are two key areas of UC’s data migration test plan that should be included. The success criteria define the expected outcomes and quality standards for the data migration process. The data validation approaches ensure that the data is accurate, complete, and consistent after the migration.

The benefits of managing change with Packaged Development are:

• Versioning to help with change management, as it allows the developers to track the changes made to the metadata and roll back to previous versions if needed.
• Making the release cycle more efficient and agile, as it enables the developers to deploy smaller and more frequent updates to the orgs, reducing the risk of errors and conflicts.
• Modular development process with specification of dependencies among packages, as it allows the developers to break down the metadata into logical units that can be reused and updated independently, while ensuring that the dependencies are resolved correctly. Managing the number of sandboxes needed to successfully deploy is not a benefit of Packaged Development, as it is more related to the sandbox strategy and the development model. Clearly dividing developers and testers is also not a benefit of Packaged Development, as it is more related to the team structure and the testing strategy.

According to the [Salesforce Performance Testing Guide], performance tests must be run in a sandbox, a business justification must be provided to Salesforce, and performance tests may be run without advanced notice, but Salesforce will not store performance logs. Salesforce does not need to be informed 7 days before starting performance tests, and Salesforce will not monitor test activity to ensure there are no issues with Salesforce Services.

The two sandbox types that would be appropriate to use as the hotfix environment are Developer sandbox and Developer Pro sandbox. These sandbox types are suitable for testing and deploying quick fixes, as they are easy to create and refresh, and have a minimal data and metadata footprint. A Partial Copy sandbox or a Full sandbox would be too large and complex for a hotfix environment, and would take longer to create and refresh.

 A is the correct answer, as generating a destructivechanges.xml file and deploying the package via the Force.com Migration Tool is the best way to manage the deletions of metadata components across sandbox environments and production with minimal impact on other work streams. A destructivechanges.xml file is a special file that specifies the components to be deleted from an org, and can be deployed using the Force.com Migration Tool, which is a command-line tool that uses the Metadata API to retrieve and deploy metadata components. This method can help to automate and streamline the deletion process, as well as ensure consistency and accuracy across the environments. B is incorrect, as performing deletes manually in a sandbox and then deploying a change set to production is not a good way to manage the deletions, as it can introduce errors and inconsistencies, as well as require additional steps and permissions. C is incorrect, as assigning business analysts to perform the deletes and splitting up the work between them is not a good way to manage the deletions, as it can create confusion and complexity, as well as lack of coordination and integration. D is incorrect, as deleting the components in production and then refreshing all sandboxes to receive the changes is not a good way to manage the deletions, as it can disrupt the production environment and the ongoing development and testing activities in the sandboxes. You can learn more about this topic in the Deploy Changes with the Force.com Migration Tool unit on Trailhead.

These are the correct answers because the project steering committee plays a role in approving deviations from the chosen methodology, when required to address project issues, and setting the criteria for selecting agile or waterfall methodology to be used on internal projects. The steering committee does not design a methodology, but rather chooses one from the existing ones. The steering committee does not enforce that corporate project stage gates are part of the chosen methodology but rather ensures that the chosen methodology aligns with the corporate project stage gates.

 The maximum size of deployed .zip file is 39MB for Metadata API. You can deploy up to 10,000 files, but retrieve more than 10,000 files using Metadata API.

A workflow and a trigger are considered minor changes that do not require alignment with a Salesforce major or patch release. However, they still need proper testing, training, and change management before being deployed to production. Therefore, the architect should plan this as a minor release with training and change management.

D is the correct answer, as automated testing is the best approach to mitigate the risk of bugs being inadvertently introduced to production. Automated testing can help to ensure that the code meets the quality and functionality standards, as well as detect and prevent any errors or regressions before deploying to production. A is incorrect, as user acceptance testing is not enough to mitigate the risk of bugs, as it depends on the manual testing and feedback of the end users, which can be subjective and incomplete. B is incorrect, as the use of an agile methodology is not directly related to mitigating the risk of bugs, as it is a way of managing the project scope, requirements, and delivery. C is incorrect, as requirements traceability is not directly related to mitigating the risk of bugs, as it is a way of tracking the requirements and their fulfillment. You can learn more about this topic in the Testing Strategies module on Trailhead.

Utilizing Heroku Connect to provide test class data is not a recommended method of creating test data in Salesforce, as it can introduce unnecessary complexity and dependency on an external system. Referencing data from middleware directly within your test class is also not a good practice, as it can make your test class unreliable and dependent on the availability of the middleware. Hosting a mock endpoint to produce sample information from an endpoint and loading a CSV as a static resource and referencing it in a test class are both valid methods of creating test data in Salesforce, as they allow you to isolate your test class from external factors and ensure consistent results. See Create Test Data for Apex Tests for more details.

These are the correct answers because they are essential components of a governance framework that helps to manage the changes and enhancements to the Salesforce application. Requirements management is the process of capturing, analyzing, prioritizing, and tracking the business needs and requests. Change control log is the tool that records and tracks the status of all change requests and approvals. Documentation repository is the central place that stores and organizes all the project artifacts and deliverables. Automated testing and continuous integration are not necessary components of a governance framework, but rather best practices for ensuring the quality and reliability of the code and configuration.

 In the post refresh plan, modifying external ids to a known valid set of values for UAT is the best way to resolve the issue of objects that have external ids from production no longer pointing to valid external ids in the UAT environment. This way, the data integrity and consistency across the integrated systems can be maintained. Letting UAT point to production integrations and rolling back each transaction after it finishes is not a good practice, as it can cause data loss or corruption in production. Deleting all the data and using an automated testing tool to create new data across all the systems in UAT is not feasible, as it can take a lot of time and resources. Masking the external id so nobody can see the production value is not a solution, as it does not address the underlying problem of invalid references.

 D is the correct answer, as the Agile methodology is the best way to handle a project with a fixed deadline and a changing scope, such as retiring a business-critical application that will no longer be supported. The Agile methodology allows for frequent feedback, iterative development, and adaptive planning, which can help to deliver a working solution on time and within budget. A is incorrect, as executive leadership is not a methodology, but a role that can support the project. B is incorrect, as a requirements traceability matrix is a tool that can help to track the requirements and their fulfillment, but not a methodology. C is incorrect, as a business continuity plan is a document that outlines how to resume business operations in the event of a disruption, but not a methodology. You can learn more about the Agile methodology in the Agile Basics module on Trailhead.

 The two actions that can effectively contribute to the quality and agility of the team are: Define and follow code standards, and use static code analysis tool in the pipeline before manual code review. Code standards can help ensure consistency, readability, and maintainability of the code, as well as reduce errors and bugs. A static code analysis tool can help automate the code review process and identify any issues or violations of the code standards before the manual review. Choosing the most senior developer to help the technical lead or skipping the code review are not effective actions, as they can lead to more errors and delays.

The best practice is to always fix the bug in the developer environment where the project work was done, and follow the normal deployment and testing process. This ensures that the code is consistent, traceable, and validated across all environments. Fixing the bug in UAT is not ideal, as it can introduce new issues, create conflicts with other changes, and bypass the version control system. Spinning up a new sandbox for a hot fix is not necessary, as it can add complexity and overhead to the deployment process. Treating the issue as a change request and putting it in the backlog is not advisable, as it can delay the resolution and affect the user experience.

When migrating a flow with change sets, the following statements should be considered: When a change set with a multiple versioned flow is uploaded, it includes only the active version of the flow. When a change set with a multiple versioned flow is uploaded, and no active version is available, it includes the most recent inactive version of the flow. These statements are based on the Salesforce documentation on how change sets handle flows with multiple versions. The other statements are incorrect, as they do not reflect the actual behavior of change sets.

The best practice for writing test classes is to not use SeeAllData and generate data in the test methods. This ensures that the test classes are independent of the data in the org and can run successfully in any environment. Creating test data in production or setting SeeAllData to True can cause unexpected failures or data conflicts.

 A and C are the correct answers, as they are the project situations that favor an agile methodology. An agile methodology is a flexible and iterative approach that can accommodate changing requirements, deliver value quickly, and enable frequent feedback and collaboration. A is correct, as a digitization project to update an existing customer-facing process and enable quick adjustments is a situation that requires an agile methodology, as it involves transforming a legacy system, adapting to customer needs, and delivering incremental improvements. C is correct, as an environment with a heavy investment in DevOps capabilities for rapid testing and deployment is a situation that requires an agile methodology, as it enables continuous integration and delivery, as well as quality assurance and automation. B is incorrect, as a project to be executed by a third party, with a fixed and formal scope, budget, and timeline is a situation that favors a waterfall methodology, as it involves clear and stable requirements, contractual obligations, and sequential phases. D is incorrect, as a project with well-defined requirements and complex interactions between front- and back-end systems is a situation that favors a waterfall methodology, as it involves detailed planning, design, and testing, as well as minimal changes and dependencies. You can learn more about this topic in the Agile Basics module on Trailhead.

Two advantages of automated test data loads over manual data loads are that automated loads can be done with no human oversight and that automated loads are reliable in their results. Automated loads can be scheduled and executed without human intervention, which saves time and effort. Automated loads can also ensure that the data is consistent and accurate, which reduces errors and risks. Automated loads do not necessarily increase costs, as they can also save money in the long run by improving efficiency and quality. Automated loads can also be scripted by CICD tools, which is one of the benefits of using them.

The reason why the Apex classes are not able to access the metadata of the target org during testing is that UC needs to get the managed package certified by the Salesforce security review. This is because Apex code in a managed package can only access the metadata of the target org if the package has passed the security review and has been granted the Modify Metadata permission. See Apex Metadata API for more details.

The best options to enforce code quality in UC’s continuous integration process are to introduce manual code review before deployment to the testing sandbox and to introduce static code analysis before deployment to the testing sandbox. Manual code review can help identify and fix any errors, bugs, or best practices violations in the code. Static code analysis can help check the code quality, complexity, and security using automated tools and standards. Introducing manual code review before deployment to the production org may be too late, as the code may have already caused defects or issues in the testing sandbox. Increasing the size of the testing team assigned to the project may not improve the code quality, as the testing team may not have the skills or authority to review or modify the code. Testing data creation is outside the scope of code quality.

 A single org strategy has the benefits of increased ability to collaborate, centralized data location, and consistent processes across the business. These factors can improve efficiency, data quality, and user adoption. A single org strategy may not allow for tailored implementation or fewer inter-dependencies, as different business units may have different requirements and dependencies.

 Implementing a pull request and secure code review will contribute to an improvement of code security by ensuring that the code is checked and approved by another developer before merging to the main branch. Integrating a static code security analysis tool in the CI/CD process will contribute to an improvement of code security by automatically scanning the code for vulnerabilities and enforcing security standards. Hiring a company specialized in secure code review or using two developers to review and fix current code vulnerabilities are not actions that will improve code security, but rather remediate existing security issues.

 Creating a governance process requiring all projects to create project deliverable documentation is an option that an Architect should recommend, as it helps to ensure that the code and configuration are well documented and maintained, and that the administrators can understand the rationale and impact of the changes. Creating a standard method for deprecating classes and fields using design standards is also an option that an Architect should recommend, as it helps to avoid cluttering the org with unused or obsolete metadata, and to improve the performance and security of the application. Creating an adoption plan for end users using Salesforce dashboards and reports is not an option that an Architect should recommend, as it does not address the issue of how objects and fields are being used and how future implementations can be maintained. Creating a design standard requiring integration to use declarative configuration patterns is not an option that an Architect should recommend, as it does not address the issue of how objects and fields are being used and how future implementations can be maintained. Creating a governance framework focused on high-level business strategy and goals is not an option that an Architect should recommend, as it does not address the issue of how objects and fields are being used and how future implementations can be maintained.

Utilizing a dedicated developer pro sandbox to address critical bugs and release to production is the recommended release management strategy, as it allows the development team to work on the new project without being interrupted by the bug fixes, and also ensures that the bug fixes are deployed to production as soon as possible. Including fixes for critical bugs in the ongoing development sandboxes is not recommended, as it may delay the release of the bug fixes and also introduce conflicts with the new code. Keeping teams separate until the end of the project and creating a full copy sandbox to merge their work then is not recommended, as it may create a lot of merge conflicts and integration issues. Addressing critical bugs in the development sandboxes and pushing those changes to production separately is not recommended, as it may create inconsistencies between the development and production environments.

A Center of Excellence is a mechanism that can help to increase the use of standard Salesforce functionality, by defining and managing best practices, standards, and governance across the organization. A Center of Excellence can also facilitate cross-functional collaboration, knowledge sharing, and alignment of Salesforce initiatives with business goals. A Change Control Board is a group of stakeholders that reviews and approves changes to the system, but does not necessarily promote the use of standard Salesforce functionality. A Requirements Traceability Matrix is a document that links requirements to their sources and test cases, but does not necessarily increase the use of standard Salesforce functionality. A Project Management Office is a group that oversees the execution of projects, but does not necessarily increase the use of standard Salesforce functionality.

Manually validating change sets before deployment is a recommended practice to avoid possible delays while deploying a change set, as it can help you identify and resolve any errors or dependencies before the actual deployment. Change set performance is not independent of included components, as some components may take longer to deploy than others. Manually creating new custom objects and new custom fields or manually applying the field type changes are not advisable, as they can introduce human errors and inconsistencies between environments. See Deploy Changes with Change Sets for more details.

The fastest approach to spin off a sandbox with up to 10,000 records in each object for testing the integration performance is to spin off a partial copy sandbox using a sandbox template with all the objects required for testing the integration. A partial copy sandbox can copy up to 10,000 records per object using a sandbox template that specifies the objects and fields to copy. A partial copy sandbox can also copy the metadata and the configuration settings from the production org. A developer pro sandbox, a development sandbox, or a full copy sandbox may not be able to copy enough data for testing the integration performance, as they have lower data storage limits. A developer pro sandbox and a development sandbox can only copy 1 GB of data, while a full copy sandbox can only copy 5 GB of data. A full copy sandbox may also take longer to spin-off, as it copies all the data and metadata from the production org.

The optimal way to store the service centers as technical reference data is to add them to a custom metadata type. Custom metadata types allow you to create, update, and deploy records that are defined by a custom object. Custom metadata types are similar to list custom settings, but they have some advantages, such as being deployable, queryable, and packageable. Hierarchical custom settings are not suitable for storing multiple records of the same type, and defining a new custom object with a picklist field is unnecessary and inefficient.

 This is the correct answer because it is a risk to have a fixed release date and budget, but unknown and changing requirements. This may lead to unrealistic expectations, scope creep, and poor quality of the application. The requirements should be solicited by an external community if they are the end users or stakeholders of the application. The project can use either the waterfall or agile methodology, depending on the nature and complexity of the project, but the methodology should be aligned with the requirements and the release date.

The architect should suggest the following actions to help UC discover the failing unit tests earlier: Train the administrators to make their changes in a special “admin changes” sandbox, and then promote to production, and ensure a metadata backup is committed to version control every day and a diff published to the release team. Training the administrators to use a sandbox can help prevent direct changes to production that can break the code or the unit tests. Ensuring a metadata backup and a diff can help identify any changes that have been made to production and compare them with the source of truth.

These are the correct answers because they are related to the data quality and integrity of the migrated data. Case association, case ownership, and data transformation are all important aspects of data migration that should be tested. Case assignment rules and escalation rules are not directly related to data migration, but rather to the business logic and workflow of the application. Page layout assignment is also not related to data migration, but rather to the user interface and security of the application.

 Using a Developer Edition org to stage changes to their Customer Community poses the following risks:

• Developer Edition orgs have limited user counts and low data volume limits, which will make User Testing difficult, as the testing environment will not be representative of the production environment.
• Developer Edition orgs cannot have sandboxes, which will make team development difficult, as the developers will not be able to work in isolated environments and test their changes before merging them.
• Changes Sets cannot be used to deploy from Developer Edition to Production, which will make deployment more complex, as the developers will have to use other tools such as Ant Migration Tool or SFDX CLI to deploy their changes.