Azure Developer Associate - D306

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/113

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

114 Terms

1
New cards

IaaS

Infrastructure as a Service model provides more granular control but requires maintenance and budget for support infrastructure.

2
New cards

PaaS

Platform as a Service model reduces infrastructure requirements, allowing focus solely on the code, but offers less control.

3
New cards

VMs

Virtual Machines are used when requiring more control over application elements, involving management of OS-related admin tasks like upgrades and patches.

4
New cards

Azure Portal

Web-based interface for managing Azure services, allowing users to create, monitor, and manage resources.

5
New cards

Resource Group

A logical container for grouping Azure resources that share the same lifecycle, permissions, and policies.

6
New cards

ARM Templates

Azure Resource Manager Templates are JSON files used to define the resources needed for an application deployment in a consistent structure.

7
New cards

ContentVersion

An internal version number in ARM Templates that changes if there are significant alterations to the template.

8
New cards

Parameters

Elements in ARM Templates that allow setting values provided to the Resource Manager for deployment.

9
New cards

Variables

In ARM Templates, variables improve readability and usability by storing values for reuse throughout the template.

10
New cards

Functions

In ARM Templates, functions are optional elements that improve code readability, usability, and debugging.

11
New cards

Outputs

Optional elements in ARM Templates that define values the Resource Manager should return after deployment.

12
New cards

dependsOn Element

In ARM Templates, specifies dependencies for the resource type, ensuring resources are deployed in the correct order.

13
New cards

Azure Cloud Shell

Browser-accessible shell for managing Azure resources, providing a command-line interface with built-in tools.

14
New cards

Azure CLI

Command-line interface for managing Azure resources, allowing users to script operations using commands in the terminal.

15
New cards

REST API

Representational State Transfer Application Programming Interface allows interaction with Azure services over HTTP.

16
New cards

Resource Provider

In ARM Templates, a service that offers specific Azure resources, such as Microsoft.Compute for VM resources.

17
New cards

Resource Manager

Azure service for managing and organizing resources, enabling consistent deployment and management through ARM Templates.

18
New cards

Resource

In Azure, a manageable item that is provisioned or updated through Azure Resource Manager.

19
New cards

Resource Group Deployment

Type of deployment in ARM Templates that targets resources within a specific resource group.

20
New cards

Subscription Deployment

Type of deployment in ARM Templates that targets resources within an Azure subscription.

21
New cards

Child Elements vs Dependencies

In ARM Templates, child elements and dependencies are not the same; dependencies are defined using the dependsOn element to ensure correct deployment order.

22
New cards

Public IP

Internet Protocol address that can be accessed over the public internet, available as static or dynamic.

23
New cards

NSG

Network Security Group in Azure that acts as a virtual firewall to control inbound and outbound traffic to Azure resources.

24
New cards

container

piece of software that groups code and dependencies into a single package that can be run from the computer environment

25
New cards

Docker Containers

most widely used container technology

26
New cards

orchestration solutions for automatically scaling/deploying containers

Docker Swarm, DC/OS, Kubernetes

27
New cards

container image

package containing code, libraries, environment variables, and configuration files needed to run applications

28
New cards

Docker Compose

used to define and run multiple containers

29
New cards

ACR

Azure Container Registry - Microsoft's implementation of a Docker registry service

30
New cards

Azure App Service

PaaS solution based on HTTP assisting with developing apps, mobile application back-end, and REST APIs

31
New cards

Azure App Service plan

requires providing region of deployment, number and size of instances, and OS platform (Windows/Linux)

32
New cards

VNet Integration

allows integration with virtual network, available only with Standard, Premium, Premium V2 pricing tiers

33
New cards

Hybrid connections

depends on Azure Service Bus Relay, enables traffic between specific TCP host/port combinations

34
New cards

Isolated pricing tier

offers dedicated VMs running on dedicated virtual networks

35
New cards

Web Server diagnostics

includes Detailed error logging, Failed Request tracing, and Web Server logging

36
New cards

Application Diagnostics

sending log messages from code to log system

37
New cards

Deployment Diagnostics

automatically enabled for troubleshooting during deployment process

38
New cards

deployment slots

require Standard pricing tier or better, each with its own host name settings

39
New cards

Kudu

platform responsible for Git deployments in Azure App Service

40
New cards

ARM templates

used for deploying resources consistently and repeatedly

41
New cards

Application Settings

configure environment variables passed to your code

42
New cards

Connection Strings

configure connection strings for the database your code relies on

43
New cards

Stack Settings

options include .NET, .NET Core, Java, PHP, Python

44
New cards

Platform Settings

configures platform, managed pipeline version, FTP state, HTTP version, Web Sockets, Always On, ARR Affinity

45
New cards

Debugging

enables remote debugging options, automatically turns off after 48 hours

46
New cards

Default Documents

configures which web page is displayed at root URL

47
New cards

Path Mappings

depend on OS selection

48
New cards

Handler Mapping

custom script processors for different file extensions

49
New cards

Virtual Applications and Directories

for adding to your App Service

50
New cards

Implement autoscaling rules

automatically adding/removing resources based on defined rules

51
New cards

Vertically scaling

scaling up/down by adding more computing power, requires stopping the system while VM is resizing

52
New cards

Azure Cloud Services

Has built-in autoscaling capabilities.

53
New cards

Profile condition

Defines the rule for adding or removing resources and can set default, max, and min allowed instances.

54
New cards

Binding

Uses Azure Functions to connect functions to external resources without hard-coding connections.

55
New cards

Triggers

Events that cause a function to execute.

56
New cards

CRON expression

A string compound of six fields specifying a schedule for triggers, including seconds, minutes, hours, days, months, and days of the week.

57
New cards

Range of values

Used in CRON expressions to specify a range of values for a trigger.

58
New cards

Interval of values

Used in CRON expressions to specify when a function is executed based on the divisibility of a field value.

59
New cards

TimeSpan expressions

Strings with format hh:mm:ss used to configure schedules for triggers.

60
New cards

Webhooks

Used to run functions based on HTTP requests or external webhooks.

61
New cards

HTTPTrigger parameter attribute

Configures authorization key, methods, route, and WebHookType for accessing functions via HTTP triggers.

62
New cards

WebHookType

Specifies the type of webhook trigger, such as genericJson, GitHub, Slack, or webhook.

63
New cards

Application Insight integration

Enables viewing log messages from functions by integrating with Application Insights.

64
New cards

Azure Functions Version

Differentiates between versions 1.0, 2.0, and 3.0, with compatibility and development platform distinctions.

65
New cards

Admin endpoints

Automatically exposed by deployed Azure Function Apps for programmatically accessing app aspects, protected by access codes or authentication keys.

66
New cards

host key

Authorization key shared by all functions deployed in a Function App; allows access to any function in the host

67
New cards

function key

Authorization key that only protects the functions where they are defined; takes precedence over host key when they have the same name

68
New cards

_master

A particular host key used when needing access to admin endpoints and setting the admin value to the AuthLevel trigger configuration parameter

69
New cards

Azure Functions

Stateless functions where the state of created objects during function execution is not maintained if the virtual machine is recycled or rebooted

70
New cards

Azure Durable Functions

An extension of Azure Functions providing stateful workflow capabilities in a serverless environment, easing the implementation of complex stateful coordination requirements

71
New cards

Chaining

The process of one function calling other functions in a sequence

72
New cards

Orchestrator

In Durable Functions, defines the actions of the workflow; each instance has an instance identifier that can be created manually or generated dynamically

73
New cards

Client

The entry point of a workflow that creates instances of orchestrator functions by sending an orchestrator trigger

74
New cards

Orchestration Trigger

A trigger used in Durable Functions that is single-threaded and focuses on calling activity functions in the correct order

75
New cards

Activity Trigger

A trigger used in Durable Functions for writing activity functions, allowing communication between orchestration and activity functions; multi-threaded with no restrictions on threading or I/O operations

76
New cards

Patterns for showing how orchestration and activity functions interact

Include Chaining, Fan out/fan in, Async HTTP APIs, Monitor, Human Interaction, and Aggregator

77
New cards

Binding mechanism

Mechanism in Durable Functions to pass information between different functions in the workflow

78
New cards

Cosmos DB

premium storage service that provides a globally-distributed, low-latency, highly responsive, and always-online database service

79
New cards

Key-Value

approach for storing data in Cosmos DB

80
New cards

Column-Family

approach for storing data in Cosmos DB

81
New cards

Documents

approach for storing data in Cosmos DB

82
New cards

Graph

approach for storing data in Cosmos DB

83
New cards

SQL

the core and default API for accessing data in a Cosmos DB account; allows querying of JSON objects with SQL syntax

84
New cards

Table

evolution of the Azure Table Storage service; allows defining indexes in tables and storing information based on documents

85
New cards

Cassandra

column-based database that stores information using a key-value approach; Cosmos DB implements the wire protocol for Apache Cassandra

86
New cards

MongoDB

NoSQL database that allows storing application information in a document-based structure; Cosmos DB implements the wire protocol compatible with MongoDB 3.2

87
New cards

Gremlin

API based on the Apache TinkerPop graph traversal language; allows storing information in Cosmos DB with a graph structure

88
New cards

Vertices

entities in a graph structure stored in Cosmos DB

89
New cards

Edges

relationships between vertices in a graph structure stored in Cosmos DB

90
New cards

Properties

attributes assignable to vertices or edges in a graph structure stored in Cosmos DB

91
New cards

Logical partitions

divisions based on user-defined criteria in Cosmos DB; all items share the same partition key

92
New cards

Partition keys

immutable keys used for partitioning data in Cosmos DB; critical for distributing data across logical partitions

93
New cards

Hot partition

occurs when the partition key in Cosmos DB is not specific enough, leading to most requests and reaching throughput/storage limits

94
New cards

Synthetic partition key

a key compound of two concatenated properties used for partitioning data in Cosmos DB

95
New cards

Physical partitions

group of replicas of data physically stored on servers in Cosmos DB; automatically managed by Azure

96
New cards

SDKs

software development kits offered by Azure for working with different APIs to connect to Cosmos DB

97
New cards

Consistency level

configurable level in Cosmos DB for data replication across regions; affects the consistency of data

98
New cards

Strong consistency

level in Cosmos DB where read operations are guaranteed to return the latest committed write, offering a linearizability guarantee

99
New cards

Bounded Staleness

level in Cosmos DB where reads are guaranteed consistent within a preconfigured lag

100
New cards

Lag

Can consist of K (number of most recent versions) and T (a time interval)