Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

SAP Exam C_FIORDEV_22 Topic 5 Question 32 Discussion

Actual exam question for SAP's C_FIORDEV_22 exam
Question #: 32
Topic #: 5
[All C_FIORDEV_22 Questions]

You develop an SAPUI5 app that updates dat on the SAP back-end system. What activities are required when you implement an XSRF token? Note: There are 2 correct answers to this question.

Show Suggested Answer Hide Answer
Suggested Answer: A, B

by Brandon at Feb 11, 2024, 08:25 AM

Limited Time Offer

25%

Off

Get Premium C_FIORDEV_22 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Elliot
12 months ago
I will stick with A) and C) as the correct answers for this question
upvoted 0 times
...
Rickie
12 months ago
I feel confident that A) and C) are the correct activities to ensure XSRF token implementation
upvoted 0 times
...
Tracey
12 months ago
I've read that D) Generate a token on each read and write request is not necessary for implementing an XSRF token
upvoted 0 times
...
Hoa
12 months ago
I'm not sure about that, I think B) Execute the Refresh method for an expired token might also be required
upvoted 0 times
...
Alex
1 years ago
I agree with you, those two activities are necessary to implement an XSRF token
upvoted 0 times
...
Ollie
1 years ago
I think the correct answers are A) Retrieve the token and send it with each write request and C) Include the token in the HTTP request body of each write request
upvoted 0 times
...
Alfred
1 years ago
I think A and C are the way to go here. Gotta keep those pesky XSRF attacks at bay by including the token in the request. Sounds like a pretty straightforward SAPUI5 implementation to me.
upvoted 0 times
...
Lizbeth
1 years ago
I believe option C is also correct, including the token in the HTTP request body makes sense.
upvoted 0 times
...
Nickie
1 years ago
B is a trap answer for sure. Refreshing an expired token? That's not how it works, you just need to retrieve the fresh token and send it with the request.
upvoted 0 times
Mila
1 years ago
C) Include the token in the HTTP request body of each write request
upvoted 0 times
...
Louvenia
1 years ago
A) Retrieve the token and send it with each write request
upvoted 0 times
...
...
Jerry
1 years ago
Haha, D is a classic - generate a new token for every read and write? That's just asking for trouble! Gotta love those XSRF token questions, they really separate the UI5 pros from the amateurs.
upvoted 0 times
Ahmed
12 months ago
C) Include the token in the HTTP request body of each write request
upvoted 0 times
...
Luis
12 months ago
A) Retrieve the token and send it with each write request
upvoted 0 times
...
Rosenda
12 months ago
Yeah, D does seem like a risky choice. It's important to handle those tokens carefully to avoid security issues.
upvoted 0 times
...
Royal
1 years ago
C) Include the token in the HTTP request body of each write request
upvoted 0 times
...
Leila
1 years ago
A) Retrieve the token and send it with each write request
upvoted 0 times
...
...
Vashti
1 years ago
A and C are definitely the correct answers. You need to retrieve the token and send it with each write request, and include the token in the HTTP request body. No need to refresh or generate a new token for each request.
upvoted 0 times
Rory
1 years ago
C) Include the token in the HTTP request body of each write request
upvoted 0 times
...
Gayla
1 years ago
A) Retrieve the token and send it with each write request
upvoted 0 times
...
Ronny
1 years ago
C) Include the token in the HTTP request body of each write request
upvoted 0 times
...
Ronny
1 years ago
A) Retrieve the token and send it with each write request
upvoted 0 times
...
...
German
1 years ago
I'm not sure about option D, generating a token on each request seems excessive.
upvoted 0 times
...
Kattie
1 years ago
I agree with Glendora, it's important to include the token in the request.
upvoted 0 times
...
Glendora
1 years ago
I think option A is correct, we need to retrieve and send the token with each write request.
upvoted 0 times
...

Save Cancel