Explanation:
Box 1: standard solid-state drives (SSDs)
Standard SSD Managed Disks, a low-cost SSD offering, are optimized for test and entry-level production workloads requiring consistent latency.
Box 2: to another Azure region
Geo-redundant storage (GRS) copies your data synchronously three times within a single physical location in the primary region using LRS. It then copies your data asynchronously to a single physical location in a secondary region that is hundreds of miles away from the primary region.
References:
https://azure.microsoft.com/en-us/pricing/details/managed-disks/
https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy#geo-redundant-storage

Explanation
References:
https://wiki.scn.sap.com/wiki/display/SM/Hardware+Capacity+Checks+in+EWA

Load balancers. These are used to distribute traffic to virtual machines in the application-tier subnet. For high availability, use the built-in SAP Web Dispatcher, Azure Load Balancer, or network appliances, depending on the traffic type (such as HTTP or SAPGUI) or the required network services, such as Secure Sockets Layer (SSL) termination.
Reference:
https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/sap/sap-netweaver

Explanation

Box 1: Yes
Scenario: Technical requirements: Ensure that an application server can be restored from a backup created during the last five days within 15 minutes.
Instant Restore has 'The instance recovery snapshot(s) for 5 Day(s)'.
Box 2: No
Scenario: Ensure that all the production application servers can restore daily backups from the last 21 days.
The Retention of daily backup point is set to for 14 days only.
Box 3: Yes
Reference:
https://docs.microsoft.com/en-us/azure/backup/backup-instant-restore-capability

Explanation
Scenario: Ensure that all the production databases can withstand the failure of an Azure region.
Note: Use Azure Site Recovery to replicate applications across regions. Azure Site Recovery replicates workloads running on physical and virtual machines from a primary site (either on-premises or in Azure) to a secondary location (in Azure). When an outage occurs at the customer's primary site, a failover can be triggered to quickly return the customer to an operational state. After the primary location is restored, customers can then fail back.
References:
https://docs.microsoft.com/en-us/azure/architecture/resiliency/recovery-loss-azure-region