DISA HBSS 201 ADMIN ePO5.1(2025)
EXAM 130 QUESTIONS AND CORRECT
ANSWERS (100% VERIFIED ANSWERS)
Users |at |Ursa |Major |Solar |are |trying |to |create |Opportunities. |When |populating |a |custom |picklist
|field, |the |users |receive |errors. |Additionally, |when |the |users |select |either |of |the |two |values |in |the
|picklist, |they |receive |different |error |messages |above |the |field |and |are |unable |to |save |the
|Opportunities. |Why |is |this |error |likely |occurring? |- |answer-The |picklist |field |has |contradicting
|validation |rules.
What |should |a |System |Administrator |do |to |organize |the |fields |available |on |a |report? |- |answer-Create
|a |custom |report |type.
Customers |complain |that |they |do |not |know |when |Comments |have |been |added |to |their |Cases. |-
|answer- |Enable |Case |Comment |Notification |to |Contacts.
Ursa |Major |Solar's |administrator |created |a |new |account |record |type, |but |when |marketing |users |are
|creating |new |account |records, |they |are |unable |to |choose |the |new |record |type. |What |are |two
|potential |causes |of |this |issue? |- |answer-1. |The |record |type |is |disabled |on |the |marketing |user |profile.
|2. |The |record |type |is |deactivated.
An |Administrator |at |Ursa |Major |Solar |is |converting |a |lead |and |needs |to |capture |custom |lead |data |on
|the |converted |contact. |What |should |the |administrator |do |to |accomplish |this |goal? |- |answer-Map
|custom |lead |fields |to |custom |contact |fields.
An |administrator |for |Ursa |Major |Solar |wants |to |allow |internal |users |to |view |a |dashboard |as |a |Sales
|Manager |within |a |given |sales |region. |How |can |this |be |configured? |- |answer-Create |a |dashboard |to |run
|as |a |specified |user.
Universal |Containers |has |a |sales |team |focused |on |renewals. |They |will |use |many |of |the |same
|Opportunity |fields |as |other |teams, |but |need |different |Stage |values. |- |answer-Stage |Selected |Values |in
|the |Sales |Processes
,Which |Salesforce |tool |should |an |administrator |use |to |better |understand |all |of |the |configuration
|changes |that |have |been |made |from |January |1 |through |July |1? |- |answer-Setup |Audit |Trail
A |System |Administrator |enables |Case |Feed |Actions |and |Feed |Items |in |Support |Settings. |With |the
|appropriate |Profile |permissions |enabled, |what |change |will |users |see? |- |answer-Cases |will |use |Feed
|Layouts |rather |than |standard |Page |Layouts.
A |System |Administrator |will |use |the |Import |Wizard |to |update |existing |Account |records. |Which |values
|can |the |Import |Wizard |use |to |find |matching |records? |- |answer-Account |Name |and |Site |fields
An |administrator |at |Ursa |Major |Solar |is |configuring |a |workflow |rule. |What |are |two |considerations |for
|an |administrator |in |this |situation? |- |answer-1. |Rule |actions |can |take |place |immediately |or |can |be
|time |based. |2. |Rules |can |be |evaluated |when |records |are |created |or |edited.
Ursa |Major |Solar |is |using |products |and |price |books. |Which |two |items |should |an |administrator |take
|into |considerations |about |these |features? |- |answer-1. |The |standard |and |list |price |for |a |product |can
|be |listed |in |more |than |one |currency. |2. |A |product |can |have |a |different |list |price |in |different |price
|books.
An |administrator |at |Ursa |Major |Solar |is |setting |up |case |feed. |What |should |the |administrator
|consider? |- |answer-Chatter |feed |tracking |must |be |enabled |for |the |case |object.
Universal |Containers |wants |to |automatically |assign |a |Task |to |account |managers |when |a |customer's
|agreement |is |about |to |expire. |How |should |a |System |Administrator |configure |this |functionality? |-
|answer- |Create |a |Time-based |Workflow |on |Account |with |a |rule |criteria |of |Agreement |End |Date |>
|TODAY().
Which |set |of |Salesforce |records |is |exported |by |choosing |the |"Export |All" |option |instead |of |"Export" |in
|Data |Loader? |- |answer-Records |for |a |specified |object |including |records |in |the |recycle |bin.
Ursa |Major |Solar |has |the |following |environment |and |requirements:
1. |Critical, |high-priority |accounts |have |an |assigned |District |Manager, |Sales |Representative, |Inside |Sales
|Representative, |and |Customer |Service |Representative. |2. |The |Sales |Manager |wants |to |prevent |these
|accounts |from |being |inadvertently |contacted |more |than |once |on |the |same |day. |3. |The |Sales
|Manager |wants |to |report |on |various |customer |interactions. |How |should |the |administrator |fulfill
|these |requirements? |- |answer-Log |a |separate |task, |call, |or |activity |on |the |account.
,At |Ursa |Major |Solar, |an |administrator |has |set |up |a |new |user. |The |user |needs |to |activate |the |account
|before |the |email |link |expires |by |default. |How |long |does |the |user |have |before |the |link |expires? |-
|answer-7 |days
A |System |Administrator |creates |a |Workflow |Rule |that |assigns |a |task |to |a |support |manager |role |when
|a |case |is |escalated. |The |case |owner |is |complaining |about |being |assigned |these |tasks. |What |should |a
|System |Administrator |do |to |correct |this |issue? |- |answer-Make |sure |there |is |only |one |user |in |the
|role.
What |are |two |ways |to |customize |basic |reports |using |Lightning |Experience? |- |answer-1. |By |adding |a |filter
2. |By |adding |a |chart
Ursa |Major |Solar |customers |are |starting |to |request |custom-sized |solar |panels, |which |are |currently
|unavailable |in |the |standard |inventory. |Management |has |decided |to |add |custom |sizing |as |an |add-on
|item |in |Salesforce. |The |administrator |needs |to |allow |sales |users |to |add |custom |sizing |to |the |total
|opportunity |sale. |What |should |the |administrator |do |to |achieve |this |goal? |- |answer-Add |custom
|sizing |as |a |new |product |in |a |pricebook.
Which |type |of |field |do |administrators |use |when |creating |a |junction |object? |- |answer-Master-detail
A |System |Administrator |wants |to |implement |a |feature |for |call |recording |to |monitor |customer |service
|quality |using |Salesforce |Service |Cloud. |Which |two |statements |regarding |call |recording |should |be
|considered |when |implementing |this |requirement? |- |answer-1. |Call |recording |is |a |feature |that |a
|developer |might |create |with |Salesforce |App |Cloud. |2. |Call |recording |is |a |feature |of |some |add-on
|products |from |the |AppExchange.
Which |two |changes |are |tracked |in |the |Setup |Audit |Trail? |- |answer-1. |Resetting |a |user's |password |2.
|Using |the |Data |Import |Wizard
Ursa |Major |Solar |wants |to |assign |feature |licenses |to |user |records |in |Salesforce. |What |are |two |features
|licenses |that |can |be |assigned |in |this |situation? |- |answer-1. |Knowledge |User |2. |Service |Cloud |User
Which |feature |should |Ursa |Major |Solar |use |if |they |want |their |support |agents |who |are |skilled |in |a
|particular |product |line |to |own |cases |directly |after |customers |log |them |from |an |automated
|channel? |- |answer-Assignment |rules
, An |administrator |at |Ursa |Major |Solar |is |implementing |an |organization-wide |default |option |for |the
|Account |object. |What |is |a |correct |option |for |the |administrator |in |this |scenario? |- |answer-Private
Universal |Containers |has |a |team |of |Account |Managers |that |requested |email |alerts |any |time |an
|Opportunity |or |Case |is |created |on |Accounts |that |they |own. |What |is |the |minimum |number |of
|workflows |needed |to |accomplish |this |task? |- |answer-Two |workflow |rules |with |one |email |alert |each
Universal |Containers |sells |through |many |different |reseller |networks. |Each |reseller's |deals |are |tracked
|on |separate |opportunities. |The |sales |manager |is |concerned |that |the |pipeline |report |is |not |accurate
|due |to |multiple |opportunities |for |the |same |end |customer. |How |should |the |sales |process |be |modified
|to |ensure |opportunities |are |not |double-counted |in |the |pipeline? |- |answer-Change |the |forecast
|category |to |Omitted |on |the |duplicate |opportunities.
A |Delegated |Administrator |at |Universal |Containers |cannot |edit |the |Created |Date |field |for |the
|Account |record. |What |reason |should |the |System |Administrator |give |for |why |this |is |occurring? |-
|answer-This |is |a |System |Audit |field |and |it |is |Read-Only |for |existing |records.
What |is |a |benefit |of |entering |Trusted |IP |Ranges |in |the |Network |Access |section? |- |answer-Users |that
|log |in |within |the |network |will |not |be |required |to |verify |their |identity.
What |are |two |reasons |a |user |cannot |be |deactivated? |- |answer-1. |The |user |is |the |recipient |of
|Workflow |Email |Alerts. |2. |The |user |is |a |Customer |Community |Administrator.
Ursa |Major |Solar |uses |the |following: |1. |Private |data |access |model |for |cases |2. |Support |agents, |who
|own |cases |3. |Product |specialists |who |occasionally |need |access |to |cases |in |their |product |line. |What
|are |two |actions |that |will |allow |the |appropriate |access |in |this |scenario? |- |answer-1. |Administrators
|configure |pre- |defined |case |teams |and |assignment |rules. |2. |Case |owners |manually |add |product
|specialists |to |case |teams.
Ursa |Major |Solar |has |selected |report |folders |that |are |shared |with |a |small |group |of |users |who |are |on
|Lightning |Experience. |The |administrator |needs |to |prevent |these |users |from |customizing |the
|information |in |the |reports. |What |should |the |administrator |do |to |achieve |this |goal? |- |answer-Lock
|report |filters
EXAM 130 QUESTIONS AND CORRECT
ANSWERS (100% VERIFIED ANSWERS)
Users |at |Ursa |Major |Solar |are |trying |to |create |Opportunities. |When |populating |a |custom |picklist
|field, |the |users |receive |errors. |Additionally, |when |the |users |select |either |of |the |two |values |in |the
|picklist, |they |receive |different |error |messages |above |the |field |and |are |unable |to |save |the
|Opportunities. |Why |is |this |error |likely |occurring? |- |answer-The |picklist |field |has |contradicting
|validation |rules.
What |should |a |System |Administrator |do |to |organize |the |fields |available |on |a |report? |- |answer-Create
|a |custom |report |type.
Customers |complain |that |they |do |not |know |when |Comments |have |been |added |to |their |Cases. |-
|answer- |Enable |Case |Comment |Notification |to |Contacts.
Ursa |Major |Solar's |administrator |created |a |new |account |record |type, |but |when |marketing |users |are
|creating |new |account |records, |they |are |unable |to |choose |the |new |record |type. |What |are |two
|potential |causes |of |this |issue? |- |answer-1. |The |record |type |is |disabled |on |the |marketing |user |profile.
|2. |The |record |type |is |deactivated.
An |Administrator |at |Ursa |Major |Solar |is |converting |a |lead |and |needs |to |capture |custom |lead |data |on
|the |converted |contact. |What |should |the |administrator |do |to |accomplish |this |goal? |- |answer-Map
|custom |lead |fields |to |custom |contact |fields.
An |administrator |for |Ursa |Major |Solar |wants |to |allow |internal |users |to |view |a |dashboard |as |a |Sales
|Manager |within |a |given |sales |region. |How |can |this |be |configured? |- |answer-Create |a |dashboard |to |run
|as |a |specified |user.
Universal |Containers |has |a |sales |team |focused |on |renewals. |They |will |use |many |of |the |same
|Opportunity |fields |as |other |teams, |but |need |different |Stage |values. |- |answer-Stage |Selected |Values |in
|the |Sales |Processes
,Which |Salesforce |tool |should |an |administrator |use |to |better |understand |all |of |the |configuration
|changes |that |have |been |made |from |January |1 |through |July |1? |- |answer-Setup |Audit |Trail
A |System |Administrator |enables |Case |Feed |Actions |and |Feed |Items |in |Support |Settings. |With |the
|appropriate |Profile |permissions |enabled, |what |change |will |users |see? |- |answer-Cases |will |use |Feed
|Layouts |rather |than |standard |Page |Layouts.
A |System |Administrator |will |use |the |Import |Wizard |to |update |existing |Account |records. |Which |values
|can |the |Import |Wizard |use |to |find |matching |records? |- |answer-Account |Name |and |Site |fields
An |administrator |at |Ursa |Major |Solar |is |configuring |a |workflow |rule. |What |are |two |considerations |for
|an |administrator |in |this |situation? |- |answer-1. |Rule |actions |can |take |place |immediately |or |can |be
|time |based. |2. |Rules |can |be |evaluated |when |records |are |created |or |edited.
Ursa |Major |Solar |is |using |products |and |price |books. |Which |two |items |should |an |administrator |take
|into |considerations |about |these |features? |- |answer-1. |The |standard |and |list |price |for |a |product |can
|be |listed |in |more |than |one |currency. |2. |A |product |can |have |a |different |list |price |in |different |price
|books.
An |administrator |at |Ursa |Major |Solar |is |setting |up |case |feed. |What |should |the |administrator
|consider? |- |answer-Chatter |feed |tracking |must |be |enabled |for |the |case |object.
Universal |Containers |wants |to |automatically |assign |a |Task |to |account |managers |when |a |customer's
|agreement |is |about |to |expire. |How |should |a |System |Administrator |configure |this |functionality? |-
|answer- |Create |a |Time-based |Workflow |on |Account |with |a |rule |criteria |of |Agreement |End |Date |>
|TODAY().
Which |set |of |Salesforce |records |is |exported |by |choosing |the |"Export |All" |option |instead |of |"Export" |in
|Data |Loader? |- |answer-Records |for |a |specified |object |including |records |in |the |recycle |bin.
Ursa |Major |Solar |has |the |following |environment |and |requirements:
1. |Critical, |high-priority |accounts |have |an |assigned |District |Manager, |Sales |Representative, |Inside |Sales
|Representative, |and |Customer |Service |Representative. |2. |The |Sales |Manager |wants |to |prevent |these
|accounts |from |being |inadvertently |contacted |more |than |once |on |the |same |day. |3. |The |Sales
|Manager |wants |to |report |on |various |customer |interactions. |How |should |the |administrator |fulfill
|these |requirements? |- |answer-Log |a |separate |task, |call, |or |activity |on |the |account.
,At |Ursa |Major |Solar, |an |administrator |has |set |up |a |new |user. |The |user |needs |to |activate |the |account
|before |the |email |link |expires |by |default. |How |long |does |the |user |have |before |the |link |expires? |-
|answer-7 |days
A |System |Administrator |creates |a |Workflow |Rule |that |assigns |a |task |to |a |support |manager |role |when
|a |case |is |escalated. |The |case |owner |is |complaining |about |being |assigned |these |tasks. |What |should |a
|System |Administrator |do |to |correct |this |issue? |- |answer-Make |sure |there |is |only |one |user |in |the
|role.
What |are |two |ways |to |customize |basic |reports |using |Lightning |Experience? |- |answer-1. |By |adding |a |filter
2. |By |adding |a |chart
Ursa |Major |Solar |customers |are |starting |to |request |custom-sized |solar |panels, |which |are |currently
|unavailable |in |the |standard |inventory. |Management |has |decided |to |add |custom |sizing |as |an |add-on
|item |in |Salesforce. |The |administrator |needs |to |allow |sales |users |to |add |custom |sizing |to |the |total
|opportunity |sale. |What |should |the |administrator |do |to |achieve |this |goal? |- |answer-Add |custom
|sizing |as |a |new |product |in |a |pricebook.
Which |type |of |field |do |administrators |use |when |creating |a |junction |object? |- |answer-Master-detail
A |System |Administrator |wants |to |implement |a |feature |for |call |recording |to |monitor |customer |service
|quality |using |Salesforce |Service |Cloud. |Which |two |statements |regarding |call |recording |should |be
|considered |when |implementing |this |requirement? |- |answer-1. |Call |recording |is |a |feature |that |a
|developer |might |create |with |Salesforce |App |Cloud. |2. |Call |recording |is |a |feature |of |some |add-on
|products |from |the |AppExchange.
Which |two |changes |are |tracked |in |the |Setup |Audit |Trail? |- |answer-1. |Resetting |a |user's |password |2.
|Using |the |Data |Import |Wizard
Ursa |Major |Solar |wants |to |assign |feature |licenses |to |user |records |in |Salesforce. |What |are |two |features
|licenses |that |can |be |assigned |in |this |situation? |- |answer-1. |Knowledge |User |2. |Service |Cloud |User
Which |feature |should |Ursa |Major |Solar |use |if |they |want |their |support |agents |who |are |skilled |in |a
|particular |product |line |to |own |cases |directly |after |customers |log |them |from |an |automated
|channel? |- |answer-Assignment |rules
, An |administrator |at |Ursa |Major |Solar |is |implementing |an |organization-wide |default |option |for |the
|Account |object. |What |is |a |correct |option |for |the |administrator |in |this |scenario? |- |answer-Private
Universal |Containers |has |a |team |of |Account |Managers |that |requested |email |alerts |any |time |an
|Opportunity |or |Case |is |created |on |Accounts |that |they |own. |What |is |the |minimum |number |of
|workflows |needed |to |accomplish |this |task? |- |answer-Two |workflow |rules |with |one |email |alert |each
Universal |Containers |sells |through |many |different |reseller |networks. |Each |reseller's |deals |are |tracked
|on |separate |opportunities. |The |sales |manager |is |concerned |that |the |pipeline |report |is |not |accurate
|due |to |multiple |opportunities |for |the |same |end |customer. |How |should |the |sales |process |be |modified
|to |ensure |opportunities |are |not |double-counted |in |the |pipeline? |- |answer-Change |the |forecast
|category |to |Omitted |on |the |duplicate |opportunities.
A |Delegated |Administrator |at |Universal |Containers |cannot |edit |the |Created |Date |field |for |the
|Account |record. |What |reason |should |the |System |Administrator |give |for |why |this |is |occurring? |-
|answer-This |is |a |System |Audit |field |and |it |is |Read-Only |for |existing |records.
What |is |a |benefit |of |entering |Trusted |IP |Ranges |in |the |Network |Access |section? |- |answer-Users |that
|log |in |within |the |network |will |not |be |required |to |verify |their |identity.
What |are |two |reasons |a |user |cannot |be |deactivated? |- |answer-1. |The |user |is |the |recipient |of
|Workflow |Email |Alerts. |2. |The |user |is |a |Customer |Community |Administrator.
Ursa |Major |Solar |uses |the |following: |1. |Private |data |access |model |for |cases |2. |Support |agents, |who
|own |cases |3. |Product |specialists |who |occasionally |need |access |to |cases |in |their |product |line. |What
|are |two |actions |that |will |allow |the |appropriate |access |in |this |scenario? |- |answer-1. |Administrators
|configure |pre- |defined |case |teams |and |assignment |rules. |2. |Case |owners |manually |add |product
|specialists |to |case |teams.
Ursa |Major |Solar |has |selected |report |folders |that |are |shared |with |a |small |group |of |users |who |are |on
|Lightning |Experience. |The |administrator |needs |to |prevent |these |users |from |customizing |the
|information |in |the |reports. |What |should |the |administrator |do |to |achieve |this |goal? |- |answer-Lock
|report |filters
