Level 5 exam — WinDev · GUIDINEE.COM

Exam — fresh questions

12 questions to validate level 5 with Yacine, a WinDev developer in an electrical equipment trading SME in Oran: WEBDEV, WinDev Mobile, REST APIs, GDS and progression/certification.
Answer everything, then click Check: your score and explanations will appear.

5 · Recall

1. In a WEBDEV project of Yacine's, where should stock be checked before saving an order?

On the server side, because the browser is visible and can be modified In browser code, to display the error faster In the HTML form, even before the data is sent In a stylesheet, to block invalid quantities

The browser is visible and modifiable: stock, price and rights are checked on the server side, the only safe place and the only one with access to the data.

5 · Recall

2. What is the main benefit of WinDev Mobile for Yacine's team?

It requires rewriting the entire application in native language It reuses WLangage and the analysis to target Android and iOS It removes the need to plan offline operation It guarantees that the stores publish the application without review

WinDev Mobile shares WLangage and the analysis with WinDev: Yacine extends his application to Android and iOS without learning two native developments.

5 · Recall

3. What does idempotence mean in a REST API exchange?

The service responds faster when the network is good The authentication token changes on each call sent The same repeated send does not create a duplicate at the recipient Received data is automatically validated by the server

With a unique operation identifier, a send replayed after an outage is recognized as already processed: recovery does not create a duplicate.

5 · Recall

4. What does the GDS keep on each check-in of an element?

A copy of each developer's entire hard drive Only the latest version, with no earlier trace The passwords of the application's users The change history: who, what and when

The GDS keeps the full history of check-ins, with comments, which allows a decision to be understood and a rollback to be made.

5 · Application

5. Yacine shares the WinDev analysis with his WEBDEV portal. What must he redo on the web side?

Nothing: the desktop application's checks apply as-is Validate prices, stock and rights again in server code Move all checks into the browser to lighten the server Remove the session, because the web keeps context automatically

Sharing the analysis reuses the data model, not security: critical checks must be redone in the portal's server code.

5 · Application

6. One of Yacine's technicians enters a reading in a warehouse with no network. What does the application do?

It refuses the entry and asks them to return to a covered area It sends the entry directly without checking the connection It saves locally then synchronizes when the network returns It erases the reading as soon as the connection is restored

Offline mode saves the reading in the local database with a synchronization indicator, then the queue is replayed when the network returns.

5 · Application

7. Yacine's supplier API responds with a price of zero. What reflex should be adopted?

Save the price as-is, because a partner API is always authoritative Display the error on screen without logging the exchange at all Retry indefinitely with no limit or queue Reject the response, log the exchange and inform the user

An inconsistent response is rejected: the data is validated, the exchange is logged for diagnosis and the user is informed without saving a wrong price.

5 · Application

8. Yacine wants to check a modified procedure back into the GDS. What does he do first?

He tests it and writes a comment describing the change He checks it out again to block the other developers He modifies the analysis directly without warning his team He deletes the history to start from a clean base

Before checking in, you test so as not to break the shared project and comment precisely on what changed and why.

5 · Arbitration

9. Yacine hesitates to check a price in the browser for immediate feedback. What does he decide?

He removes all validation so as not to slow the page down He moves the check into the page's CSS He keeps browser-side convenience but validates the price on the server side He entrusts the check to the hosting provider

Browser-side convenience is acceptable, but the validation that matters remains on the server side: the browser never protects a price.

5 · Arbitration

10. Yacine must extend his management system into the field. What scope should he choose for the mobile application?

Copy every management screen so nothing is forgotten Reduce the application to a simple login screen Remove the business procedures to lighten the phone A few useful field tasks: scan, inventory, delivery note

Mobile is a different use: a scope restricted to field actions is better than an unreadable copy of the entire desktop application.

5 · Arbitration

11. An order is sent twice to the API because of an outage. What does Yacine prioritize?

A unique operation identifier to make the send idempotent A new full send on each retry without an identifier Deleting the log to hide the duplicate Increasing the timeout without a queue

The unique operation identifier lets the recipient recognize a send already processed: recovery becomes idempotent, without duplicates.

5 · Arbitration

12. Yacine wants to invest in a PC SOFT certification. What is the right reflex?

Pay immediately the first price found on a forum Check the official terms and costs, and cultivate the fundamentals Give up practice for as long as it takes to memorize all the syntax Choose the most expensive certification to be sure of its value

Terms and prices vary by country and period: you check with the official source, without stopping practice or maintaining the fundamentals.

What's next?

Score ≥ 80%: you have mastered the web, mobile and API exchanges of level 5 — put these reflexes into practice on Yacine's management project.
Score between 50% and 80%: go back over the section(s) you missed (5.1 WEBDEV, 5.2 WinDev Mobile, 5.3 REST API, 5.4 GDS, 5.5 progression and certification), reread the course, then take the test again.
Score < 50%: reread the whole of level 5 while applying each 48h challenge (secure web portal, offline mobile application, logged API exchange, GDS cycle, progression plan) before trying again.
What next? Keep Yacine's reflexes: capitalize without transposing, secure on the server side, anticipate failures, version your sources and keep learning — that is what turns an application developer into a lasting professional.