Backup and Restore: Azure Backup
Scenario: The VM is critical and has not been backed up in the past. The VM must enable
a quick restore from a 7-day snapshot to include in-place restore of disks in case of failure.
In-Place restore of disks in IaaS VMs is a feature of Azure Backup.
Performance: Accelerated Networking
Scenario: The VM shows high network latency, jitter, and high CPU utilization.
Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, greatly
improving its networking performance. This high-performance path bypasses the host from
the datapath, reducing latency, jitter, and CPU utilization, for use with the most demanding
network workloads on supported VM types.
References:
https://azure.microsoft.com/en-us/blog/an-easy-way-to-bring-back-your-azure-vm-with-inplace-
restore/

Scenario: Shipping website
Use Azure Content Delivery Network (CDN) and ensure maximum performance for
dynamic content while minimizing latency and costs.
Tier: Standard
Profile: Akamai
Optimization: Dynamic site acceleration
Dynamic site acceleration (DSA) is available for Azure CDN Standard from Akamai, Azure
CDN Standard from Verizon, and Azure CDN Premium from Verizon profiles.
DSA includes various techniques that benefit the latency and performance of dynamic
content. Techniques include route and network optimization, TCP optimization, and more.

You can use this optimization to accelerate a web app that includes numerous responses
that aren't cacheable. Examples are search results, checkout transactions, or real-time
data. You can continue to use core Azure CDN caching capabilities for static data.

Step 1: Create an integration account in the Azure portal
You can define custom metadata for artifacts in integration accounts and get that metadata
during runtime for your logic app to use. For example, you can provide metadata for
artifacts, such as partners, agreements, schemas, and maps - all store metadata using
key-value pairs.
Step 2: Link the Logic App to the integration account
A logic app that's linked to the integration account and artifact metadata you want to use.
Step 3: Add partners, schemas, certificates, maps, and agreements
Step 4: Create a custom connector for the Logic App.
References:
https://docs.microsoft.com/bs-latn-ba/azure/logic-apps/logic-apps-enterprise-integrationmetadata

Plan: Standard
Standard support auto-scaling
Instance Count: 10
Max instances for standard is 10.
Scenario:
The REST API’s that support the solution must meet the following requirements:
Allow deployment to a testing location within Azure while not incurring additional
costs.
Automatically scale to double capacity during peak shipping times while not
causing application downtime.
Minimize costs when selecting an Azure payment model.

Enable Cross-Origin Resource Sharing (CORS) on your Azure App Service Web App.
Enter the full URL of the site you want to allow to access your WEB API or * to allow all
domains.
Box 1: cors
Box 2: add
Box 3: allowed-origins
Box 4: http://testwideworldimporters.com/
References:
http://donovanbrown.com/post/How-to-clear-No-Access-Control-Allow-Origin-header-errorwith-
Azure-App-Service

Azure Database Migration service

Migrate from on-premises or cloud implementations of MongoDB to Azure Cosmos DB with
minimal downtime by using Azure Database Migration Service. Perform resilient migrations
of MongoDB data at scale and with high reliability.
Scenario: Data migration from on-premises to Azure must minimize costs and downtime.
The application uses MongoDB JSON document storage database for all container and
transport information.
References:
https://azure.microsoft.com/en-us/updates/mongodb-to-azure-cosmos-db-online-andoffline-
migrations-are-now-available/

Scenario: Shipping Function app: Implement secure function endpoints by using app-level
security and include Azure Active Directory (Azure AD).
Box 1: Function
Box 2: JSON based Token (JWT)
Azure AD uses JSON based tokens (JWTs) that contain claims
Box 3: HTTP
How a web app delegates sign-in to Azure AD and obtains a token
User authentication happens via the browser. The OpenID protocol uses standard HTTP
protocol messages.
References:
https://docs.microsoft.com/en-us/azure/active-directory/develop/authentication-scenarios

Box 2: http://test-shippingapi.wideworldimporters.com
Syntax: Access-Control-Allow-Origin: *
Access-Control-Allow-Origin: <origin>
Access-Control-Allow-Origin: null
<origin> Specifies an origin. Only a single origin can be specified.
Box 3: AllowedOrigins
Box 4: POST
The only allowed methods are GET, HEAD, and POST. In this case POST is used.
"<Corsrule>" "allowedmethods" Failed to load no "Access-control-Origin" header is present
References:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Integration Service Environment (ISE)

Explanation:
Scenario: The Shipping Logic App requires secure resources to the corporate VNet and
use dedicated storage resources with a fixed costing model.
You can access to Azure Virtual Network resources from Azure Logic Apps by using
integration service environments (ISEs).
Sometimes, your logic apps and integration accounts need access to secured resources,
such as virtual machines (VMs) and other systems or services, that are inside an Azure
virtual network. To set up this access, you can create an integration service environment
(ISE) where you can run your logic apps and create your integration accounts.
References:
https://docs.microsoft.com/en-us/azure/logic-apps/connect-virtual-network-vnet-isolatedenvironment-
overview