New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

OutSystems Architecture-Specialist-11 Exam - Topic 4 Question 32 Discussion

Actual exam question for OutSystems's Architecture-Specialist-11 exam
Question #: 32
Topic #: 4
[All Architecture-Specialist-11 Questions]

"Splitting UI elements per functionality" is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Sharmaine at Nov 14, 2024, 08:09 AM

Limited Time Offer

25%

Off

Get Premium Architecture-Specialist-11 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Jaclyn
3 months ago
Wait, CSS only in the theme module? That seems limiting!
upvoted 0 times
...
Moira
4 months ago
D is the way to go for modularity!
upvoted 0 times
...
Tien
4 months ago
C sounds right, but is it really that much better?
upvoted 0 times
...
Michell
4 months ago
I think E makes more sense for organization.
upvoted 0 times
...
Tricia
4 months ago
A is definitely a best practice!
upvoted 0 times
...
Angella
4 months ago
I vaguely remember something about screens and placeholders being a good practice, but I can't quite remember if that's true for this question.
upvoted 0 times
...
Rodney
5 months ago
I feel like the answer might be E, since we talked about keeping CSS centralized in the theme module during our last practice session.
upvoted 0 times
...
Reena
5 months ago
I think putting CSS in blocks might actually help with performance, but I can't recall if that's considered a best practice or not.
upvoted 0 times
...
Danica
5 months ago
I remember we discussed how splitting UI elements can improve maintainability, but I'm not sure which option is the odd one out here.
upvoted 0 times
...
Bettye
5 months ago
I'm pretty confident about this one. Option E, putting all CSS in the mobile theme module, is not a best practice. We want to keep CSS close to the UI elements it styles, not centralized in a single module.
upvoted 0 times
...
Mona
5 months ago
Okay, I've got this. Splitting UI elements by functionality is a best practice to avoid monolithic modules. The key is to group blocks into independent functional modules with their own lifecycles. That way, changes in one area don't impact the whole UI.
upvoted 0 times
...
Joni
5 months ago
Hmm, this is a tricky one. I'm not entirely sure about the difference between putting CSS in blocks vs. screens. I'll need to review my notes on modular UI design to make sure I choose the right answer.
upvoted 0 times
...
Mertie
5 months ago
This question seems to be testing our understanding of best practices for organizing mobile UI elements. I'll need to carefully read through the options and think about the pros and cons of each approach.
upvoted 0 times
...
Stefania
1 year ago
Wait, wait, wait. Option A with the 'Screens as layouts' thing? That's straight out of the UI design playbook. Gotta love it!
upvoted 0 times
...
Monte
1 year ago
I'm feeling a bit lost here. Is option B about including the Common flow and Menu artifacts really a 'best practice'? Seems kinda vague to me.
upvoted 0 times
Alex
1 year ago
C) Put CSS in blocks or screens. Allows better performance and seamless screen transitions
upvoted 0 times
...
Stacey
1 year ago
A) Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
upvoted 0 times
...
...
Joesph
1 year ago
Nah, I think option D is the way to go. Grouping blocks in functional modules with independent life cycles? That's the key to a clean, maintainable UI.
upvoted 0 times
Antione
1 year ago
User 3: I think we're all on the same page here, option D is the way to go for avoiding monolithic mobile UI modules.
upvoted 0 times
...
Dorsey
1 year ago
User 2: Absolutely, grouping blocks in functional modules with independent life cycles is crucial for a clean and maintainable UI.
upvoted 0 times
...
Dominque
1 year ago
User 1: I agree, option D is definitely the best practice for splitting UI elements.
upvoted 0 times
...
...
Shenika
1 year ago
I believe putting CSS in blocks or screens is not a best practice. It can lead to performance issues.
upvoted 0 times
...
Jess
1 year ago
Hold up, what about option C? Putting CSS in blocks or screens for better performance? Sounds legit to me.
upvoted 0 times
Norah
1 year ago
Talia: Oh, I see. Thanks for clarifying that!
upvoted 0 times
...
Talia
1 year ago
User 3: Eulah is correct. CSS should be centralized in the mobile theme module for better management.
upvoted 0 times
...
Eulah
1 year ago
User 2: Really? I thought putting CSS in blocks or screens was a good idea for better performance.
upvoted 0 times
...
Allene
1 year ago
User 1: Option C is actually not a best practice. CSS should only be placed in the mobile theme module.
upvoted 0 times
...
...
Lynna
1 year ago
I agree. It helps to keep the code organized and makes it easier to maintain.
upvoted 0 times
...
Han
1 year ago
Option E seems like a no-brainer, right? Putting all the CSS in one module is just asking for trouble.
upvoted 0 times
Rodrigo
1 year ago
User: Option E seems like a no-brainer, right? Putting all the CSS in one module is just asking for trouble.
upvoted 0 times
...
Elise
1 year ago
C) Put CSS in blocks or screens. Allows better performance and seamless screen transitions
upvoted 0 times
...
Willis
1 year ago
B) Include the Common flow and Menu artifacts
upvoted 0 times
...
Jin
1 year ago
A) Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
upvoted 0 times
...
...
Virgina
1 year ago
I think splitting UI elements per functionality is important for mobile UI design.
upvoted 0 times
...

Save Cancel