Microsoft AZ-400 Practice Exam Questions & Answers

To ensure every committed change to the webhook code automatically updates and publishes the webhook to Azure Automation, you should configure a webhook in your GitHub repository that triggers when code is committed. This webhook should point to an Azure Automation endpoint or trigger an Azure Pipeline that runs a runbook publication script. Alternatively, configure a pipeline trigger that automatically runs when repository code changes, then include a task to publish the runbook to Azure Automation.

Instead reduce the code complexity.

https://dzone.com/articles/fight-through-the-pain-how-to-deal-with-technical

With the storage account ready, you can configure backs up in the web app or App Service.

Open the App Serviceaz400-11566895-main, which you want to protect, in the Azure Portal and browse to Settings > Backups. Click Configure and a Backup Configuration blade should appear.

Select the storage account.

Click + to create a private container. You could name this container after the web app or App Service.

Select the container.

If you want to schedule backups, then set Scheduled Backup to On and configure a schedule: every five hours

Select your retention. Note that 0 means never delete backups.

Decide if at least onebackup should always be retained.

Choose if any connected databases should be included in the web app backup.

Click Save to finalize the backup configuration.

https://petri.com/backing-azure-app-service

To enable CodeQL scanning for C# code in GitHub Enterprise repositories:

• Solution: Use GitHub's CodeQL analysis feature by creating a CodeQL scanning workflow
• Steps:
  1. Navigate to the repository's Security tab
  2. Select 'Code scanning' or 'Code scanning alerts'
  3. Enable CodeQL or set up a workflow
  4. GitHub provides a default CodeQL workflow template that auto-detects C# code
  5. Commit the workflow file to your repository
• For C#: CodeQL supports C# analysis. The default workflow will automatically scan C# files
• Alternative (more manual): Manually create a GitHub Actions workflow file that runs github/codeql-action with C# language specification
• Automatic approach: Using GitHub's UI recommendation is simplest and requires minimal configuration
• Result: After enabling, CodeQL scans run on every push and PR, surfacing vulnerabilities in the code

For deploying Infrastructure as Code (IaC) resources to Azure using an Azure DevOps release pipeline, you should use template formats that Azure natively supports. The correct template formats are: Azure Resource Manager (ARM) templates (JSON format) and Bicep (which is a higher-level language that compiles to ARM templates). These are the official Azure IaC template formats. Terraform could also be used but is not Azure-specific. The question specifically asks for template formats for Azure deployment, so the answers should be ARM templates and/or Bicep templates.

To ensure a credential (cred1) can be used to deploy builds to production while restricting access to specific users and pipelines in Project1, you should: (1) Store the credential in Azure DevOps Library (variable groups) with appropriate pipeline permissions, or (2) Use service connections with role-based access control. The best approach is to create a service connection or variable group with restricted authorization that specifies which pipelines and users can access it. Azure DevOps allows you to set pipeline-level permissions on variable groups and service connections to ensure only specific pipelines can use the credential, and only authorized users can manage it.

The .artifactignore file uses a gitignore-like syntax. To meet the requirements:

• ** - Matches all files in the build output folder and all subfolders
• \n - Line break to separate patterns
• !**/*.dll - Excludes files with the .dll extension using the negation operator (!)

The correct syntax should include all files by default and then exclude .dll files: **\n!**/*.dll