MENU
A developer needs to display the following information together on one FlexCard:
* Account name, address, phone number, website
* Primary contact first name, contact name, address, phone number, email
The account information must always be visible, and the contact information should only be visible as needed by the user.
What approach should the developer use to display the contact information on the card?
Suggested Answer: C, D
Get Premium OMS-435 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
EL
Elbert
11 months ago
I love the idea of using a conditional state, super clean!
MI
Micheal
11 months ago
Wait, can the collapsible property really handle all that info?
LI
Linwood
12 months ago
A datatable won't work here, too cluttered!
BE
Bette
12 months ago
I disagree, D seems more flexible for user needs.
RE
Reyes
1 year ago
I think option C is the way to go.
WA
Wai
1 year ago
Using a Datatable seems like it would show too much info at once, so I’m leaning towards the collapsible option, but I need to double-check my notes.
LO
Louvenia
1 year ago
I’m a bit confused about the difference between the collapsible class and the collapsible property. I feel like I’ve seen both in practice questions.
NO
Noe
1 year ago
I remember practicing a question about displaying additional info on demand, and I think using a conditional FlexCard State could work well here.
RA
Raymon
1 year ago
I think the collapsible property on the block element might be the right choice, but I'm not entirely sure if it’s the same as setting a class.
DE
Denae
1 year ago
I'm leaning towards the collapsible block approach as well. It seems like the most intuitive way to keep the account info visible while allowing the user to expand the contact details as needed.
ST
Stephanie
1 year ago
The conditional FlexCard State option seems interesting, but I'm not sure if that's the most efficient way to handle this. I think the collapsible block is probably the cleanest and most straightforward solution.
BR
Brandon
1 year ago
A Datatable element seems like overkill for this simple use case. I'd go with the collapsible block approach - it should be easy to implement and give the user a nice way to toggle the contact info.
RO
Rosina
1 year ago
Hmm, I'm a bit unsure about this one. I'm not sure if the "collapsible" class is the right way to go, or if there's a more specific property I should be using. I'll have to think this through carefully.
VI
Vivan
1 year ago
This looks like a pretty straightforward question. I think using a collapsible block element would be the best approach to hide the contact information until the user needs it.
AZ
Azzie
1 year ago
This question seems pretty straightforward. The obvious answer is that having stakeholders from different countries would increase the complexity, since you'd have to navigate cultural differences and potentially language barriers. I'm confident I can get this one right.
CH
Chaya
2 years ago
Collapsible property? What is this, the dark ages? FlexCard State is the way to go, my dude. Keep up with the times!
AR
Armando
1 year ago
Collapsible property is outdated, FlexCard State is more modern and user-friendly.
VE
Veda
1 year ago
I agree, using a conditional FlexCard State is the best approach for this scenario.
NO
Noemi
1 year ago
FlexCard State is definitely the way to go for displaying the contact information.
HA
Hayley
2 years ago
Ha! Imagine trying to use the 'collapsible' class. That's so 2010. We're in the future now, gotta use that fancy schmancy FlexCard State!
WI
William
1 year ago
Yeah, using a conditional FlexCard State is much more modern and user-friendly.
FI
Fidelia
1 year ago
FlexCard State is definitely the way to go for displaying contact information.
LE
Letha
2 years ago
I was thinking about using a Datatable, but that would make the layout look too structured. The conditional FlexCard State is a much more elegant solution.
AV
Avery
1 year ago
I like the idea of only showing the contact information when needed, it keeps the layout clean.
AM
Ammie
1 year ago
The conditional FlexCard State sounds like the best option for this scenario.
TY
Tyra
1 year ago
I think setting the collapsible property on the block element would be a good way to handle the contact information.
HE
Hester
2 years ago
I agree, using a Datatable might make it look too rigid.
DE
Deja
2 years ago
Option D seems like the way to go. Using a conditional FlexCard State will allow the account info to always be visible while toggling the contact info on user interaction.
DO
Dorothy
2 years ago
I'm not sure about that. Wouldn't setting the collapsible property on the block element also work well for this situation?
JO
Josephine
2 years ago
I agree with Melissia. Using a conditional FlexCard State seems like the best approach for this scenario.
ME
Melissia
2 years ago
I think the developer should use a conditional FlexCard State to display the contact information only when needed.