Scale up ASP1 : Correct
Basic App service plan does not support backup/restore.

The Backup and Restore feature requires the App Service plan to be in the Standard, Premium or Isolated tier. Since in question it is mentioned as a Basic service plan app so at first you need to do it to Scale up the service plan so that backup can be enabled on App1.
Scale up: Get more CPU, memory, disk space, and extra features like dedicated virtual machines (VMs), custom domains and certificates, staging slots, autoscaling, and more. You scale up by changing the pricing tier of the App Service plan that your app belongs to.
Configure a WebJob for App1 : Incorrect
WebJobs is a feature of Azure App Service that enables you to run a program or script in the same instance as a web app, API app, or mobile app. There is no additional cost to use WebJobs

Scale out ASP1 : Incorrect
Scale out: Increase the number of VM instances that run your app. You can scale out to as many as 30 instances, depending on your pricing tier.
Configure the application settings for App1 : Incorrect
This is the 2nd step you need to perform once azure service plan upgraded to standard.
Most folks don't realize how easy it is to configure a backup copy of your Azure App Service to ensure you have restorable archive copies of your app and database. In order to take advantage of this, you'll need to log into your Azure account and go to your App Service that you created and look under Settings then you will see Backup

Reference:
https://azure.microsoft.com/en-in/pricing/details/app-service/windows/
https://docs.microsoft.com/en-us/azure/app-service/manage-scale-up
https://docs.microsoft.com/en-us/azure/app-service/webjobs-create
https://microsoft.github.io/AzureTipsAndTricks/blog/tip28.html

DC1 : Not supported as it is Gen2 and OS disk size is greater than 300 GB FS1 : Not supported as it is Gen2 and Linux VM. Linux Generation 2 VMs aren't supported.
CA1 : Not supported as bitlocker is enabled. BitLocker must be disabled before you enable replication for a VM.
SQL1: Supported
Reference:
https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-support-matrix#azure-vm-requirements

The primary use case for the Azure Desired State Configuration (DSC) extension is to bootstrap a VM to the Azure Automation State Configuration (DSC) service. The service provides benefits that include ongoing management of the VM configuration and integration with other operational tools, such as Azure Monitoring. Using the extension to register VM's to the service provides a flexible solution that even works across Azure subscriptions.
You can use the DSC extension independently of the Automation DSC service.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/dsc-overview

If you have an existing virtual network, either select an existing empty subnet or create a new subnet in your existing virtual network solely for use by the application gateway.
Verify that you have a working virtual network with a valid subnet. Make sure that no virtual machines or cloud deployments are using the subnet. The application gateway must be by itself in a virtual network subnet.
Reference:
https://social.msdn.microsoft.com/Forums/azure/en-US/b09367f9-5d01-4cda-9127-b7a506a0a151/cant-create-application-gateway?forum=WAVirtualMachinesVirtualNetwork
https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-create-gateway

As D drive is temporary storage so new files on D drive will be lost. The screensaver, wall paper, new files on C drive are available after Redeploy.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/redeploy-to-new-node-windows