A successful IOS device build will produce an ipa file. In order to install the build on a device, it needs to be signed with a validprovisioning profile and certificate. To sign the builds produced from a branch, enable code signing in the configuration pane and upload a provisioning profile (.mobileprovision) and a valid certificate (.p12) , along with the password for the certificate.
References:
https://docs.microsoft.com/en-us/appcenter/build/xamarin/ios/

Explanation:

Box 1: rwx
The Log Analytics agent for Linux runs as the omsagent user. To grant >write permission to the omsagent user, run the command setfacl -m u:omsagent:rwx /tmp.
Box 2: /tmp
Deploying DSC to a Linux node uses the /tmp folder.
Reference:
https://docs.microsoft.com/en-us/azure/automation/automation-dsc-onboarding
Topic 3, Woodgrove bank
This is a case study.Case studies are not timed separately. You can use as much exam time as you would like to complete each case.However, there may be additional case studies and sections on this exam. You must manage yourtime to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might containexhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click theNextbutton. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has anAll Informationtab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click theQuestionbutton to return to the question.
Overview
General Overview
Woodgrove Bank is a financial services company that has a main office in the United Kingdom.
Technical Requirements and Planned Changes
Planned Changes
Woodgrove Bank plans to implement the following project management changes:
Implement Azure DevOpsfor project tracking.
Centralize source code control in private GitHub repositories.
Implement Azure Pipelines for build pipelines and release pipelines.
Woodgrove Bank plans to implement the following changes to the identity environment:
Deploy an Azure AD tenant named woodgrovebank.com.
Sync the Active Directory domain to Azure AD.
Configure App1 to use a service principal.
Integrate GitHub with Azure AD.
Woodgrove Bank plans to implement the following changes to the core apps:
Migrate App1 to ASP.NET Core.
Integrate Azure Pipelines and the third-party build tool used to develop App2.
Woodgrove Bank plans to implement the following changes to the DevOps environment:
Deploy App1 to Azure App Service.
Implement source control for the DB1 schema.
Migrate all the source code from TFS1 to GitHub.
Deploy App2 to an Azure virtual machine named VM1.
Merge the POC branch into the GitHub default branch.
Implement an Azure DevOps dashboard for stakeholders to monitor development progress.
Technical Requirements
Woodgrove Bank identifies the following technical requirements:
The initial databases for new environments must contain both schema and reference data.
An Azure Monitor alert for VM1 must be configured to meet the following requirements:
Be triggered when average CPU usage exceeds 80 percent for 15 minutes.
Calculate CPU usage averages once every minute.
The commit history of the POC branch must replace the history of the default branch.
The Azure DevOps dashboard must display the metrics shown inthe following table.

Access to Azure DevOps must be restricted to specific IP addresses.
Page load times for App1 must be captured and monitored.
Administrative effort must be minimized.

With enterprise level of SonarQube you can use OWASP that runs the securityscans for known vulnerabilities. https://www.sonarqube.org/features/security/https://www.sonarqube.org/features/security
/owasp/?gclid=Cj0KCQiAzZL-BRDnARIsAPCJs70Teq0-efI2Hd_h-
kykCB7I_C7L88Q7kpiuTzuD6Xw1jUb6ZqIP7O0aApVzEALw_wcB

Explanation:

Box 1: User Flows
The User Flows tool visualizes how users navigate between the pages and features of your site. It's great for answering questions like:
How do users navigate away from a page on your site?
What do users click ona 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?
Box 2: Users
Box 3: Impact
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/usage-flows