Security and Performance Superbadge Unit
Design a data model based on a set of security and performance requirements
Security and Performance Superbadge Unit
What You'll Be Doing to Earn This Superbadge
- Demonstrate how to use Big Objects for big data.
- Work with external data.
- Apply data classification, security, and access to fields.
Concepts Tested in This Superbadge
- Big Objects
- External Objects
- Data Classification
Prework and Notes
Sign Up for a Developer Edition Org with Special Configuration
To complete this superbadge unit, you need a special Developer Edition org that contains special configuration and sample data. Note that this Developer Edition org is designed to work with the challenges in this superbadge unit.
-
Sign up for a free Developer Edition org with special configuration.
Fill out the form. For Email address, enter an active email address.
- After you fill out the form, click Sign me up.
When you receive the activation email (this might take a few minutes), open it and click Verify Account.
Complete your registration by setting your password and challenge question. Tip: Save your username, password, and login URL in a secure place—such as a password manager—for easy access later.
You are logged in to your superbadge Developer Edition org.
Now, connect your new Developer Edition org to Trailhead.
Make sure you’re logged in to your Trailhead account.
In the Challenge section at the bottom of this page, select Connect Org from the picklist.
On the login screen, enter the username and password for the Developer Edition org you just set up.
On the Allow Access? page, click Allow.
On the Want to connect this org for hands-on challenges? page, click Yes! Save it. You are redirected back to the Challenge page and ready to use your new Developer Edition org to earn this superbadge.
Now that you have a Salesforce org with special configuration for this superbadge unit, you’re good to go.
Tips
- Grab a pen and paper. You may want to jot down notes and map out the data model as you read the requirements.
- Enter all labels exactly as described in the instructions. Labels are case-sensitive and spelling counts.
- When possible, copy and paste the label names from superbadge instructions instead of typing them.
- Make sure you save your work before running the challenge check.
- Build your solution according to the requirements; adding more configurations can cause challenge checks to fail.
- We recommend following best practices and always including descriptions for configurations. However, we’re not checking for descriptions in this superbadge unit.
Use Case
Flow and the Low Codes’s first album, A Momentary Lapse of Memory, has broken into the Top 10 on the Alt-Text Charts thanks to their new number-one hit song, “No More Mr. Wi-Fi.” But their success has been bolstered by a second hit song, “With or Without UI,” which has risen to number three in the charts.
As the quarter is coming to a close, the band’s manager, Art Tenor, wants to put together a way to track how many times a song is played on the two primary streaming platforms, Pineapple, and Flowafy. Given the streaming success of both “No More Mr. Wi-Fi” and “With or Without UI,” the band is expected to have enough backing to produce their second album, Back in Slack, at Appy Road Studios.
While vinyl, CDs, and cassettes were the big-ticket sales back in the day, streaming platforms are now the number-one way that listeners consume music. And because listeners can play a song multiple times a day, the amount of data you collect will be enormous.
You need to think about a data model that can handle the volume of song plays.
Standard Objects
The World Tour Manager app will use these standard objects.
- Account: Venues for shows, vendors, streaming services, studios, and fans.
- Contact: Fans, venue personnel, agents, producer, or manager.
- Campaign: Tours (or groups of performances) by a particular band or a combination of bands (such as a music festival). Examples: World Tour, Errors Tour, and the Trailblazer Tour.
- Campaign member: These are contact records related to a campaign.
Custom Objects
As the Salesforce admin, you are responsible for maintaining the custom objects that interact with standard objects to keep track of all the elements that go into a tour. These custom objects represent details such as new songs, track lists, and even guest performers that can be updated and shared with stakeholders. The custom objects include:
- Song: Includes fields such as Written by, Duration, Album, and so on.
- Album: A collection of songs released together with band and production information, artwork, and bonus tracks.
- Track List: A list of songs for a live show.
- Artist: These are the singers, writers, and performers involved with the songs, albums, and even tours if it’s a guest artist performing with the band on a particular night.
- Performs On: This object is used to connect Artists to Songs, in the future Art wants to be able to connect Artists to Albums too, however, that is out of scope for right now.
Entity Relationship Diagram (ERD)
Review the current model in Schema Builder and diagram below to understand how the band is using standard and custom objects.
Downloadable PDF of the Entity Relationship Diagram (ERD).
Business Requirements
Support Song Play Tracking
Create a way to track song plays. The Play Tracker will have a number of required fields, including song, streaming service (Account), number of plays, play date, start date for a tracking period, and end date for a tracking period. Other fields include device (such as a laptop, phone, or tablet), and operating system (such as iOS, Windows, or Android). Art Tenor informed you that when using the data in the object, the two most important fields, in order, are song and then streaming service (Account). The fields should be in ascending order to improve query performance. He also points out that we should expect up to 500 rows of data per hour.
| Field Label | Field Purpose |
|---|---|
Song |
Connects Songs to Play Tracker |
Account |
Connects Streaming Service (Account) to Play Tracker |
Number of Plays |
Holds the number of song plays |
Play Date |
Date that a song was played for that streaming service and device |
Start Date |
Start date/time of the tracking period for a song |
End Date |
End date/time of the tracking period for a song |
Device |
Device displays the type of device that the song was played on. Allocate for up to 60 characters. |
OS |
OS displays the operating system that the song was played on. Allocate for up to 60 characters. |
Once the Play Tracker is set up, you can check your work by loading in some data. (We won’t check this.)
| Start Date | End Date | Song | Streaming Service | Number of Plays | Play Date | Device | OS |
|---|---|---|---|---|---|---|---|
| 2023-10-01 11:31:45 | 2023-10-31 11:31:45 | With or Without UI | Pineapple | 1,700,000 | 2023-10-27 00:00:00 | Phone | iOS |
| 2023-10-01 11:31:45 | 2023-10-31 11:31:45 | With or Without UI | Flowafy | 1,200,000 | 2023-10-27 00:00:00 | Phone | iOS |
| 2023-10-01 11:31:45 | 2023-10-31 11:31:45 | With or Without UI | Flowafy | 1,300,000 | 2023-10-27 00:00:00 | Tablet | iOS |
| 2023-10-01 11:31:45 | 2023-10-31 11:31:45 | With or Without UI | Pineapple | 1,600,000 | 2023-10-27 00:00:00 | Tablet | iOS |
Bring in Ticket Sales Data
Flow and the Low Codes supports a charity organization called Save the DevOps. The band wants to donate 1,000 seats over several shows to the charity. In this challenge, you connect with the ticket vendor, TicketSnatcher, and check the band’s remaining tour dates at specific venues to determine the capacity, tickets sold, and tickets still available. Then create a report filtering capacity against tickets available to share with the band.
Message from Developer Team
We set up the required integration on the MuleSoft side. We’re now ready to hand over the guitar so you can connect to the integration we built and expose the performances (ticket sales) data from TicketSnatcher ticket vendor to Salesforce.
- Name:
Performances- Request Row Counts = false
- Performance data source URL:
https://security-performance-33i1n3.5sc6y6-2.usa-e2.cloudhub.io/api- Type: Salesforce Connect: OData 4.0
Make sure to activate so we can rock and roll.
Once you have this setup, create a report named
Ticket Trackingthat includes all the fields. Create a folder namedTicketing Reports. Save the report so that we can review the data.
Enhance Fan Member Privacy
Fanny Loveflow is the new president of the official Flow and the Low Codes Fan Club. As president, she represents the band’s most devoted fans. Fans are granted early access to special material, exclusive music, concert tickets, VIP passes, rare merch, and virtual concerts. Fanny plays a crucial role in the band's community and advocates for the privacy and security of fan club members.
To access this content, Fanny and her team decide to issue each fan club member an 18-digit Fan Number with enhanced security, include a description, and ensure that only Standard Users and System Administrators can see or edit the Fan Number. She also requests personal identifiable information (PII) for Email, Birthdate, Gender Identity, and Pronouns are marked as confidential in the org.
Here's how the Fan Number should look:
- Example Fan Number: 13784-623-318-1989
- Displayed Fan Number: XXXXXXXXXXXXXX1989