Level 4 exam — WinDev · GUIDINEE.COM

Exam — fresh questions

12 questions to validate level 4 with Yacine, a WinDev developer at an electrical equipment trading SME in Oran: HFSQL client/server, security and rights, advanced UX (internal windows, supercontrols, layouts), deployment and automatic update, automated tests and quality.
Answer everything, then click Check: your score and explanations will appear.

4 · Recall

1. What characterizes an HFSQL database in client/server mode?

Database processing is executed by a central HFSQL server, to which client workstations connect Each workstation has a complete copy of the data that it then synchronizes with the others The database is a simple file shared on a network drive, with no dedicated service The data is stored in the client workstation's browser and sent on demand

In client/server mode, the HFSQL server centralizes the data and executes processing; client workstations connect to it. That is what distinguishes this mode from simple file sharing.

4 · Application

2. Yacine wants a salesperson to view customer records without being able to modify prices. What is the right approach?

Give them administrator rights, it is the simplest to manage Create a user in a group with limited rights (view customers, no write on prices) Share the administrator account between the salesperson and Yacine Disable security for the demonstration, then re-enable it

Apply least privilege: a named account attached to a group whose rights cover the real usage — view customers, without writing to prices.

4 · Arbitration

3. The application works on Yacine's workstation but fails at startup at the customer's site. What is the most likely cause?

The customer has an Internet connection that is too fast for the application The database contains too many records for a client workstation The WinDev framework and the necessary elements were not included in the installation The executable was generated in 64 bits, which prevents any installation

It is the classic incomplete deployment: the development workstation already contains the framework and native access, which masks their absence. A clean-machine test would have revealed it.

4 · Recall

4. What is a supercontrol in WinDev?

A modal window that blocks input until an answer is given A tab of the main window loaded on demand An input control whose value is mandatory A set of controls with their behavior, placed like a single reusable control

The supercontrol groups controls and their behavior into a reusable block — for example an address block placed in several screens.

4 · Application

5. Yacine must give a new assistant access to the application. What does he do?

He installs a copy of the database on her workstation so she can work locally He creates the user in the groupware/HFSQL and assigns her to a group whose rights match her role He gives her the administrator account password He disables user management to avoid blockages

Access is granted through a named account attached to a rights group suited to the role: it is traceable and revocable, unlike sharing an administrator account.

4 · Arbitration

6. Yacine has little time to test his trading application. Where does he start?

Unit tests on the business core: VAT, discounts, due dates Tests of the display of each window, one by one Manual verification of all screens before each delivery Writing tests for the least-used parts of the application

The best effort/benefit ratio goes to the business core: a wrong calculation is a serious and invisible defect. Then target edge cases, not total coverage.

4 · Recall

7. What does the principle of least privilege mean?

Give each user all rights to avoid blockages Reserve write rights for developers only Grant each user only the rights strictly necessary for their role Delete accounts as soon as a user changes department

Least privilege limits each account to the strict minimum: it reduces the surface for errors and compromise, and rights remain readable and revocable.

4 · Application

8. Before deploying an update that evolves the database structure, what does Yacine do first?

He sends the executable to users to save time He deletes the old data to start from a clean database He disables automatic update to avoid any rollback He backs up the data and tests the conversion on a representative copy

A structure evolution affects real data: prior backup, test on a copy, scheduling outside critical hours and rollback are essential.

4 · Arbitration

9. Salespeople consider order entry too slow. What approach does Yacine favor?

Add animations and a more modern theme to the screen Observe a real user, then simplify entry (tabbing, internal window, supercontrol) Multiply modal windows to guide step by step Reduce the amount of information displayed without asking users

Efficiency prevails over visual effect: observation reveals unnecessary gestures, then internal windows, supercontrols and tab order remove superfluous clicks.

4 · Recall

10. What is a regression?

A defect introduced into a part that used to work, following a modification A bug present since the first version of the application A slowdown caused by too large a volume of data An input error made by the user in the interface

A regression is the risk specific to maintenance: a modification breaks something that worked elsewhere. Replayable automated tests are precisely there to detect it.

4 · Application

11. A salesperson leaves the company. What does Yacine do with their account?

He leaves it active in case the salesperson comes back He renames it to the replacement's name so as not to lose the history He disables or deletes it and removes its access rights He simply changes its password and communicates it to the team

A departure must be accompanied by deactivating the account and removing rights: an orphan account is a forgotten entry point and distorts traceability.

4 · Arbitration

12. Yacine's application must be used by eight people simultaneously on shared data. What does he conclude?

Stay on a single workstation and copy the database to a USB key every evening Share the database file on a network drive, without a dedicated server Have each person work on their own local database, then merge manually Switch to client/server: the HFSQL server centralizes the data and handles concurrent access

With several workstations on shared data, client/server is required: it centralizes processing, handles concurrent access and secures the data, where the shared file becomes risky.

What's next?

Score = 80%: you have mastered level 4 — HFSQL client/server, security and rights, advanced UX, deployment and tests. Consolidate by applying each 48h challenge to your own application.
Score between 50% and 80%: go back over the section(s) you failed (4.1 HFSQL client/server, 4.2 security and rights, 4.3 advanced UX, 4.4 deployment, 4.5 tests), reread the course, then take the test again.
Score < 50%: reread the whole of level 4 while applying each 48h challenge (install an HFSQL server, define rights, modernize a screen, deploy on a clean machine, write tests) before trying again.
And afterwards? Keep your practices: a well-administered HFSQL server, least-privilege rights, efficient screens, a deployment tested on a clean machine and a suite of automated tests — these are the foundations of a durable professional application.