AZ-400 Chapter 7-10 Flashcards
3 reasons to use packages
extract shared components
build packages used by other teams
reduce build and CI time
3 aspects of dependency management
standardization
package formats
versioning
What are feeds?
Hosted in Azure Artifacts
support NuGet, npm, Maven, universal packs
You can make views on a feed
4 authority types: reader, collab, contributor, owners
each feed is an isolated repository
2 ways to publish a package?
Manually from computer
by pipeline - this won’t set the version number though, you have to do it in the build
What is semantic versioning?
Major.Minor.Patch[suffix] (suffix is pre release indicator)
only patch level ensures backward compatibility
Universal Packages
Aren’t associated with a build
can be stored up to 4 TB
Infrastructure as code: 2 approaches
Declarative - specify only desired state
Imperative - specify all steps to be taken
ARM templates
are JSON
must contain schema and contentVersion
parm section (or file)
variable section
functions
comments (java style)
resource section
output section
can use ‘dependsOn’
Ways to deploy ARM templates
Powershell
Pipeline
Azure CLI (cross platform)
Azure blueprints
code for building subscriptions and policy assignments
Azure Automation
uses a ‘run as’ account, replaced by managed identities
schedule can be used
modules are run (runbooks in powershell or python)
variables can be stored at account level
can use runbook gallery which are pre-made
End State Migrations
don’t track individual changes, just the latest version
tools then generate diff scripts at runtime
Metrics for quality
% of integration builds that fail
% of code covered by tests
amount of unplanned work
number of known issues
amount of technical debt
what is shifting left?
idea that automated tests should be done earlier
What are functional tests?
unit tests - one test per class
integration tests - use a few classes
system tests - use full app, take minutes to run
exploratory tests (manual)
scripted tests (manual)
