Performance as a Self-Service Flashcards

1
Q

6 parameters for the load test

A
  • SERVER URL - The domain of the service.
  • SERVER_PORT - The port of the service.
  • CHECK_PATH - The endpoint to send the requests to.
  • DT_LTN - The Load Test Name uniquely identifies a test execution.
  • VUCount - The number of virtual users
  • LoopCount - The number of loops each virtual user performs.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

what does the x-dynatrace-test header contain

A

list of key-value pairs

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

what are the keys of the x-dynatrace-test header?

A
  • VU - Virtual User ID of the unique user who sent the request.
  • TSN - Test Step Name a logical test step within your load testing script (for example, Login or Add to cart.
  • LSN - Load Script Name - name of the load testing script. This groups a set of test steps that make up a multi-step transaction (for example, an online purchase)
  • LTN • The Load Test Name uniquely identifies a test execution (for example, 6h Load Test - June 25)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

how is the load testing tool named?

A

jmeter

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

recreate

A
  • version A is shutdown and version B is rolled out
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

recreate PRO

A
  1. app state renewed

2. easy to do

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

recreate NEG

A
  1. Downtime => users affected
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

ramped

A
  • rollout version B which slowly replaces version A instances
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

ramped PRO

A
  1. easy to do

2. new version is slowly released

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

ramped NEG

A
  1. No control over traffic

2. rollout can take time

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

blue/green

A
  • version B is released with version A

- traffic is switched to green at the load balancer

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

blue/green PRO

A
  1. no version conflict

2. instant rollout/rollback

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

blue/green NEG

A
  1. Long transactions

2. Not good with stateful apps

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

canary

A
  • gradually shifting from A to B

- control over traffic

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

canary PRO

A
  1. Easy rollout/rollback

2. New version released to a subset

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

canary NEG

A
  1. Not good with stateful apps

2. Slow

17
Q

A/B

A
  • shift from A to B based on criteria
18
Q

A/B PRO

A
  1. full traffic control
19
Q

A/B NEG

A
  1. Hard to troubleshoot
20
Q

Shadow

A
  • deploy version B with version A

- shadow traffic from A to B

21
Q

Shadow PRO

A
  • testing B under real conditions

- easy rollout

22
Q

Shadow NEG

A
  • costly (double the resources)

- not a true user test

23
Q

what is Istio used for?

A

service interaction management

24
Q

3 main components of Istio?

A
  1. Pilot
  2. Mixer
  3. Citadel
25
Q

Pilot

A

policy routing

26
Q

Mixer

A

policy enforcement

27
Q

Citadel

A

service to service authentication and encryption

28
Q

Gateway

A

load balancer receiving outgoing/incoming requests

29
Q

VirtualService

A

defines traffic routing rules when a host is addresed

30
Q

Destination rule

A

what policies to apply after routing

31
Q

Service Entry

A

used to define new services