Level 4 exam — Microsoft Teams & Outlook

Exam — fresh questions

14 questions to validate “Level 4 · Expert: Teams (files, apps & integrations)”: the fundamentals, the trade-offs and Nassim’s cases.
Answer everything, then click Check: your score and explanations will appear.
The questions cover sections 4.1 to 4.5.
Objective: 80% before moving to the next level.

4.1 · Recall

1. What is the advantage of posting a file in a channel rather than sending it as an attachment?

A single file, co-editable in real time and versioned (end of divergent versions) None He is prettier It weighs more

Co-editing deletes the “v3_final_VRAI.docx file”: a single team file, always up to date.

4.2 · Application

2. What is the purpose of adding a Planner tab to a channel?

To decorate To make tracking of team tasks (who/what/when) visible to everyone To chat To call

The tabs centralize the project's essentials: pivotal document, tasks (Planner), notes (OneNote).

4.3 · Application

3. What type of notification should ALWAYS be left active?

All reactions Every message from every channel The @personal mention (we call you by name) None

Personal mention has priority; the rest is filtered by channel (all/mentions/nothing) to preserve concentration.

4.4 · Application

4. How to collaborate with an external client on a meeting, securely?

Add it to the whole team Give him your password Send him all the files Invite their email to the meeting link (no access to the rest of the team)

Least privilege: the external joined by the link; for lasting collaboration, a shared (targeted) channel is better.

4.5 · Recall

5. What do Teams ↔ Outlook gateways allow?

Nothing Share an email in Teams, start a meeting from a chat — while keeping the context Delete emails Change account

The fluid flow: capture (email) → discuss (chat) → decide (meeting) → trace (channel), without copying and pasting.

4.1 · Application

6. What do we remember from the “Files & co-editing (SharePoint / OneDrive)” section?

The @personal mention is the only type to always notify; the rest is filtered by channel priority. The tabs centralize the project's essentials at the top of the channel: documents, tasks, notes, dashboards. Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it. Least privilege + validation in case of doubt: external collaboration follows security rules.

Section 4.1 emphasizes this point: Files in a channel = stored in SharePoint; personal files = OneDrive. Teams is a window on it.

4.2 · Application

7. What do we remember from the “Tabs, applications & integrations” section?

The version history makes any error reversible: co-edit without fear. Set notifications channel by channel: all / mentions / nothing depending on importance. Meeting with an external = his email invited to the link: no access to the rest of the team. Planner tab = tracking of team tasks visible to everyone (who/what/when).

Section 4.2 emphasizes this point: Planner tab = tracking of team tasks visible to everyone (who/what/when).

4.3 · Judgment

8. What do we remember from the “Manage notifications & settings” section?

Turning off the pop-up email alert and processing the inbox at set times protects concentration. Real-time co-editing removes divergent versions: one file, several authors. To collaborate sustainably: shared (targeted) or guest channel — at the minimum access level. Switching to oral (Meet Now) when writing gets bogged down saves a lot of time.

Section 4.3 emphasizes this point: Turning off the pop-up email alert and processing the mailbox at fixed times protects concentration.

4.4 · Application

9. What do we learn from the “Collaborate with the external (guests) & secure” section?

Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it. The @personal mention is the only type to always notify; the rest is filtered by channel priority. Least privilege + validation in case of doubt: external collaboration follows security rules. The tabs centralize the project's essentials at the top of the channel: documents, tasks, notes, dashboards.

Section 4.4 emphasizes this point: Least privilege + validation in case of doubt: external collaboration follows security rules.

4.5 · Judgment

10. What do we learn from the “Teams & Outlook together (workflow)” section?

What is pinned in a tab is accessible to ALL members: knowledge no longer depends on one person. The tabs centralize the project's essentials at the top of the channel: documents, tasks, notes, dashboards. Channel files = stored in SharePoint; personal files = OneDrive. Teams is a window on it. Teams and Outlook take turns: share an email to Teams, start a meeting from a chat, keep the link everywhere.

Section 4.5 emphasizes this point: Teams and Outlook take turns: share an email to Teams, start a meeting from a chat, keep the link everywhere.

4.1 · Recall

11. What concrete action should be taken for “Files & co-editing (SharePoint / OneDrive)”?

In a Teams channel, Files tab: drop (or create) a Word/Excel document. Add a OneNote tab for project reports and documentation. In a channel, click the + at the top (add tab): pin the project reference document. After the meeting: file the minutes in the channel Files tab (not as a loose attachment).

The practice in section 4.1 begins with: In a Teams channel, Files tab: drop (or create) a Word/Excel document.

4.2 · Judgment

12. How to answer the question "Can I add any application?"” ?

Yes: Do Not Disturb (3.5) hides notifications while still letting messages arrive. Combined with per-channel settings and silent times, this is your complete interruption mastery kit. The catalog is vast, but the organization can restrict the authorized apps (security). Stick to useful and validated integrations: the goal is to centralize work, not collect gadgets. According to the canal rights, yes — hence the importance of only sharing with him what he must see. For sensitive documents, we prefer targeted link sharing (with limited rights) rather than access to an entire channel. In the new integrated Outlook / Teams: “Share in Teams” button (or… → Share). The email (subject + content, possibly attachments) is posted in the chosen chat/channel, ready to be discussed.

The FAQ in section 4.2 answers: The catalog is vast, but the organization can restrict authorized apps (security). Stick to useful and validated integrations: the goal is to centralize work, not collect gadgets.

4.3 · Application

13. What concrete steps should I take to “Manage notifications & settings”?

For lasting collaboration: Assess the right level — a shared channel (targeted access) rather than a guest across the entire team, if possible. If you add a guest: check WHAT THEY VIEW (the team's channels and files) — don't leave anything confidential not intended for them. Apply least privilege: access to the common project, nothing beyond. If in doubt about sensitivity: confirm with IT/manager. Outlook: deactivate the pop-up alert for new emails (Settings → Notifications) and process the inbox at set times rather than continuously.

The practice in section 4.3 begins with: Outlook: disable the pop-up alert for new emails (Settings → Notifications) and process the mailbox at set times rather than continuously.

4.4 · Judgment

14. How to answer the question “Can a guest download our files?”” ?

The catalog is vast, but the organization can restrict the authorized apps (security). Stick to useful and validated integrations: the goal is to centralize work, not collect gadgets. Yes: Do Not Disturb (3.5) hides notifications while still letting messages arrive. Combined with per-channel settings and silent times, this is your complete interruption mastery kit. According to the canal rights, yes — hence the importance of only sharing with him what he must see. For sensitive documents, we prefer targeted link sharing (with limited rights) rather than access to an entire channel. In YOUR OneDrive (“Microsoft Teams Chat Files” folder), shared with chat participants. The channel files go to the team's SharePoint. Hence the interest in the canal for what must remain accessible to all.

The FAQ in section 4.4 answers: Depending on the channel's rights, yes — hence the importance of only sharing with it what it needs to see. For sensitive documents, we prefer targeted link sharing (with limited rights) rather than access to an entire channel.

What's next?

Reread the key points from level 4 before moving on to level 5.
Replay a Nassim case with your own messages and calendar.

Back to the guideGuide contents