Level 0 exam — harder

Exam — fresh questions

0.1 · Recall

1. What does Crystal Reports do with data?

Presentation tool: data stays at the source, the report is a refreshable template.
0.1 · Application

2. Farès produces the same sales statement every month. Which organisation?

Fixed presentation + up-to-date data: a template designed once, refreshed at will.
0.1 · Application

3. Farès must: (A) explore an exceptional variance, (B) produce 500 paginated invoices. How to split?

Free one-off analysis → Excel; fixed repeatable document → Crystal Reports.
0.2 · Recall

4. Which edition should Farès install to learn to design statements?

Standalone designer = design; for Visual Studio = .NET integration; Enterprise = mass distribution.
0.2 · Application

5. Farès is on Mac and wants to follow this guide. What should he do?

Windows-only designer: on Mac, Windows virtual machine, recent version (2020).
0.2 · Arbitration

6. A colleague says: “Let us take for Visual Studio, it is free so it equals the designer”. Farès’s verdict?

Each edition has its use: design (designer), integrate (Visual Studio), distribute (Enterprise).
0.3 · Recall

7. Where does Farès place the grand total so it appears only once?

Details repeats per row; the Report Footer displays only once, at the end.
0.3 · Application

8. Farès put his title in Details: it repeats on every row. What to fix?

The section decides frequency: single title → Report Header, check in Preview.
0.3 · Arbitration

9. Farès builds everything in Design without ever opening Preview. Verdict?

Normal loop: build in Design, check with data in Preview, fix, recheck.
0.4 · Application

10. Farès links Customers and Orders. What is the join based on?

No link on a common field: duplicates, missing rows or cartesian product.
0.4 · Application

11. Farès’s revenue looks doubled after the join. First reflex?

Join errors are silent: cross-check totals before distributing.
0.4 · Arbitration

12. Connection impossible: “source not found” via ODBC. Where does Farès start?

No. 1 cause of ODBC failures: 32/64-bit mismatch between software and driver — exact message first.
What's next?
Back to the guideGuide contents