File and project organization in Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why organize BI project files into folders?

Imagine you have many reports, dashboards, and data sources in one BI project. Why is it important to organize these files into folders?

A To find files quickly and avoid confusion when working with many items.

B Because folders make the project run faster when loading data.

C To reduce the file size of the project automatically.

D Because BI tools require folders to save any file.

💡 Hint

Think about how you find your documents on your computer.

Organizing files into folders helps users find and manage files easily, especially in large projects. It does not affect file size or tool requirements.

🎯 Scenario

intermediate

Best practice for naming BI report files

You have multiple reports for sales, finance, and marketing. Which naming style helps your team understand the file purpose quickly?

A Final, Draft, Old

B Report1, Report2, Report3

C 2024Q1, 2024Q2, 2024Q3

D Sales_Report_2024_Q1, Finance_Report_2024_Q1, Marketing_Report_2024_Q1

💡 Hint

Think about what information helps identify the report at a glance.

Clear and descriptive file names with category and date help team members find and understand files quickly.

❓ dax_lod_result

advanced

Calculate total sales ignoring filters on Region

Given a Sales table with columns Region and SalesAmount, which DAX measure calculates total sales ignoring any filters on Region?

Figma

Measure = CALCULATE(SUM(Sales[SalesAmount]), ALL(Sales[Region]))

A SUM(Sales[SalesAmount])

B CALCULATE(SUM(Sales[SalesAmount]), ALL(Sales[Region]))

C SUMX(VALUES(Sales[Region]), Sales[SalesAmount])

D CALCULATE(SUM(Sales[SalesAmount]), FILTER(Sales, Sales[Region] = "East"))

💡 Hint

Think about how to remove filters on a specific column.

ALL(Sales[Region]) removes filters on Region, so the measure sums all sales regardless of Region filters.

❓ visualization

advanced

Choose the best visualization for comparing sales trends by product category

You want to show how sales change over time for different product categories. Which visualization is best?

A Line chart with time on X-axis and sales on Y-axis, lines colored by product category.

B Pie chart showing total sales per product category.

C Stacked bar chart showing sales per product category for a single month.

D Scatter plot with sales on X-axis and product category on Y-axis.

💡 Hint

Think about how to show changes over time for multiple groups.

Line charts are best for showing trends over time. Coloring lines by category allows easy comparison.

🔧 Formula Fix

expert

Identify the error in this DAX measure for average sales per customer

Given a Sales table with CustomerID and SalesAmount, what error does this measure cause?

AvgSalesPerCustomer = AVERAGE(Sales[SalesAmount]) / DISTINCTCOUNT(Sales[CustomerID])

Figma

AvgSalesPerCustomer = AVERAGE(Sales[SalesAmount]) / DISTINCTCOUNT(Sales[CustomerID])

A It causes a syntax error because DISTINCTCOUNT cannot be used in division.

B It returns the correct average sales per customer.

C It returns an incorrect average because it divides average sales by distinct customers instead of total sales by customers.

D It causes a runtime error due to division by zero.

💡 Hint

Think about what the formula calculates step by step.

The formula divides average sales by distinct customers, which is not the average sales per customer. The correct approach is total sales divided by distinct customers.

Practice

1. Why is it important to organize Figma files into folders within a project?

easy

A. To hide files from team members

B. To increase the file size

C. To make files load slower

D. To find and manage files easily later

Solution

1. Step 1: Understand folder purpose in Figma

   Folders group related files so you can find them quickly without searching everywhere.

2. Step 2: Consider file management benefits

   Organized folders reduce confusion and save time when working on projects.

3. Final Answer:

   To find and manage files easily later -> Option D

4. Quick Check:

   Organizing files = Easy access [OK]

Hint: Folders help you find files fast, like folders on your computer [OK]

Common Mistakes:

• Thinking folders slow down Figma
• Believing folders hide files from others
• Confusing folders with file size changes

2. Which of the following is the correct way to name Figma files for version control?

easy

A. ProjectName_v1, ProjectName_v2, ProjectName_final

B. FinalProject, FinalProject2, FinalProject3

C. MyFile, MyFileCopy, MyFileCopy2

D. Design1, Design2, Design3

Solution

1. Step 1: Identify clear version naming

   Using _v1, _v2, etc., clearly shows file versions in order.

2. Step 2: Compare other options

   Other names like 'FinalProject' or 'Copy' are vague and confusing for version tracking.

3. Final Answer:

   ProjectName_v1, ProjectName_v2, ProjectName_final -> Option A

4. Quick Check:

   Consistent version names = ProjectName_v1, ProjectName_v2, ProjectName_final [OK]

Hint: Use _v1, _v2 to track versions clearly [OK]

Common Mistakes:

• Using vague names like 'Copy' or 'Final'
• Skipping version numbers
• Mixing unrelated file names

3. Given a Figma project with folders named 'Assets', 'Designs', and 'Docs', where should you place a new icon file and why?

medium

A. In 'Docs' because icons need documentation

B. In 'Designs' because icons are part of the design files

C. In 'Assets' because icons are reusable elements

D. In the root project folder to keep it simple

Solution

1. Step 1: Understand folder roles

   'Assets' holds reusable elements like icons; 'Designs' holds working design files; 'Docs' holds documentation.

2. Step 2: Match icon file to folder

   Icons are reusable assets, so they belong in 'Assets' for easy reuse across projects.

3. Final Answer:

   In 'Assets' because icons are reusable elements -> Option C

4. Quick Check:

   Reusable elements go in Assets [OK]

Hint: Put reusable items like icons in Assets folder [OK]

Common Mistakes:

• Putting icons in Docs folder
• Mixing assets with design files
• Leaving files in root folder

4. You notice your Figma project has files named inconsistently like 'DesignFinal', 'design_v2', and 'Design copy'. What is the best way to fix this?

medium

A. Rename files using a consistent pattern like ProjectName_v1, ProjectName_v2

B. Delete all files and start over

C. Leave files as they are to avoid confusion

D. Merge all files into one big file

Solution

1. Step 1: Identify problem with inconsistent naming

   Inconsistent names make it hard to track versions and progress.

2. Step 2: Apply consistent naming convention

   Renaming files with a clear pattern like ProjectName_v1 helps organize and find files easily.

3. Final Answer:

   Rename files using a consistent pattern like ProjectName_v1, ProjectName_v2 -> Option A

4. Quick Check:

   Consistent naming fixes confusion [OK]

Hint: Rename files with clear version numbers [OK]

Common Mistakes:

• Deleting files unnecessarily
• Ignoring inconsistent names
• Merging unrelated files

5. You manage a large Figma project with multiple teams. How should you organize files and folders to keep work clear and efficient?

hard

A. Put all files in one folder and name them randomly

B. Create separate folders for each team, use consistent file naming, and keep assets in a shared 'Assets' folder

C. Create folders only for assets and put all design files together without folders

D. Use different projects for each file instead of folders

Solution

1. Step 1: Organize by team folders

   Separate folders for each team help keep their work isolated and easy to find.

2. Step 2: Use consistent naming and shared assets

   Consistent file names avoid confusion; a shared 'Assets' folder allows reuse across teams.

3. Final Answer:

   Create separate folders for each team, use consistent file naming, and keep assets in a shared 'Assets' folder -> Option B

4. Quick Check:

   Team folders + consistent names + shared assets = Create separate folders for each team, use consistent file naming, and keep assets in a shared 'Assets' folder [OK]

Hint: Separate by team, name files clearly, share assets [OK]

Common Mistakes:

• Mixing all files in one folder
• Ignoring naming conventions
• Scattering assets across folders