Skip to content

Commit 652edcb

Browse files
Updated Exam Structure Page
1 parent 7a10392 commit 652edcb

2 files changed

Lines changed: 75 additions & 53 deletions

File tree

docs/00)-CTA-Exam-Structure.md

Lines changed: 75 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -1,81 +1,120 @@
11
### Exam Structure
22

3-
The exam is typically no more than 8 pages and it breaks down into the following sections:
3+
The exam is typically 12-15 and approximately 2400-3000 words in length. There are also typically approximately 60 client requirements you must solve for on the exam. There are two potential formats to the exam these days. The first format you could potentially see on the exam is one that breaks the exam into the following sections:
44

5-
* Company Overview
6-
* Current Systems
7-
* Business Process Requirements
8-
* Migration Requirements
9-
* Accessibility/Visibility Requirements
10-
* Reporting Requirements
11-
* Project and Dev Requirements
5+
* Company Overview
6+
* Current Systems
7+
* Business Process Requirements
8+
* Migration Requirements
9+
* Accessibility/Visibility Requirements
10+
* Reporting Requirements
11+
* Project and Dev Requirements
1212

13-
It is a 4 hour and 25 minute long exam presented in front of a board of 3 other CTA's, and it consists of the following 3 events:
13+
A good example of a mock CTA exam that uses this structure is [Universal Safety Technologies](https://github.com/Coding-With-The-Force/Salesforce-CTA-Study-Guide/blob/main/CTA_Practice_Mock_Scenarios/Full%20Scenarios%20-%20Final%20Step/Full%20Scenario%20-%20Universal%20Safety%20Technologies.pdf)
1414

15-
* 180 minutes to read, solution, design and justify an architectural solution based on the 8 page scenario given to you.
15+
The second exam format you could potentially run into is one that presents more like just a long list of client requirements as opposed to being broken down into generic requirement sections like above, the second would present sections like:
1616

17-
* 45 minutes to present the solution to the judges
17+
* Project Overview
18+
* General Pain Points
19+
* Venue Onboarding
20+
* Event Sales
21+
* Order
22+
* Banner Image Creation
23+
* Expansion
1824

19-
* 40 minutes for Q&A discussion (judges ask questions about your solution you presented)
25+
A good example of a mock CTA exam that uses this second structure type is [Mega Print](https://github.com/Coding-With-The-Force/Salesforce-CTA-Study-Guide/blob/main/CTA_Practice_Mock_Scenarios/Full%20Scenarios%20-%20Final%20Step/Full%20Scenario%20-%20Mega%20Print.pdf)
26+
27+
As far as which structure you get on your exam, your guess is as good as mine, but I do believe they are trying to fully transition to the second format, so over time I believe more mocks will start to look like format 2.
28+
29+
---
30+
31+
### What to expect on the day of your CTA Review Board
32+
33+
It is approximately a 5 hour and 25 minute long exam presented in front of a board of 3 other CTA's as well as one exam proctor, and the exam is broken out in the following way
34+
35+
* 15 minute check-in prior to your exam to make sure your camera is setup right and that your desk area abides by the rules of the exam.
36+
37+
* 120 minutes of solutioning/solving the scenario
38+
39+
* 5 minute restroom break
40+
41+
* 60 minutes to continue solutioning/solving the scenario
42+
43+
* 15 minute break
44+
45+
* 45 minutes to present your solution to the CTA judges
46+
47+
* 15 minute break
48+
49+
* 40 minutes for Q&A discussion (judges ask questions about your solution you presented)
50+
51+
* 2 minutes to wrap up with the exam proctor
52+
53+
After you finish the exam you are not given your results until 2-10 weeks later. This is to prevent CTA candidates from cheating since they often reuse the same CTA for the exam on an ~2 month rotation.
2054

2155
***
2256

2357
### Technology and Materials allowed on Exam
2458

25-
* During the CTA Exam the only software you can use are google sheets, google slides and google docs.
26-
* Pens
27-
* Paper
28-
* Flipchart paper and/or whiteboard
29-
* Phone to take pictures
59+
During the CTA Exam you can no longer use any physical materials like pens, paper, etc. You can only use the software they make available to you. The only software you can use is:
60+
61+
* Lucid chart
62+
* Google sheets
63+
* Google slides
64+
* Google docs
65+
66+
I would suggest using lucid chart for diagrams, google sheets for any calculations you need to make, and google docs to solve your scenario solutions. I would not waste your time with google slides.
3067

3168
***
3269

33-
### How the exam is Administered Virtually
70+
### How the exam is Administered
71+
72+
The exam is now only administered virtually through webex and you must use a virtual machine that Salesforce sets up for you and allows you to control via webex. You also need to have a camera that is positioned so that they can see all of your screens, your hands, and surroundings while taking the exam, so the camera needs to be moveable within your office/room you are taking the exam in.
3473

35-
The virtual exam is currently administered through webex and you must use a virtual machine that Salesforce controls. You also need to have a camera the is positioned so that they can see all of your screens, your hands, and surroundings while taking the exam.
74+
The virtual machine you are controlling is a normal 1080p monitor, so try to practice on a normal sized monitor, not on an ultra wide or curved monitor as it may make exam day challenging for you.
3675

3776
***
3877

3978
### The 7 Sections Covered/Graded on the Exam
4079

41-
During the exam you will be judged in the 7 areas listed below. You can fail up to 2 sections and be able to retake the exam for free (referred to as a section retake), however, only failing one section gives you an easier retake with (a smaller scenario) that focuses heavily on the section you failed. If you fail 2 sections you have to retake the entire exam (a full scenario) during your section retake. In either scenario you still must FULLY solve the scenario, not just the section you failed. If you fail more than 2 scenarios you fail the exam, if you get a section retake and fail any of it, you fail the exam.
80+
During the exam you will be judged in the 7 areas listed below. These days you must pass every section on the exam to pass the exam. There used to be a concept called "section retakes", but those were removed in 2024, so you must receive a passing score in all 7 sections listed below.
4281

4382
**Exam Sections:**
4483

45-
1) System Architecture
46-
2) Security
47-
3) Data Model
48-
4) Solution Architecture
49-
5) Integration Architecture
50-
6) Development Life Cycle
51-
7) Communication
84+
1) System Architecture
85+
2) Security
86+
3) Data Model
87+
4) Solution Architecture
88+
5) Integration Architecture
89+
6) Development Life Cycle
90+
7) Communication
5291

5392
***
5493

5594
### Most Important Areas to Cover for the Exam
5695

57-
I think most people when they start studying for this exam are completely lost (myself included), the other architecture exams trailheads/trailmixes kinda help but they ultimately throw in a ton of junk that you don't necessarily need for this exam imo. Below are the areas you absolutely must study to prepare for the exam. This is purely based on my experience with mock exams and mock QA's
96+
I think most people when they start studying for this exam are completely lost (myself included), the other architecture exams trailheads/trailmixes kinda help but they ultimately throw in a ton of junk that you don't necessarily need for this exam imo. Below are the areas you absolutely must study to prepare for the exam.
5897

5998
1) You must know Service Cloud, Sales Cloud and Experience Cloud inside and out. You need to know their data model, their config settings, their many OOTB features and their limitations. You also need to know about how reporting works as well as CRM Analytics.
6099

61100
2) You need to know internal security mechanisms inside and out, record level sharing mechanisms, object and field level sharing mechanisms, etc (Sharing rules, Apex Sharing, Account Teams, Profiles, Perms, Roles, etc)
62101

63102
3) You need to know how to solution for Large Data Volumes! Should you store it in SF? And if so what steps need to take place for that LDV to not be problematic either because of storage, data skew, etc. Should you store it externally? If you store it externally, how could you see that data in SF (Salesforce Connect, Canvas App, Heroku Connect, etc).
64103

65-
4) Know how to identify multi-org scenarios and how to make multiple orgs work together if necessary. Normally multi-org scenarios are valid if SF limits would become an issue, if business processes and/or technology are significantly different (and can't be consolidated), data residency (country location of servers) is an issue due to compliance stipulations (GDPR or similar), or potentially if the scenario has an existing org that cannot easily be migrated in the timeframe the scenario gives you to produce a solution. If you need to merge multi-orgs together for people in both orgs to see data or for reporting data, look into CRM Analytics and/or Salesforce Connect.
104+
4) While I have never seen a scenario that requires a multi-org setup, it is still imperative to understand how to identify multi-org scenarios and how to make multiple orgs work together if necessary. Normally multi-org scenarios are valid if SF limits would become an issue, if business processes and/or technology are significantly different (and can't be consolidated), data residency (country location of servers) is an issue due to compliance stipulations (GDPR or similar), or potentially if the scenario has an existing org that cannot easily be migrated in the timeframe the scenario gives you to produce a solution. If you need to merge multiple orgs together for people in both orgs to see data or for reporting data, look into CRM Analytics and/or Salesforce Connect.
66105

67-
5) Know the high level use cases for every on platform cloud (CPQ, Field Service Lightning, Privacy and Consent, Billing, Salesforce Maps, etc) (you do not need to know B2B Commerce), it is unlikely that you will actually NEED to use them, however it is possible you will be asked to justify why you did not use them in the QA portion so you must know how they work and their use cases.
106+
5) Know the high level use cases for every on platform cloud (CPQ, Field Service Lightning, Privacy and Consent, Billing, Salesforce Maps, etc) (you do not need to know B2B Commerce, B2C Commerce, or Industry Clouds), it is unlikely that you will actually NEED to use them, however it is possible you will be asked to justify why you did not use them in the QA portion so you must know what they are, how they work, and their use cases.
68107

69-
6) Know the high level use cases for every off platform cloud (Marketing, Tableau, Heroku, Mulesoft), how their integrations with SF work and when you might use them. You do not need significant in depth knowledge of these systems, you only need to know what they're capable of and why people use them.
108+
6) Know the high level use cases for every off platform cloud (Marketing, Tableau, Mulesoft), how their integrations with SF work and when you might use them. You do not need significant in depth knowledge of these systems, you only need to know what they're capable of and why people use them.
70109

71-
7) Know how integrations work, what is an ETL, what is an ERP, what are the different OAuth, OIDC and SAML flows, what are the different integration patterns, what are firewalls, what are reverse proxies, what is an identity provider, what is LDAP, what is SCIM, what is JIT? You must know the answer to all of these things, how they work, and when and why to use them. You also need to know how to draw all OAuth, OIDC and SAML Flows from memory.
110+
7) Know how integrations work, what is an ETL, what is an ERP, what are the different OAuth, OIDC and SAML flows, what are the different integration patterns, what are firewalls, what are reverse proxies, what is an identity provider, what is LDAP, what is SCIM, what is JIT? You must know the answer to all of these things, how they work, and when and why to use them. You also need to know how all OAuth, OIDC and SAML Flows work from memory.
72111

73-
8) Know absolutely everything about the 6 major license types (Sales, Service, Platform, CC, CC+, and Partner) and know how licensing works for the other products (especially CRM Analytics and SF Connect).
112+
8) Know absolutely everything about the 6 major license types (Sales, Service, Platform, CC, CC+, and Partner) and know how licensing works for the other products (especially CRM Analytics, Service Cloud Voice, and Digital Engagement).
74113

75-
9) Know the major products 3rd party applications (appexchange products) in the following areas: Document Generation, eSignature, Payment Processing, Data Enrichment & Validation, eCommerce, Scheduling, Project Management, and CTI. You need to know how they work, when to use them, their major objects (aside from doc generation and esig), how licensing works, etc. I would pick one major app in every area and understand at a high level how they work and how they integrate with SF.
114+
9) Know the major 3rd party applications (appexchange products) in the following areas: Document Generation, eSignature, Payment Processing, Data Enrichment & Validation, eCommerce, Scheduling, Project Management, and CTI. You need to know at a very high level how they work, when to use them, and their major objects (aside from doc generation and esig). I would pick one major app in every area and understand at a high level how they work and how they integrate with SF.
76115

77116
10) Governance, ETL, Mobile and Environment strategies must be produced, however these are typically relatively simple if you understand everything above. These four areas can be whipped up quick and can be learned fast, but I would save your time studying these areas last as they are the simplest imo to deal with.
78117

79-
11) Your end solution needs to be simple and flexible! It should be so simple a junior admin could understand it and it needs to be as flexible as a rubber band, because the judges are going to likely slightly alter the scenario in QA to see how you and your solution can respond to it. Don't over complicate it, don't make it too fancy, if you're making it too fancy and too rigid you've done something wrong, try again.
118+
11) Your end solution needs to be simple and flexible! You are gonna be pretending to present to a CEO or CTO, these are often not ultra technical people, so you need to have a solution that easy to explain, and you need to be able to explain it in a simplistic way that the average person could understand. Do your best not to over complicate it, don't make it too fancy, if you're making it too fancy and too rigid you've done something wrong, try again.
80119

81-
12) The last thing is to just practice presenting and solving these scenarios at least once per week until your exam. It will take time to build up the stamina, confidence and knowledge to solve them, and you won't know where to improve if you aren't constantly solving them. Also get someone who will challenge you in QA because you need someone who will absolutely destroy you so you get practice either justifying or backtracking your scenario in QA.
120+
12) The last thing is to just practice presenting and solving these scenarios at least once every other week until your exam. It will take time to build up the stamina, confidence and knowledge to solve them, and you won't know where to improve if you aren't constantly solving them. Also get someone who will challenge you in QA because so you get practice either justifying or backtracking your scenario in QA. If you are serious about attempting this exam I would highly suggest doing a CTA study program, or finding a CTA who does hourly consultation that will do mock scenarios with you. It is worth it. Their feedback is often lightyears better than any other person you will ever study with.

docs/Notes-for-Improvement.md

Lines changed: 0 additions & 17 deletions
This file was deleted.

0 commit comments

Comments
 (0)