Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
147 Cards in this Set
- Front
- Back
Force.com Sites comes with self registration
|
FALSE
|
|
Customer Portal Licenses come with self registration
|
TRUE
|
|
The multicurrency feature activation can be undone
|
FALSE
|
|
Additional currencies can be added after the intial multicurrency feature activation
|
TRUE
|
|
Visualforce is required to filter a related list
|
TRUe
|
|
objects must be inserted with a salesforce id with data loader
|
FALSE
|
|
In a migration, Accounts should be inserted before Users
|
FALSE
|
|
In a migration, Contacts should be inserted before Accounts in data loader
|
FALSE
|
|
Approvals are initiated when the entry criteria are met
|
FALSE
|
|
Approvals are initiated when the user clicks "Submit for Approval"
|
TRUE
|
|
A cross object formula can pull a value from a Contact onto an Account
|
FALSE
|
|
A cross object formula can pull a value from a Account onto an Contact
|
TRUE
|
|
A cross object formula can pull a value from a PARENT onto an CHILD
|
TRUE
|
|
In a migration, active validation rules run on records inserted through data loader
|
TRUE
|
|
In a migration, triggers run on records inserted through data loader
|
TRUE
|
|
In MVC, Objects represent the Model
|
TRUE
|
|
In MVC, Visualforce pages are the controller
|
FALSE
|
|
IN MVC, Apex Classes are the controller
|
TRUE
|
|
Managers who want to monitor progress of metrics month after month should use analytic snapshots
|
TRUE
|
|
Summary reports are the only report type with a grand total
|
FALSE
|
|
Troubleshooting Time dependent Workflows is done in the debug log
|
FALSE
|
|
Troubleshooting Time dependent Workflows is done in setup>monitoring>time based workflow
|
TRUE
|
|
Apex Tabs allow custom code to be display on a tab in any app
|
FALSE
|
|
Visualforce tabs allow custom code to be displayed in a tab
|
TRUE
|
|
Web tabs allow a webpage to be displayed in an iframe on a tab in an app
|
TRUE
|
|
in a migration, With the "system insertable fields" feature activation you can insert a record with a created date field
|
TRUE
|
|
in a migration, With the "system insertable fields" feature activation you can insert a record with a modifiedby field
|
TRUE
|
|
Rollup fields must total child records
|
TRUE
|
|
Custom Object Tabs provide a way to create and list custom objects
|
TRUE
|
|
Radio button are a standard field type
|
FALSE
|
|
Radio buttons require Visualforce
|
TRUE
|
|
System Admin profile users will be able to see decrypted values by default
|
TRUE
|
|
An advantage to Sites vs Custom Portal is users don't need to login to see unauthenticated content.
|
TRUE
|
|
the import wizard is limited to 10,000 records
|
FALSE
|
|
Data loader is limited to 100,000 records
|
TRUE
|
|
Import Wizard is limited to 50,000 records
|
TRUE
|
|
Modify All permission for the object on the profile will allow a user to edit a record locked for approval
|
TRUE
|
|
Visualforce pages can be added to page layouts in a section of the document if the standard controller matches the object type
|
TRUE
|
|
Page layouts allow a 3 column section without visualforce
|
FALSE
|
|
Validation rule can make one field required based on the result of another field
|
TRUE
|
|
Page layouts can make a field required
|
TRUE
|
|
Upon final reject an approval process can create a task
|
TRUE
|
|
Upon final reject an approval process can send an email
|
TRUE
|
|
Upon final reject an approval process can lock a record
|
TRUE
|
|
HIERARCHY Fields can add a users manager to the record
|
TRUE
|
|
Report maintain calculated values from previous runs
|
FALSE
|
|
outlier values can be color coded on dashboards
|
TRUE
|
|
IF AN upsert finds multiple matches on an external id the first match is updated
|
FALSE
|
|
The force.com metadata api is used to create new custom objects
|
TRUE
|
|
AJAX TOOLKIT ALLOws multiple applications to share a single password & login
|
FALSE
|
|
isdeleted can be set for inserted records by dataloader
|
FALSE
|
|
Report running user can let a manager share data with subordinates
|
FALSE
|
|
Dashboard Running User lets a manager share information with subordinates
|
TRUE
|
|
Import wizard inserts for custom objects
|
FALSE
|
|
Users can be inserted with the Import Wizard
|
TRUE
|
|
Sites has restricted IP ranges
|
FALSE
|
|
Sites has read write on standard objects
|
FALSE
|
|
Custom Object Org Wide Default set to Private. Hierarchies are turned off. All users can change the record owner
|
FALSE
|
|
Custom Object Org Wide Default set to Private. Hierarchies are turned off. Admins can edit the record
|
TRUE
|
|
Custom Object Org Wide Default set to Private. Hierarchies are turned off. Manually shared users can be granted edit rights
|
TRUE
|
|
Custom Object Org Wide Default set to Private. Hierarchies are turned off. Record owners can edit
|
TRUE
|
|
the endpoint for a sandbox is http://sandbox.salesforce.com
|
FALSE
|
|
the endpoint for a sandbox is http://test.salesforce.com
|
TRUE
|
|
Data loader passwords can be encrypted for command line mode
|
TRUE
|
|
A CEO would like a list of the top 10 positions by # of job applications. Dashboard guages should be used
|
FALSE
|
|
A CEO would like a list of the top 10 positions by # of job applications. Dashboard tables should be used
|
TRUE
|
|
Force.com Sites Domain names must be unique<br />
|
TRUE
|
|
Force.com Sites Domain names can be changed for a fee.
|
FALSE
|
|
Force.com Sites Domain names can be a company name AND must be unique<br />
|
TRUE
|
|
Job Application has a lookup to Candidate. Recruiters want to see a Name & Email address on each Job Application. <br />This requires a field update
|
FALSE
|
|
Job Application has a lookup to Candidate. Recruiters want to see a Name & Email address on each Job Application<br />this requires a cross object formula with an apex trigger
|
FALSE
|
|
Job Application has a lookup to Candidate. Recruiters want to see a Name & Email address on each Job Application<br />This requires a cross object formula
|
TRUE
|
|
In the custom object Bugs, some bugs must relate to eachother in a hierarchical fashion. a lookup to the bug object titled Parent bug should be used
|
TRUE
|
|
In a lookup relationship, the child IS DELETED when the parent is deleted.
|
FALSE
|
|
The value in a custom field called Salary is 50,000. the formula, ISNUMBER (Salary__c), WOULD return false
|
TRUE
|
|
A custom setting is accessed by apex to retrieved stored values
|
TRUE
|
|
the process visualizer is read only
|
TRUE
|
|
the process visualizer shows support processes
|
FALSE
|
|
Sites is integrated with google analytics
|
TRUE
|
|
Sites and Google Analytics can track the source of every lead
|
FALSE
|
|
Batch Apex can be initiated by the Apex Scheduler like a cron job
|
TRUE
|
|
Batch Apex can be helpful to overcome governor limits on triggers
|
TRUE
|
|
Cross object workflow can set a field on a contact every time an account changes status
|
FALSE
|
|
A Profile can be set to modify all objects of a certain type regardless if that user owns the record
|
TRUE
|
|
delete access can be controlled from the profile by object type
|
TRUE
|
|
Field-level access allows us to hide sensitive information<br />like the maximum salary for a position or a candidate's social security<br />number without having to hide the whole object.
|
TRUE
|
|
org wide defaults allow us to make sure that a manager will always have<br />access to the same records as his or her subordinates.
|
FALSE
|
|
workflows allow us to make sure that a manager will always have<br />access to the same records as his or her subordinates.
|
FALSE
|
|
role hierarchies allow us to make sure that a manager will always have<br />access to the same records as his or her subordinates.
|
TRUE
|
|
sharing rules allow us to make automatic exceptions to<br />organization-wide defaults for particular groups of users.
|
TRUE
|
|
manual sharing allows record owners to give read and edit permissions<br />to folks who might not have access to the record any other way.
|
TRUE
|
|
profiles do not control the tabs the user can view in the app
|
FALSE
|
|
User child records control the hours during which the user can log in to the app
|
FALSE
|
|
profiles control the record types available to the user
|
TRUE
|
|
A User can be assigned to multiple profiles at a time
|
FALSE
|
|
Setup ➤Security Controls ➤ Field Accessibility lets you hide fields
|
TRUE
|
|
Setup ➤Security Controls ➤ This is boring
|
wake up ! you are getting smarter :)
|
|
Users assigned to roles near the top of the hierarchy (normally the CEO, executives, and other<br />management) get to access the data of all the users who fall directly below them in the hierarchy.
|
TRUE
|
|
You can use<br />the Grant Access Using Hierarchies checkbox to enable and disable record access<br />through hierarchies on an object-by-object basis when you set your org-wide defaults.
|
TRUE
|
|
Sharing rules can be used to restrict access and lock users out of certain data
|
FALSE
|
|
A public group is a collection of individual users, other groups, individual roles, and/or roles with their subordinates that all have a function in common.
|
TRUE
|
|
“Customize Application” permission lets users assigned to that profile customize just about anything in Salesforce.com, from page layouts to the data model
|
TRUE
|
|
A delegated administration group is a group of non-administrator users with limited administrative<br />privileges.
|
TRUE
|
|
a workflow outbound message, sends data to an external<br />Web service, such as another application in the cloud
|
TRUE
|
|
workflows cannot send out emails with merged data from communication templates
|
FALSE
|
|
workflows can assign tasks
|
TRUE
|
|
workflow rules can have only 2 actions
|
FALSE
|
|
workflow rules can have only 1 field update
|
FALSE
|
|
Users who have access to the queue can examine every record that's<br />in it and claim ownership of the ones they want.
|
TRUE
|
|
a queue can be the only value in an ownerid field
|
TRUE
|
|
we can define a time-dependent workflow action that alerts<br />the recruiting manager if no recruiter claims a position record within a certain number of days.
|
TRUE
|
|
time based workflows can be evaluated every 5 minutes
|
FALSE
|
|
time base workflow can be evaluated every hour
|
TRUE
|
|
there is a limit to the number of custom fields on an opp
|
TRUE
|
|
the console breaks sfdc into 5 screens will all the required list views for a busy service agent
|
FALSE
|
|
profiles control console layouts and therefore the list views that they contain
|
TRUE
|
|
Encryped fields are limited to 170 characters
|
FALSE
|
|
Encrypted fields are not searchable
|
TRUE
|
|
all users can clone the value of an encrypted field when cloning that record.
|
FALSE
|
|
SCONTROLS ARE obsolete and should not be used for new development
|
TRUE
|
|
You can specify whether a user can execute<br />methods in a custom controller based on the user’s profile.
|
TRUE
|
|
A controller extension is a class written in Apex that adds to or overrides behavior in a standard or<br />custom controller
|
TRUE
|
|
Visualforce cannot override a New button
|
FALSE
|
|
Visualforce cannot override a save button
|
FALSE
|
|
import wizard can be scheduled
|
FALSE
|
|
Dataloader does not write log files
|
FALSE
|
|
DataLoader appends a new column on the far right to error files with the exact error message
|
TRUE
|
|
You can use the Process Visualizer to save as pdf
|
TRUE
|
|
records can be deleted with dataloader
|
TRUE
|
|
data loader can run from a command line in a windows .bat file
|
TRUE
|
|
each dashboard can have 3 running users
|
FALSE
|
|
In a migration, Opportunity should be inserted before OpportunityContactRoles
|
TRUE
|
|
If a master is deleted the detail is deleted
|
TRUE
|
|
If a lookup relationship record is deleted all related records are deleted
|
FALSE
|
|
Adding a lookup relationship field will allow a related list to be added to the records page layout
|
TRUE
|
|
the spyglass icon loads a lookup dialog that can be controlled with search layout to control which columns display in search results
|
TRUE
|
|
In Data loader 50,000 more records CRUD at a time
|
TRUE
|
|
ID's are identical in
|
Production and full copy sandbox only (TRUE)
|
|
Maximum No of Master Details per child object
|
2
|
|
For the user object what can you do in the page layout
|
custom link, nline vf page, custom field
|
|
For approval process what groups can you have
|
roles and subordicates
|
|
In Page Layout can you add inline vf
|
True
|
|
What does out of the box salesforce give you?
|
approval process
|
|
A developer wants to ensure that when a parent record is deleted, child records are not deleted. Which relationship should the developer choose?
|
lookup
|
|
A custom tab can be included in as many applications as desired
|
True
|
|
When would a developer use upsert and external IDs? (Choose two answers.
|
to integrate with an external system OR To load related records without knowing Salesforce record IDs
|
|
A group of executives has requested a convenient way to see daily metrics without having to log in to Salesforce. How would a developer accomplish this goal?
|
Schedule the dashboard for daily refresh and email distribution.(your answer)
|