300-415 · Question #294
How many concurrent sessions does a vManager REST API have before it invalidates the least recently used session if the maximum concurrent session number is reached?
The correct answer is C. 250. A vManage REST API will invalidate the least recently used session to make room for new requests if the maximum concurrent session limit of 250 is reached.
Question
Options
- A150
- B200
- C250
- D300
How the community answered
(44 responses)- A2% (1)
- B7% (3)
- C86% (38)
- D5% (2)
Why each option
A vManage REST API will invalidate the least recently used session to make room for new requests if the maximum concurrent session limit of 250 is reached.
The maximum number of concurrent REST API sessions for vManage is not 150; 250 is the documented default limit.
The maximum number of concurrent REST API sessions for vManage is not 200; 250 is the documented default limit.
Cisco vManage is designed to handle a maximum of 250 concurrent REST API sessions. If this limit is reached, vManage implements a Least Recently Used (LRU) algorithm to invalidate the oldest inactive session, thereby allowing new API requests to establish a session.
The maximum number of concurrent REST API sessions for vManage is not 300; 250 is the documented default limit.
Concept tested: vManage REST API session limits
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/sdwan-xe-gs-book_chapter_01.html
Topics
Community Discussion
No community discussion yet for this question.