Q:

Your company has multiple environments for development, testing, and production.

You need to implement an Application Lifecycle Management (ALM) strategy that allows for controlled promotion of changes across these environments with minimal downtime.

What should you do? Each correct answer presents a complete solution. Choose two.

Wrong: Rely solely on the built-in version control of the development environment for tracking changes.

Wrong: Manually copy customizations from one environment to another using file transfer.

Wrong: Use the Environment Monitoring Tool within LCS to monitor the performance and usage of each environment.

The correct actions to implement an Application Lifecycle Management (ALM) strategy are to create deployment packages in LCS to group and deploy customizations across environments, use the Environment Monitoring Tool within LCS to monitor the performance and usage of each environment, and utilize Microsoft Dynamics Lifecycle Services (LCS) to manage the application lifecycle and track customizations. These actions allow for controlled promotion of changes, systematic deployment, and crucial health and performance monitoring of environments. Deploying changes directly to the production environment, manually copying customizations using file transfers, or relying solely on the built-in version control of the development environment do not provide the necessary control, tracking, or comprehensive ALM capabilities.

Overview of Lifecycle Services - Training | Microsoft Learn

Checklist for application lifecycle management - Dynamics 365 | Microsoft Learn