Deal of The Day! 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

Salesforce OMS-435 Exam - Topic 9 Question 57 Discussion

Actual exam question for Salesforce's OMS-435 exam
Question #: 57
Topic #: 9
[All OMS-435 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: C, D

by Rory at Sep 13, 2024, 07:23 AM

Limited Time Offer

25%

Off

Get Premium OMS-435 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Elbert
4 months ago
I love the idea of using a conditional state, super clean!
upvoted 0 times
...
Micheal
4 months ago
Wait, can the collapsible property really handle all that info?
upvoted 0 times
...
Linwood
4 months ago
A datatable won't work here, too cluttered!
upvoted 0 times
...
Bette
5 months ago
I disagree, D seems more flexible for user needs.
upvoted 0 times
...
Reyes
5 months ago
I think option C is the way to go.
upvoted 0 times
...
Wai
5 months 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.
upvoted 0 times
...
Louvenia
5 months 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.
upvoted 0 times
...
Noe
5 months ago
I remember practicing a question about displaying additional info on demand, and I think using a conditional FlexCard State could work well here.
upvoted 0 times
...
Raymon
6 months 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.
upvoted 0 times
...
Denae
6 months 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.
upvoted 0 times
...
Stephanie
6 months 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.
upvoted 0 times
...
Brandon
6 months 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.
upvoted 0 times
...
Rosina
6 months 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.
upvoted 0 times
...
Vivan
6 months 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.
upvoted 0 times
...
Azzie
6 months 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.
upvoted 0 times
...
Chaya
11 months ago
Collapsible property? What is this, the dark ages? FlexCard State is the way to go, my dude. Keep up with the times!
upvoted 0 times
Armando
10 months ago
Collapsible property is outdated, FlexCard State is more modern and user-friendly.
upvoted 0 times
...
Veda
10 months ago
I agree, using a conditional FlexCard State is the best approach for this scenario.
upvoted 0 times
...
Noemi
10 months ago
FlexCard State is definitely the way to go for displaying the contact information.
upvoted 0 times
...
...
Hayley
11 months 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!
upvoted 0 times
William
11 months ago
Yeah, using a conditional FlexCard State is much more modern and user-friendly.
upvoted 0 times
...
Fidelia
11 months ago
FlexCard State is definitely the way to go for displaying contact information.
upvoted 0 times
...
...
Letha
12 months 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.
upvoted 0 times
Avery
10 months ago
I like the idea of only showing the contact information when needed, it keeps the layout clean.
upvoted 0 times
...
Ammie
10 months ago
The conditional FlexCard State sounds like the best option for this scenario.
upvoted 0 times
...
Tyra
11 months ago
I think setting the collapsible property on the block element would be a good way to handle the contact information.
upvoted 0 times
...
Hester
11 months ago
I agree, using a Datatable might make it look too rigid.
upvoted 0 times
...
...
Deja
12 months 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.
upvoted 0 times
...
Dorothy
12 months ago
I'm not sure about that. Wouldn't setting the collapsible property on the block element also work well for this situation?
upvoted 0 times
...
Josephine
12 months ago
I agree with Melissia. Using a conditional FlexCard State seems like the best approach for this scenario.
upvoted 0 times
...
Melissia
12 months ago
I think the developer should use a conditional FlexCard State to display the contact information only when needed.
upvoted 0 times
...

Save Cancel