Custom objects on the "detail" side of a master-detail relationship cannot have sharing rules.

• A.False
• B.True

Comment: *

Name: *

Email: *

Verification: *

Your company has a Custom Object called Projects with a Lookup relationship to Opportunities. Once an Opportunity is closed won a project needs to be created automatically and assigned to a queue.
How would you best accomplish this requirement?

• A.Apex Trigger on Projects
• B.Visual Flow
• C.Lightning Process Builder
• D.Apex Trigger on Opportunities

Comment: *

Name: *

Email: *

Verification: *

What is the name for an object that enables a many-to-many relationship between two other objects?

• A.Schema Object
• B.Connector Object
• C.Parent Object
• D.Child Object
• E.Junction Object

Comment: *

Name: *

Email: *

Verification: *

How is the Lightning Component framework different from Visualforce?

• A.The framework can be used to build mobile apps only.
• B.None of the above.
• C.The framework is client-side centric, while Visualforce relies on server calls.
• D.They are both useful in building components, but Visualforce has a simpler markup.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers conducts evaluations of its sales reps using a custom object consisting of numerical scores and executive comments. The company wants to ensure that only the sales reps, their managers, and their manager's executives can view the rep's evaluation record, but the reps should not be able to view the executive comment fields on their review.
How can these requirements be met?

• A.Use a private sharing model granting record access using custom settings; manage field access with record types and page layouts.
• B.Use a private sharing model granting record access using hierarchy; manage field access with record types and field-level security.
• C.Use a private sharing model granting record access using custom settings; manage field access with page layouts and field-level security.
• D.Use a private sharing model granting record access using hierarchy; manage field access with field-level security.

Comment: *

Name: *

Email: *

Verification: *