Shaohua Fan Reading time ~1 minute

  1. inbound

Outbound

Backend

  1. C

Page 25

Page 26

Page 27

Shaohua Fan Reading time ~3 minutes

  1. AB X BD

https://docs.microsoft.com/en-us/azure/azure-monitor/app/custom-operations-tracking

  1. Y

Y X N

Y

https://docs.microsoft.com/en-us/azure/frontdoor/front-door-caching

  1. Set if missing X Override

1 hour

Cache every unique URL

  1. Standard

Enable

Add

Configure

Page 21

  1. N

  2. N

Instead deploy and configure Azure Cache for Redis. Update the web applications.

  1. ICache X IDatabase ValueDel

  2. Create trigger on message Action to read IoT Add a condition to compare Add to send email

  3. Funnels

Impact

User flows X Retention

User flows

  • Retention - how many users come back?

  • Users tool: How many people used your app and its features. Users are counted by using anonymous IDs stored in browser cookies. A single person using different browsers or machines will be counted as more than one user.

  • Sessions tool: How many sessions of user activity have included certain pages and features of your app. A session is counted after half an hour of user inactivity, or after 24 hours of continuous use.

  • Events tool: How often certain pages and features of your app are used. A page view is counted when a browser loads a page from your app, provided you’ve instrumented it.

  • Funnel: If your application involves multiple stages, you need to know if most customers are progressing through the entire process, or if they’re ending the process at some point. The progression through a series of steps in a web application is known as a funnel

  • User flows:

    • How do users navigate away from a page on your site?
    • What do users click on a page on your site?
    • Where are the places that users churn most from your site?
    • Are there places where users repeat the same action over and over?

Page 22

  1. B X A

  2. AD

  3. A

  4. A

  5. ago

distinct

where

summarize count()

Page 23

  1. config

–docker-container-log

webapp

tail

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

az webapp log config -h

Command
    az webapp log config : Configure logging for a web app.

Arguments
    --application-logging      : Configure application logging.  Allowed values: azureblobstorage,
                                 filesystem, off.
    --detailed-error-messages  : Configure detailed error messages.  Allowed values: false, true.
    --docker-container-logging : Configure gathering STDOUT and STDERR output from container.
                                 Allowed values: filesystem, off.
    --failed-request-tracing   : Configure failed request tracing.  Allowed values: false, true.
    --level                    : Logging level.  Allowed values: error, information, verbose,
                                 warning.
    --slot -s                  : The name of the slot. Default to the productions slot if not
                                 specified.
    --web-server-logging       : Configure Web server logging.  Allowed values: filesystem, off.

az webapp log -h

Group
    az webapp log : Manage web app logs.

Subgroups:
    deployment [Preview] : Manage web app deployment logs.

Commands:
    config               : Configure logging for a web app.
    download             : Download a web app's log history as a zip file.
    show                 : Get the details of a web app's logging configuration.
    tail                 : Start live log tracing for a web app.
  1. BC

Types of tests

There are four types of availability tests:

  • URL ping test (classic): You can create this simple test through the portal to validate whether an endpoint is responding and measure performance associated with that response. You can also set custom success criteria coupled with more advanced features, like parsing dependent requests and allowing for retries.
  • Standard test (Preview): This single request test is similar to the URL ping test. It includes SSL certificate validity, proactive lifetime check, HTTP request verb (for example GET, HEAD, or POST), custom headers, and custom data associated with your HTTP request.
  • Multi-step web test (classic): You can play back this recording of a sequence of web requests to test more complex scenarios. Multi-step web tests are created in Visual Studio Enterprise and uploaded to the portal, where you can run them.
  • Custom TrackAvailability test: If you decide to create a custom application to run availability tests, you can use the TrackAvailability() method to send the results to Application Insights.

https://docs.microsoft.com/en-us/azure/azure-monitor/app/availability-overview

internal X External

consumption plan doesn’t support build-in cache.

private

Authorization

https://docs.microsoft.com/en-us/azure/api-management/api-management-caching-policies#CachingPolicies

  1. D

  2. A

Page 24

  1. Register -> Build -> Create auth provider -> Create new instance -> Invoke

  2. Storage -> Log Analytics -> diagnostic settings to Azure Logic App

X

Log Analytics -> Install LogicApp Management solution -> diagnostic settings to Azure Logic App

To set up logging for your logic app, you can enable Log Analytics when you create your logic app, or you can install the Logic Apps Management solution in your Log Analytics workspace for existing logic apps.

  1. Log -> ApplicationInsight -> Install -> VMInsight

X

Log -> VMInsight -> Install -> ApplicationInsight

Shaohua Fan Reading time ~1 minute

In app registration, select New registration

Select Azure AD

Wrong

In app registration, select New registration

Select Azure AD

Create a new application

https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app

Page 13

  1. AC X BC

Prerequisites:

A working Azure AD tenant with at least an Azure AD Premium P1 or trial license enabled.

The recommended way to enable and use Azure AD Multi-Factor Authentication is with Conditional Access policies.

https://docs.microsoft.com/en-us/azure/active-directory/authentication/tutorial-enable-azure-mfa

  1. C

  2. B

  3. Y

  4. Y

Page 14

  1. Soft deletion

Purge protection

  1. AD

9. client_id, application, profile X

  1. UseAuth UseAuthorization UseAzureAppConfiguration

  2. C

Page 15

  1. Y

  2. Y X

The requirement is to save scanned copies of patient intake forms. Which is kind of unstructured data, should not be saved with cosmos db. Using azure blob storage instead.

  1. N

  2. keyvault

keyvault key

vm

vm encryption

data X all

  1. C

Page 16

  1. 5->3->4->2->1

X

5->3->2->1->4

  1. N

  2. Y X

Role-based access control is used for authorization and not authentication.

  1. Device

iPhone X iOS

Header

User_agent

iPhone

  1. Y X

Page 17

  1. Y

  2. optionalClaims

requiredResourceAccess

https://docs.microsoft.com/en-US/azure/active-directory/develop/reference-app-manifest?WT.mc_id=Portal-Microsoft_AAD_RegisteredApps

  1. B

  2. B X A

  1. D

Page 18

  1. D

  2. Inbound

Inbound

Outbound Outbound

  1. SecretClient

ClientSecretCredential X DefaultAzureCredential

This example is using ‘DefaultAzureCredential()’ class from Azure Identity Library, which allows to use the same code across different environments with different options to provide identity. For more information about authenticating to key vault, see Developer’s Guide.

https://docs.microsoft.com/en-us/azure/key-vault/secrets/quick-create-net#authenticate-and-create-a-client

  1. AB

31. AC X AD

The question requires to use SAS token, C is not correct.

https://docs.microsoft.com/en-us/rest/api/storageservices/create-user-delegation-sas#revoke-a-user-delegation-sas

Page 19

  1. Generate key blob-> Generate KEK-> Retrieve KEk-> key import

X

Generate KEK-> Retrieve KEk-> Generate key blob-> key import

User steps To perform a key transfer, a user performs following steps:

  1. Generate KEK.
  2. Retrieve the public key of the KEK.
  3. Using HSM vendor provided BYOK tool - Import the KEK into the target HSM and exports the Target Key protected by the KEK.
  4. Import the protected Target Key to Azure Key Vault.

Customers use the BYOK tool and documentation provided by HSM vendor to complete Steps 3. It produces a Key Transfer Blob (a “.byok” file).

https://docs.microsoft.com/en-us/azure/key-vault/keys/byok-specification

  1. A

  2. YYYY

  3. AC

36. Y X N

N

Y

https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-choose-offer

Page 20

  1. Builder scopes

Page 21

Page 22