1.
`bash az ad app permission grant -display-name $appName ...`
2.
`bash az ad app credential create -display-name $appName ...`
3.
`bash az ad app create -display-name $appName ...`
4.
`bash az ad app permission ass -display-name $appName ...`
Q 1 / 55
**Explanation:** Twilio is an SMS notification app, also not from Microsoft. Event Grid can be techincally used for this purpose but it's a more generic event-broadcasting service. Service Bus is another generic publish-subscribe solution. Finally [Notification Hubs](https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-overview) are specifically designed for push-notifications.1.
Notification Hub
2.
Event Grid
3.
Twilio
4.
Service Bus
Q 2 / 55
1.
service principal and a certificate
2.
managed identity
3.
service principal and a secret
4.
shared access key
Q 3 / 55
1.
Do nothing. The API server will provision additional storage automatically
2.
Add a data disk definition for the AKS cluster to your apps YAML manifest
3.
Add a data disk to each Kubernetes cluster node and reattempt app deployment
4.
Provision an Azure Files instance and reattempt app deployment
Q 4 / 55
1.
Application gateway
2.
Front Door
3.
API Management
4.
Traffic manager
Q 5 / 55
1.
Add the assets to a git repository
2.
Add the assets in Key Vault
3.
Add the assets to an encrypted volume
4.
Add the assets to a library
Q 6 / 55
1.
Azure AD user account
2.
Shared access signature
3.
Shared key
4.
Certificate
Q 7 / 55
1.
Configure application insights cohort
2.
Install the Log Analytics agent and configure Azure Monitor for Containers
3.
Install the App Insights on AKS nodes
4.
Add instrumentation to your app to send usage analytics with Application Insights.
Q 8 / 55
1.
based on a time (schedule)
2.
another Azure service (cosmos, service bus)
3.
threshold alert in Azure App insights
4.
third party services (GitHub)
Q 9 / 55
1.
Service Bus
2.
Event Hub
3.
Notification Hub
4.
Event Grid
Q 10 / 55
1.
Populate from a BACPAC file.
2.
Restore from a backup file.
3.
Populate from a CSV file.
4.
Populate from a SQL file.
Q 11 / 55
1.
Azure Storage static website
2.
static website with Azure CDN
3.
App Service on Consumption plan
4.
App Service on Standard plan
Q 12 / 55
**Hint:** If you see the words REST and throttling - the answer is almost always API Management. It's the most expensive solution but is specifically designed to proxy the REST API.1.
Front door
2.
API Management
3.
Traffic manager
4.
Application Gateway
Q 13 / 55
1.
Enable Network Performance Monitor on the VMs.
2.
Install the Log Analytics Agent and enable Azure Monitor for VMs.
3.
Install the Application Insights Agent.
4.
Enable SolarWinds Performance Monitor from the Azure Marketplace.
Q 14 / 55
1.
a Manual Intervention task
2.
a pre-deployment condition
3.
a branch filter
4.
a pre-deployment gate
Q 15 / 55
1.
Create a service principal in Azure then assign the service principal AKS.
2.
Add users an Azure AD security group. Then assign the group permissions to AKS.
3.
Create a service principal in Azure AD. Then add user to the AKS security group.
4.
Create an App ID in Azure AD. Then create a service principal for the server app.
Q 16 / 55
1.
Network File System (NFS)
2.
HTTPS
3.
REST API
4.
Server Message Block(SMB)
Q 17 / 55
1.
Dynamic Data Masking
2.
Transparent Data Encryption
3.
Row-Level Security
4.
Always Encrypted
Q 18 / 55
1.
service principals
2.
certificates
3.
access policies
4.
RBAC roles
Q 19 / 55
1.
Create a Logic App. Then configure an action group with the Logic App action type.
2.
Create an Azure Automation Runbook. Then configure an action group with the Automation Runbook action type.
3.
Configure an autoscale rule based on a metric.
4.
Create an Azure function. Then configure an action group with the Secure Webhook action type.
Q 20 / 55
1.
Query Work Items gate
2.
Manual Intervention task
3.
Approval gate
4.
Invoke REST API gate
Q 21 / 55
1.
Trigger scale down in Azure Container Instances.
2.
Trigger scale down in the HPA from the Azure CLI.
3.
Manually deprovision unneeded pods.
4.
Do nothing. HPA will initiate scale down automatically.
Q 22 / 55
1.
Install Azure Resource Manager Tools extension in VS Code.
2.
Install Visual Studio 2019 Enterprise edition.
3.
Install Visual Studio 2019 Community edition.
4.
Install Visual Studio Code IntelliCode extension in VS Code.
Q 23 / 55
1.
Agile
2.
Waterfall
3.
Basic
4.
CMMI
Q 24 / 55
1.
Azure SQL elastic pool
2.
SQL on Azure VMs
3.
Azure SQL Database
4.
SQL Managed Instance
Q 25 / 55
1.
append blob
2.
table storage
3.
page blob
4.
block blob
Q 26 / 55
1.
Azure CLI
2.
Azure Portal
3.
Azure PowerShell
4.
REST API
Q 27 / 55
1.
LUIS
2.
Text to Speech
3.
QnA Maker
4.
Form Recognizer
Q 28 / 55
1.
managed identity (shared)
2.
X.509 certificate
3.
managed service identity (per device)
4.
SAS key
Q 29 / 55
json { "type": "Microsoft.Compute/virtualMachines", "name": "[concat('myvm', `______`)]", "apiVersion": "2016-04-30-preview", "location": "[parameters('location')]", "copy": " ", "name": "virtualMachineLoop", "count": "[parameters('numberOfInstances')]" },1.
max()
2.
copyIndex()
3.
createArray()
4.
indexOf()
Q 30 / 55
1.
Install the Analytics agent and configure Azure Monitor for Containers.
2.
Install the App Insights Agent on AKS nodes.
3.
Configure Application Insights cohorts.
4.
Add instrumentation to your app to send usage analysis with Application Insights.
Q 31 / 55
1.
page blob
2.
block blob
3.
table storage
4.
queue storage
Q 32 / 55
1.
Store secrets in Azure Key Vault.
2.
Store secrets in a configuration file.
3.
Configure release variables.
4.
Configure a variable group.
Q 33 / 55
1.
Configure the horizontal pod autoscaler (HPA).
2.
Manually scale pod when necessary.
3.
Configure burst to Azure Container Instances.
4.
Do nothing. Pods running on AKS scale up automatically.
Q 34 / 55
1.
with a community-developed Key Vault task
2.
with an ARM template
3.
all of these answers
4.
with an Azure CLI script in a Bash task
Q 35 / 55
/SourceServerName:"kinetecosql.database.windows.net" /SourceDatabaseName:"kinetecoweb" /SourceUser:"admin" /SourcePassword:"MyPassword" /SourceServerName:"kinetecosql.database.windows.net" /SourceDatabaseName:"kinetecoweb" /SourceUser:"admin" /SourcePassword:"MyPassword" /SourceServerName:"kinetecosql.database.windows.net" /SourceDatabaseName:"kinetecoweb" /SourceUser:"admin" /SourcePassword:"MyPassword" /SourceServerName:"kinetecosql.database.windows.net" /SourceDatabaseName:"kinetecoweb" /SourceUser:"admin" /SourcePassword:"MyPassword"1.
SqlPackage.exe /TargetFile:" myapp.bacpac " /Action:**Export**
2.
SqlPackage.exe /TargetFile:" myapp.bacpac " /Action:**Import**
3.
SqlPackage.exe /TargetFile:"./myapp.bacpac" /Action:**Publish**
4.
SqlPackage.exe /TargetFile:"./myapp.bacpac" /Action:**Extract**
Q 36 / 55
1.
service map in Azure Monitor
2.
application maps in Azure Application Insights
3.
availability tests in Azure Application Insights
4.
Profiler in Azure Application Insights
Q 37 / 55
1.
Change to a self-hosted agent pool running Ubuntu 16.04 LTS or later.
2.
Changed to a hosted pool running Windows 2019.
3.
Change to a hosted agent pool running Ubuntu 16.04 LTS or later.
4.
Change to a self-hosted agent pool running Windows 2019.
Q 38 / 55
1.
Event Grid
2.
Service Bus
3.
Event Hub
4.
Queue Storage
Q 39 / 55
1.
LoadBalancer
2.
NodePort
3.
Cluster IP
4.
ExternalName
Q 40 / 55
1.
The lifecycle of a user-managed identity is managed separately from the resource.
2.
with a user-assigned managed identity, Azure manages the password for you.
3.
The lifecycle of a system-managed identity is managed separately from the resource.
4.
with a system-assigned managed identity, Azure manages the password for you.
Q 41 / 55
1.
Organization: Administrator; Project: Service Account
2.
Organization: Reader; Project: Service Account
3.
Organization: Reader; Project: Administrator
4.
Organization: Service Account; Project: Reader
Q 42 / 55
1.
Agent.WorkFolder
2.
Agent.HomeDirectory
3.
Agent.BuildDirectory
4.
Agent.ToolsDirectory
Q 43 / 55
1.
Event Hub
2.
Event Grid
3.
Service Bus
4.
Queue Storage
Q 44 / 55
1.
on the secret itself
2.
by secret type
3.
on the Key Vault instance
4.
at the Azure Subscription level
Q 45 / 55
`Dynamic data masking helps prevent unauthorized access to sensitive data by enabling customers to designate how much of the sensitive data to reveal with minimal impact on the application layer.`1.
Implement dynamic data masking and include the managers group.
2.
Implement transparent data encryption and include the managers group.
3.
Implement dynamic data masking and exclude the managers group.
4.
Implement transparent data encryption and exclude the managers group.
Q 46 / 55
1.
Run the troubleshooting wizards under Resource and solve problems.
2.
Enable Intelligent Insights.
3.
Configure App Insights to alert admins when web interface experiences latency.
4.
Configure an alert rule to email DBAs when DTU usage hits 100%.
Q 47 / 55
1.
SMB
2.
REST API
3.
Storage Explorer
4.
NFS
Q 48 / 55
1.
Download the GitHub repository to a Zip file, and then unzip the repository in Azure DevOps.
2.
From the **Import a Git repository** menu, select **Import**.
3.
Create a service connection to the GitHub repository.
4.
Create a webhook in GitHub and then trigger it from Azure DevOps.
Q 49 / 55
1.
Configure an additional App Service instance. In Azure DevOps, enable an approval gate for deployment.
2.
Configure an Azure load balancer to redirect traffic to the approved App Service instance.
3.
Configure an additional deployment slot in the existing App Service instance.
4.
Configure an App Service Environment (ASE).
Q 50 / 55
1.
Table storage
2.
append blob
3.
page blob
4.
block blob
Q 51 / 55
1.
`dcpromo.exe`
2.
`dcgpofix.exe`
3.
`dcdiagfix.exe`
4.
`ntdsutil.exe`
Q 52 / 55
As described in [Microsoft Docs: Hosting a Restful-API with CORS in AAS](https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-rest-api): The Answer should be CORS (Cross Origin Ressource Sharing)1.
`CORS`
2.
`deployment slots`
3.
`WebJobs`
4.
`custom domains`
Q 53 / 55
1.
parallel
2.
out
3.
asynchronous
4.
in
Q 54 / 55
1.
Event Grid
2.
Service Bus
3.
Event Hub
4.
Queue Storage
Q 55 / 55