A batch job retrieving wireless health for city branch IDs receives HTTP 404 for one identifier. What is the correct control flow for that resource hop?
Select an answer to reveal the explanation.
Short Explanation
A 404 says that address does not exist. Standing on the empty lot forever will not build the house. Close that item, log the ID, and move on if the batch allows skipping.
Full Explanation
HTTP 404 means the path or identifier does not exist; looping the same GET is not robust control flow. Under 2.2 the consumer stops that hop, logs the identifier, and continues only under a skip-item batch policy—not retry-forever. This is not a platform trivia question about DNA Center resources.