Q1 Which of the following statements are true about page layouts?
- They can have one or two columns per section
- We can add a list button using a page layout editor
- We can hide a section header detail view, edit view, or both views
- We can add blank spaces instead of fields
- We can preview the layout for different profiles
Q2 In a Model View Controller architecture, which of the following are appropriate to Views? (Select two)
- Page layouts
- Validation rules
- Tabs
- Workflows
Q3 What is possible through page layouts for custom objects? (Select two)
- Adding custom fields and buttons
- Setting a mandatory field based on a certain value on another field
- Adding inline Visualforce pages
- Setting a three-column display
Q4 Which of the following cannot be included in the user page layout (Select two)
- Tagging
- Custom links
- Inline Visualforce pages
- Custom buttons
- Custom fields
Q5 Which editions support Apex and Visualforce? (Select two)
- Unlimited Edition
- Enterprise Edition
- Apex Edition
- Professional Edition
- Group Edition
Q6 Position is a custom object containing details of each position. A candidate contains the details of each candidate such as skills. When a user is viewing position records, they should also be able to see all those candidates who match the skills required for the post. However, a position can have no candidate, and a candidate record can also be kept blank. A position can be applied by multiple candidates, while a candidate can also apply to multiple positions. What can be done to achieve this?
- Creating a master-child relationship between them
- Creating a junction object to store both the values
- Creating a lookup relationship of a candidate on a position
- Creating a Visualforce page
Q7 What are the different custom tabs that you can create? (Select three)
- Web tabs
- Apex tabs
- Visualforce tabs
- Custom object tabs
- Standard object tabs