How should I use these Troubleshooting practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Troubleshooting questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Troubleshooting domain.

JNCIA-DevOps · topic practice

Troubleshooting practice questions

Practise Juniper Networks Automation and DevOps, Associate (JNCIA-DevOps, JN0-224) (JNCIA-DevOps) Troubleshooting practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

5 questionsDomain: Troubleshooting

Practice 10 questions Browse domain →

What the exam tests

What to know about Troubleshooting

Troubleshooting questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Troubleshooting exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Troubleshooting questions

5 questions · select your answer, then reveal the explanation

Question 1hardmultiple choice

Read the full Troubleshooting explanation →

An engineer is troubleshooting a script that updates Junos configuration via the REST API. The payload is sent as JSON, but the device returns a 415 Unsupported Media Type error. What is the root cause?

Trap 1: The device is running out of memory buffers.

Resource exhaustion typically results in 503 Service Unavailable or 500 Internal Server Error.

Trap 2: The user account does not have permission to execute PUT requests.

Permission issues result in 403 Forbidden, not 415.

Trap 3: The target resource URI path does not exist on the device.

Non-existent resource URIs result in 404 Not Found.

Study all Troubleshooting common traps →

A
The device is running out of memory buffers.
Why wrong: Resource exhaustion typically results in 503 Service Unavailable or 500 Internal Server Error.
B
The user account does not have permission to execute PUT requests.
Why wrong: Permission issues result in 403 Forbidden, not 415.
C
The Content-Type header provided in the HTTP request is missing or specifies an unsupported media type.
415 Unsupported Media Type is explicitly caused by missing or invalid Content-Type headers.
D
The target resource URI path does not exist on the device.
Why wrong: Non-existent resource URIs result in 404 Not Found.

Full breakdown with real-world context →

Question 2hardmulti select

Read the full Troubleshooting explanation →

When troubleshooting REST API authentication and authorization on Junos devices, which THREE log files or diagnostic tools can an administrator inspect? (Choose three)

Trap 1: Kernel core dump files located in /var/crash/kernel.

Kernel core dumps are for kernel panics, not routine API auth troubleshooting.

Trap 2: BGP peer state packet captures in Wireshark.

BGP packet captures are irrelevant to REST authentication debugging.

Study all Troubleshooting common traps →

A
Kernel core dump files located in /var/crash/kernel.
Why wrong: Kernel core dumps are for kernel panics, not routine API auth troubleshooting.
B
HTTP response headers and status codes returned by the API client.
Response codes (401, 403) provide immediate clues regarding auth failures.
C
jpagent traceoptions log file (if configured under system services jpagent)
Traceoptions logs detailed API request processing and errors for jpagent.
D
BGP peer state packet captures in Wireshark.
Why wrong: BGP packet captures are irrelevant to REST authentication debugging.
E
/var/log/messages system log file for daemon startup and authentication events.
System logs record daemon initialization and login events.

Full breakdown with real-world context →

Question 3mediummultiple choice

Read the full REST/YANG explanation →

You are troubleshooting a NETCONF session where the client sent an improperly formatted XML payload. Where would you expect to find detailed error logging related to this malformed XML request on the Junos device?

Trap 1: /var/log/netconf.log

Default system logs do not automatically create a netconf.log file unless traceoptions are explicitly configured.

Trap 2: /var/db/config/juniper.conf.gz

This is the configuration archive path, not a log file.

Trap 3: /etc/netconf/errors.xml

Junos does not store NETCONF error logs in /etc/netconf/errors.xml.

Study all Troubleshooting common traps →

A
/var/log/netconf.log
Why wrong: Default system logs do not automatically create a netconf.log file unless traceoptions are explicitly configured.
B
/var/db/config/juniper.conf.gz
Why wrong: This is the configuration archive path, not a log file.
C
/etc/netconf/errors.xml
Why wrong: Junos does not store NETCONF error logs in /etc/netconf/errors.xml.
D
NETCONF traceoptions output file or /var/log/messages
NETCONF operational logs and parsing errors appear in traceoptions files or /var/log/messages.

Full breakdown with real-world context →

Question 4hardmultiple choice

Study the full Python automation breakdown →

During troubleshooting of a Python script using the ncclient library to interact with a Junos device, an automation engineer observes a 'rpc-error' response containing an error-tag of 'operation-failed'. Upon examining the Junos system logs, it is discovered that the candidate configuration had syntax errors introduced by an uncommitted previous session. Which NETCONF capability negotiation mechanism ensures that the client is aware of the exact XML schema constraints before sending the RPC?

Trap 1: The <get-schema> RPC operation defined in RFC 6020.

While <get-schema> retrieves specific YANG modules, it is executed after the hello message exchange and is not the primary capability negotiation mechanism.

Trap 2: The automatic download of Junos PyEZ schema definitions during the…

Junos PyEZ operates on top of NETCONF but does not fetch schemas during the SSH handshake.

Trap 3: The automated execution of a pre-flight XML validation check via…

<validate> checks configuration correctness but does not negotiate schema capabilities during session establishment.

Study all Troubleshooting common traps →

A
The <get-schema> RPC operation defined in RFC 6020.
Why wrong: While <get-schema> retrieves specific YANG modules, it is executed after the hello message exchange and is not the primary capability negotiation mechanism.
B
The automatic download of Junos PyEZ schema definitions during the SSH handshake phase.
Why wrong: Junos PyEZ operates on top of NETCONF but does not fetch schemas during the SSH handshake.
C
NETCONF capability URIs exchanged during the initial hello message exchange.
Clients and servers advertise supported models and schema namespaces via capability URIs in the initial hello messages.
D
The automated execution of a pre-flight XML validation check via the <validate> RPC.
Why wrong: <validate> checks configuration correctness but does not negotiate schema capabilities during session establishment.

Full breakdown with real-world context →

Question 5hardmulti select

Read the full Troubleshooting explanation →

When troubleshooting Junos REST API integration issues, which THREE factors should an engineer examine if API requests return connection timeouts or refused errors? (Choose three)

Trap 1: Whether the BGP routing table has valid routes to external BGP…

BGP reachability does not directly cause API connection timeouts to the local management daemon.

Trap 2: Whether the NETCONF subsystem script is properly compiled in Python…

NETCONF and Python version are unrelated to REST API daemon socket connection failures.

Study all Troubleshooting common traps →

A
Whether firewall filters or security zones permit traffic to TCP port 3000 or 3443.
Firewall filters protecting the Routing Engine can block REST API ports.
B
Whether the BGP routing table has valid routes to external BGP peers.
Why wrong: BGP reachability does not directly cause API connection timeouts to the local management daemon.
C
Network reachability and IP connectivity between the client and the Junos management interface (fxp0 or RE loopback).
Basic IP reachability is required for HTTP/HTTPS socket establishment.
D
Whether the jpagent service is configured and active on the Junos device.
If jpagent is disabled, the device will not listen on ports 3000/3443.
E
Whether the NETCONF subsystem script is properly compiled in Python 2.7.
Why wrong: NETCONF and Python version are unrelated to REST API daemon socket connection failures.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Troubleshooting sessions

Start a Troubleshooting only practice session

Every question in these sessions is drawn from the Troubleshooting domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Troubleshooting questions →Mixed JNCIA-DevOps session

Frequently asked questions

What does the JNCIA-DevOps exam test about Troubleshooting?: Troubleshooting questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Troubleshooting questions in a focused session?: Yes — the session launcher on this page draws every question from the Troubleshooting domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other JNCIA-DevOps topics?: Use the topic links above to move to related areas, or go back to the JNCIA-DevOps question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the JNCIA-DevOps exam covers. They are not copied from any real exam or dump site.

Troubleshooting only

10 questions 20 questions 30 questions 50 questions

Mixed JNCIA-DevOps session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All JNCIA-DevOps questions Troubleshooting domain overview JNCIA-DevOps exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Troubleshooting practice questions

What to know about Troubleshooting

Common Troubleshooting exam traps

Troubleshooting questions

An engineer is troubleshooting a script that updates Junos configuration via the REST API. The payload is sent as JSON, but the device returns a 415 Unsupported Media Type error. What is the root cause?

When troubleshooting REST API authentication and authorization on Junos devices, which THREE log files or diagnostic tools can an administrator inspect? (Choose three)

You are troubleshooting a NETCONF session where the client sent an improperly formatted XML payload. Where would you expect to find detailed error logging related to this malformed XML request on the Junos device?

When troubleshooting Junos REST API integration issues, which THREE factors should an engineer examine if API requests return connection timeouts or refused errors? (Choose three)

Track your progress over time

Start a Troubleshooting only practice session

Related JNCIA-DevOps topic practice pages

Python And PyEZ practice questions

Junos Automation Stack And DevOps Concepts practice questions

Data Serialization practice questions

NETCONF And XML API practice questions

Junos REST API practice questions

JNCIA-DevOps fundamentals practice questions

JNCIA-DevOps scenario practice questions

JNCIA-DevOps troubleshooting practice questions

Frequently asked questions

Track your progress

Study resources

Exam traps to avoid