Explanation

Box 1: Custom text/string: A masking method, which exposes the first and/or last characters and adds a custom padding string in the middle.
Only show the last four digits of the values in a column named SuspensionSprings.
Box 2: Default
Default uses a zero value for numeric data types (bigint, bit, decimal, int, money, numeric, smallint, smallmoney, tinyint, float, real).
Scenario: Only show a zero value for the values in a column named ShockOilWeight.
Scenario:
The company identifies the following data masking requirements for the Race Central data that will be stored in SQL Database:
* Only show a zero value for the values in a column named ShockOilWeight.
* Only show the last four digits of the values in a column named SuspensionSprings.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/dynamic-data-masking-overview

Explanation

Step 1: Configure Blob storage as input; select items with the TIMESTAMP BY clause The default timestamp of Blob storage events in Stream Analytics is the timestamp that the blob was last modified, which is BlobLastModifiedUtcTime. To process the data as a stream using a timestamp in the event payload, you must use the TIMESTAMP BY keyword.
Example:
The following is a TIMESTAMP BY example which uses the EntryTime column as the application time for events:
SELECT TollId, EntryTime AS VehicleEntryTime, LicensePlate, State, Make, Model, VehicleType, VehicleWeight, Toll, Tag FROM TollTagEntry TIMESTAMP BY EntryTime Step 2: Set up cosmos DB as the output Creating Cosmos DB as an output in Stream Analytics generates a prompt for information as seen below.

Step 3: Create a query statement with the SELECT INTO statement.
References:
https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-inputs

References:
https://docs.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime

Explanation

Scenario:
All deployments must be performed by using Azure DevOps. Deployments must use templates used in multiple environments No credentials or secrets should be used during deployments

Explanation

The way you control access to resources using RBAC is to create role assignments. This is a key concept to understand - it's how permissions are enforced. A role assignment consists of three elements: security principal, role definition, and scope.
Scenario:
No credentials or secrets should be used during deployments
Phone-based poll data must only be uploaded by authorized users from authorized devices Contractors must not have access to any polling data other than their own Access to polling data must set on a per-active directory user basis References:
https://docs.microsoft.com/en-us/azure/role-based-access-control/overview