Adeveloper needs to create a visualforce page that displays case data. the page will be used by both support reps and support managers. the support rep profile does not allow visibility of the customer_satisfaction_c field, but the support manager profile does. how can the developer create the page to enforce field level security and keep future maintenance to a minimum? a. create one visualforce page for use by both profilesb. use a new support manager permission setsc. create a separate visualforce page for each profiled. use a custom controller that has the with sharing keywords

B. Use a new support manager permission sets

Explanation:

According to the requirements, field level security is required so, 1st options is not suitable because it may reduce the maintenance cost but increase the risk of security.

By creating a separate page for each of the two, it will leads to increase in the maintenance cost of the system. So Option C is also not suitable.

Option B is more Suitable as compared to others, that Create a new support manager permission set, with the help of this, both of Support rep and Support manager can visualize their required information with the help of support manager permission. This solution will not compromise the security and not increase the maintenance cost.

given the lack of choices, i'm gonna wing it and say that pushing your car off a cliff might not be the best idea. your car might sustain damage from the fall and will probably result in the car being too damaged to jump start.

if that's not good enough, avoid filling the car with bees. bees might get agitated when trapped or during the moving process, and might result in death or painful stings that will make jump starting your car very difficult. but in the event that you do choose to fill your car with bees, remember to wear protective gear!