H13-311_V3.5 · Question #361
Which of the following options is not the- session mode used by Tensorflow?
The correct answer is D. Multiple POST queries. Option D describes an HTTP web protocol concept, not a TensorFlow execution mechanism - "Multiple POST queries" has no relevance to how TensorFlow manages computational graph sessions, making it the clear outlier. Options A, B, and C are all legitimate TensorFlow 1.x session…
Question
Which of the following options is not the- session mode used by Tensorflow?
Options
- AExplicitly call the session to generate function
- BExplicitly call the session to close function
- CThrough the Python context manager
- DMultiple POST queries
How the community answered
(33 responses)- A9% (3)
- B3% (1)
- C6% (2)
- D82% (27)
Explanation
Option D describes an HTTP web protocol concept, not a TensorFlow execution mechanism - "Multiple POST queries" has no relevance to how TensorFlow manages computational graph sessions, making it the clear outlier.
Options A, B, and C are all legitimate TensorFlow 1.x session patterns. Explicitly calling sess.run() (A) executes operations in the graph. Explicitly calling sess.close() (B) is how you release session resources when managing the session lifecycle manually. Using a Python context manager (C) - with tf.Session() as sess: - automatically handles both opening and closing, making it the cleaner and more Pythonic approach.
Memory tip: Think of TensorFlow sessions like file I/O - you can open and close a file manually, or use with open(...) as a context manager. "Multiple POST queries" belongs to REST APIs, not TensorFlow, so it's the one that clearly doesn't fit.
Topics
Community Discussion
No community discussion yet for this question.