MENU
How can the debug log for a playbook execution be viewed?
Suggested Answer: A
Get Premium SPLK-2003 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
42 comments · newest first
WA
Wai
11 months ago
B is incorrect, it’s not about expanding the scope.
CA
Catina
11 months ago
Definitely A, that's the easiest way!
RE
Refugia
11 months ago
Wait, is it really in the Visual Playbook Editor? That seems odd.
RA
Raul
11 months ago
I always use the Playbook Run History for logs.
VI
Vincenza
12 months ago
You can find the debug log in the Recent Activity panel.
IL
Ilene
12 months ago
I’m pretty confident about option A, but I also have a nagging feeling that option C might be correct too. I guess I’ll have to choose!
KA
Katina
12 months ago
I feel like I saw something about opening the playbook in the Visual Playbook Editor, but I can't recall if that was for logs or something else.
HA
Harrison
1 year ago
I remember practicing a question about viewing logs, and I think it was related to the Administration section. Maybe it's option C?
BR
Brinda
1 year ago
I think the debug log can be accessed from the Investigation page, but I'm not entirely sure if it's the action menu or somewhere else.
GL
Glory
1 year ago
Hmm, I'm not sure if that's the best approach. The question mentions using JsonPath, so I might try that instead to get a more targeted output.
KA
Kaycee
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully review the information provided and think through the options.
RE
Reuben
1 year ago
This seems like a straightforward question about social media marketing strategies for a book publisher. I think option A, posting author interview videos with buy now links, could be a good way to drive sales directly from social media.
MI
Miriam
1 year ago
Wait, I'm confused. I thought the vManage API was more for managing the certificates on the Cisco devices themselves, not distributing them to clients. Let me re-read the question and options again.
JE
Jennifer
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully review the options and think through which tasks can be automated using the Regression suite automation tool.
LE
Lenna
1 year ago
I'm just happy I don't have to use a ouija board to find the debug logs. C is the way to go!
AD
Adelle
1 year ago
Yeah, no need for any mystical methods with C option available!
TE
Teddy
1 year ago
I always go straight to Administration > System Health > Playbook Run History to check the debug logs.
JE
Jennie
1 year ago
I agree, C is definitely the easiest way to view the debug log.
RO
Roxanne
1 year ago
Ah, the debug log, the bane of every automation engineer's existence. At least we have options to view it, unlike the old days when we had to stare at the command line and hope for the best.
MA
Marsha
1 year ago
D) Open the playbook in the Visual Playbook Editor, and select Debug Logs in Settings.
MI
Mitzie
1 year ago
B) Click Expand Scope in the debug window.
MI
Miss
1 year ago
C) In Administration > System Health > Playbook Run History, select the playbook execution entry, then select Log.
WI
William
1 year ago
A) On the Investigation page, select Debug Log from the playbook's action menu in the Recent Activity panel.
HE
Hermila
1 year ago
D) Open the playbook in the Visual Playbook Editor, and select Debug Logs in Settings.
OW
Owen
1 year ago
B) Click Expand Scope in the debug window.
MA
Mattie
1 year ago
C) In Administration > System Health > Playbook Run History, select the playbook execution entry, then select Log.
NI
Nida
1 year ago
A) On the Investigation page, select Debug Log from the playbook's action menu in the Recent Activity panel.
RE
Reynalda
1 year ago
Option D sounds interesting, but I don't want to have to open the Visual Playbook Editor just to check the logs. C seems like the most straightforward approach.
HO
Honey
1 year ago
Yeah, I prefer the straightforward approach of going to Administration > System Health > Playbook Run History to check the logs.
KA
Kayleigh
1 year ago
I agree, option C seems like the easiest way to view the debug log.
GI
Gilberto
1 year ago
That's correct! Another option is to open the playbook in the Visual Playbook Editor and select Debug Logs in Settings.
AR
Ardella
1 year ago
I believe you can also view the debug log by selecting Log in Administration > System Health > Playbook Run History.
GI
Gilberto
1 year ago
I think the debug log can be viewed by selecting Debug Log from the playbook's action menu in the Recent Activity panel.
NO
Norah
1 year ago
I prefer checking the debug log in Administration > System Health > Playbook Run History. It's more organized and easier to find.
TH
Thaddeus
2 years ago
I'm not sure about the debug log. Is there a way to enable it for all playbook runs by default?
ST
Stephen
2 years ago
I agree with Matthew. That option seems the most straightforward and efficient.
WI
Winifred
2 years ago
I think the correct answer is C. The playbook run history page allows you to view the debug log for a specific playbook execution.
JO
Jonelle
1 year ago
D) Open the playbook in the Visual Playbook Editor, and select Debug Logs in Settings.
TO
Toshia
1 year ago
C) In Administration > System Health > Playbook Run History, select the playbook execution entry, then select Log.
ST
Stevie
1 year ago
B) Click Expand Scope in the debug window.
KE
Keva
1 year ago
A) On the Investigation page, select Debug Log from the playbook's action menu in the Recent Activity panel.
MA
Matthew
2 years ago
I think the debug log can be viewed by selecting Debug Log from the playbook's action menu in the Recent Activity panel.