Connect/Consume Azure services and 3rd-party services Flashcards

1
Q

What components are API Mangement made of?

A
  1. API gateway
  2. Management plane
  3. Developer portal
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What’s the API gateway?

A

an endpoint that
1. accepts API calls and route them to appropriate backends
2. verify API keys and other credentials presented w/reqs
3. caches responses to improve respone latency and minimize the load on backend services
4. Emits logs, metrics, and traces for monitoring, reporting and troubleshooting

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What’s the Management plane?

A

the administrative interface where you set up your API program

Use it to
1. Provision/Configure API Management servie settings
2. Define/Import API schema
3. Get insights from analytics
4. Manage users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What’s the Developer portal?

A

auto generated, customizable website w/ doc of your APIs.
You can
1. read API doc
2. Call an API via the ineractive console
3. Download API definitions
4. Access analytics on their own usage
5. Manage API keys

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are products in API Management?

A

products are how APIs are surfaced to developers.
Products have one or more APIs.
Configured with a title, description and terms of use.
Products can be open or protected (must be subscribed to use)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are groups in API Management?

A

Groups are used to manage the visibility of products to developers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the different groups in API Management?

A
  1. Administrators; Manage API Management service instances and create the APIs, operations, and products that are used by developers. Azure subscription administrators are members of this group
  2. Developers; Authenticated developer portal users that build applications using your APIs. Developers are granted access to the developer portal and build applications that call the operations of an API.
  3. Guests; Unauthenticated developer portal users. They can be granted certain read-only access, like the ability to view APIs but not call them
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What’s Managed gateways?

A

The managed gateway is the default gateway component that is deployed in Azure for every API Management instance in every service tier. With the managed gateway, all API traffic flows through Azure regardless of where backends implementing the APIs are hosted.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What’s self-hosted gateway?

A

The self-hosted gateway is an optional, containerized version of the default managed gateway. It’s useful for hybrid and multicloud scenarios where there’s a requirement to run the gateways off of Azure in the same environments where API backends are hosted. The self-hosted gateway enables customers with hybrid IT infrastructure to manage APIs hosted on-premises and across clouds from a single API Management service in Azure.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are the different API Management policies?

A
  1. Choose policy; applies enclosed policy statements based on the outcome of evaluation of boolean expressions, like if-then-else. <when></when> element
  2. Forward-request; forwards incoming req to backend service specified in the req context. follow-redirects attribute
  3. Return-response; aborts pipeline execution and returns either a default or custom response to the caller. Default response is 200 OK with no body.
  4. Limit concurrency; prevent enclosed policies from executing by more than the specified no of reqs at any time. When exceeding that number, new req fails immediately w/ 429 Too many Requests status code.
  5. Log to Event Hub; sends message in the specified format to an Event Hub defines by a Logger entity. save req for online/offline analysis.
  6. Mock response; to mock APIs and operations. Aborts normal pipeline execution and return mocked response.
  7. Retry; executes its child policies once and then retries their execution until the retry condition becomes false or retry count is exhausted.condition attribute
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is API Management Consumption Tier suited for?

A

microservice based architectures and event-driven systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What’s Azure Event Grid?

A

serverless event broker that u can use to integrate apps using events

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the 5 concepts in Azure Event Grid?

A
  1. Event; what happened
  2. Event sources; where the event took place
  3. Topics; the endpoint where publishers send events
  4. Event subscriptions; the endpoint/built-in mechanism to route events
  5. Event handlers; the app/service reacting to the event
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What two types of event schemas does Azure Event Grid support?

A
  1. Event Grid event schema
  2. Cloud event schema
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the built-in roles in Event Grid?

A
  1. Event Grid Subscription Reader
  2. Event Grid Subscription Contributor
  3. Event Grid Contributor
  4. Event Grid Sender
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What’s the role of Event Grid Subscription Reader?

A

read Event Grid event subscriptions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What’s the role of Event Grid Subscription Contributor?

A

manage Event Grid event subscription operations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What’s the role of Event Grid Contributor?

A

create and manage Event Grid resources

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What’s the role of Event Grid Data Sender?

A

send events to Event Grid topics

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What’s checkpointing?

A

a process by which an event processor marks/commits the position of the last successfully processed event within a partition.

21
Q

What’s a partition in Event Hub?

A

an ordered sequence of events that is held in an Event Hub.

22
Q

What’s Event Hubs producer?

A
23
Q

What’s Consumer group?

A
24
Q

What key components does Event Hubs contain?

A
  1. Event Hubs client; primary interface for developers interacting with the Event Hubs client library
  2. Event Hubs producer; type of client that serves as a source of telemetry data, diagnostics information, usage logs, etc.
  3. Event Hubs consumer; type of client that reads information from the Event Hubs and allows processing of it
  4. Partition; ordered sequence of events that is held in an Event Hubs.
  5. Consumer group; view of an entire Event Hubs
  6. Event receivers; Any entity that reads event data from an Event Hubs
  7. Throughout units/ processing units; Prepurchased units of capacity that control the throughput capacity of Event Hubs.
25
Q

When should you use Service Bus queues?

A

when your solution …
1. needs to receive messages without having to poll the queue.

  1. requires the queue to provide a guaranteed first-in-first-out(FIFO) ordered delivery.
  2. needs to support automatic duplicate detection
  3. you want ur app to process messages as parallel long-running streams (messages associated w/a stream using session ID)
  4. require transactional behaviour and atomicity when sending or receiving multiple messages from a queue.
  5. ur app handles messages that can exceed 64 KB but won’t approach the 256 KB limit.
26
Q

When should you consider using Storage queues?

A
  1. ur app must store over 80 GB of messages in a queue.
  2. ur app wants to track progress for processing a message in the queue. Useful if the worker processing a message crashes. Another worker can then use that information to continue from where the prior worker left off.
  3. you require server side logs of all of the transactions executed against your queues.
27
Q

Which Service Bus tier is recommended for production scenarious?

A

Premium tier cause address common customer requests around scale, performance and availability for mission-critical apps.

28
Q

What are the different Service Bus tiers?

A
  1. Premium
  2. Standard

almost identical but serve different use cases

29
Q

What are the differences between premium and standard Service Bus tier?

A

Premium; high throughput, predictable performance, fixed pricing, ability to scale workload up/down, message size up to 100MB

Standard; variable throughput, variable latency, pay as you go variable pricing, message size up to 256 KB

30
Q

What are the two different receive modes Service Bus receives messages?

A
  1. Receive and delete
  2. Peek lock
31
Q

What’s Receive and Delete mode in Service Bus?

A

It’s a receive message mode.
The Service Bus receives the request from the consumer, it marks the message as consumed and return it to the consumer app.

Works best for app that can tolerate missing messages (not processing a message if a failure occurs).

32
Q

What’s Peek lock receive mode in Service Bus?

A

The receive operation has two stages. Support apps that can’t tolerate missing messages.

  1. Finds the next message to be consumed, locks it to prevent other consumers from receiving it, and then, return the message to the application.
  2. After the application finishes processing the message, it requests the Service Bus service to complete the second stage of the receive process. Then, the service marks the message as consumed.

timeout with the lock. When timeout, message is unlocked and available to receive again.

33
Q

what’s Azure Queue Storage?

A

service for storing large numbers of messages.
Access anywhere via authenticated calls using HTTP/HTTPS.

34
Q

How big can a queue message be in Azure Queue Storage?

A

up to 64 KB in size.
A queue may contain millions of messages, up to the total capacity limit of a storage account

35
Q

What are the components Azure Queue Storage contain?

A
  1. URL format; Queues are addressable using the URL format https://<storage>.queue.core.windows.net/<queue>. For example, the following URL addresses a queue in the diagram above https://myaccount.queue.core.windows.net/images-to-download</queue></storage>
  2. Storage account
  3. Queue; A queue contains a set of messages. All messages must be in a queue. The queue name must be all lowercase.
  4. Message; A message, in any format, of up to 64 KB. For version 2017-07-29 or later, the maximum time-to-live can be any positive number, or -1 indicating that the message doesn’t expire. If this parameter is omitted, the default time-to-live is seven days.
36
Q

What’s the benefit of load leveling?

A

When producers send lots of messages to the consuming app, the consuming app only has to handle average load instead of peak load.

“So, when the producers send a lot of messages in a short time (peak load), the queue collects them patiently. The consumers can then take their time and process the messages at a steady, comfortable pace, handling an average amount of work.”

37
Q

You manage an Azure event hub.
You need to ensure that multiple load-balanced instances of a .NET application (version 5.0) can be used to scale event processing.

Which event processor client should you use?

A

EventProcessorClient balances the load between multiple instances of a program in newer .NET versions (version 5.0).

EventHubConsumerClient balances the load between multiple instances of a program in Python and JavaScript.

EventProcessorHost balances the load between multiple instances of a program in earlier .NET versions.
The EventHubProducerClient class is used to send events to an event hub.

38
Q

How can you scale your event processing apps?

A
  1. run multiple instances of the app and have it balance the load among themselves.

In old versions, EventProcessorHost allowed you to balance the load between multiple instances of your program and checkpoint events when receiving.

In the newer versions (5.0+), EventProcessorClient (.NET and Java) or EventHubConsumerClient (Python and JavaScript) allows you to do the same

39
Q

What are the different message routing you can do with Service Bus?

A
  1. Simple request/reply
  2. Multicast request/reply
  3. Multiplexing
  4. Multiplexed request/reply
40
Q

What’s the message routing Simple request/reply?

A

A publisher sends a message into a queue and expects a reply from the message consumer. The publisher owns a queue to receive the replies. The address of that queue is contained in the ReplyTo property of the outbound message. When the consumer responds, it copies the MessageId of the handled message into the CorrelationId property of the reply message and delivers the message to the destination indicated by the ReplyTo property.

One message can yield multiple replies, depending on the application context.

41
Q

What’s the message routing Multicast request/reply?

A

As a variation of the prior pattern, a publisher sends the message into a topic and multiple subscribers become eligible to consume the message. Each of the subscribers might respond in the fashion described previously. If ReplyTo points to a topic, such a set of discovery responses can be distributed to an audience.

42
Q

If you want to define policies to multiple scopes in Azure API Management, what element should you use to enforce a policy evaluation order?

A

The <base></base> element provides the ability to enforce policy evaluation order.

43
Q

Azure Event Hubs Capture enables you to auto deliver streaming data in Event Hubs. To which locations?

A

Azure Blob storage,
Azure Data Lake Storage Gen1 and Gen 2

44
Q

What’s Azure Event Hub?

A

a big-data streaming platform and event ingestion service (the process of importing large, assorted data files from multiple sources into a single, cloud-based storage medium).

One of the three types of message broker available on Azure.

45
Q

What are message broker?

A

Message brokers act as intermediaries between event producers (eg, mobile apps) and event consumers (eg. dashboards or data processing pipelines)

46
Q

What messaging broker services does Azure have?

A
  1. Azure Event Hubs; pull method
  2. Azure Service Bus; similar to Event Hubs. Designed for delivery of mission-critical commands for which a delivery guarantee is required.
  3. Azure Event Grid; push model -> follows a publisher-subscriber pattern. A source (eg. mobile app) triggers an event that is pushed to all subscribers, or is discarded if no subscribers exist.
47
Q

When is Event Hubs a suitable solution?

A

Ingesting high volumes of messages quickly and reliably. Suitable for receiving data from thousands+ event publishers simultaneously and ensuing the data is stored in a non-volatile state (doesn’t change rapidly).

48
Q

When is Event Hubs not the best solution?

A
  1. If the event creators are critically dependent on specific actions taking place in a specific window of time.
  2. When delivery of all info is absolutely business critical.
49
Q

How much is a single throughput unit for ingress and egress?

A

Ingress: Up to 1MB per second or 1000 events per second (whichever comes first)

Egress: Up to 2MB per second or 4096 events per second.