1.
ACLs - what are the different options?: View, Modify (includes delete, create, execute), Full Control (can give privs to others) Deny All (no privs at all), Default (inherit), Custom
2.
Alerts are based on....: Conditions
3.
Authentication Modes:: SWIL DaG: Standard, Windows, Integrated (Kerberos), LDAP, Database, Anon/Guest
4.
Change Journal Transactions: ....
5.
Compare and contrast Report Execution, Element Browsing and Object Browsing Execution flows in a 3 Tier Environment.: 1. RE: 9 possible steps, Caches, SQL Engine, Query Engine Analytical Engine, IServer Bus; if no cache, Bus obtains report def and app. objects from metadata, SQL Engine formulates SQL sends back to Bus --> Query Engine <-> DW -> Bus; can be multiple passes, back to Bus and Desktop.
2. EB: 7 Steps, Same as RE, but no Analytical Engine/Multipass
3. OB: 5 steps, Same as EB but no SQL Engine, Query Engine, DW.
6.
Cubes Vs. Caches: Cubes: Ad hoc Anal, Multiple Overlapping Reports, Highly prompted reports.
Caches: Very Frequent shared reports.
7.
Database Connections Monitor.....: Displays a list of database connections to BOTH the metadata and the DW. DB connection threads.
8.
Define a Database Instance: Represents a connection between a PROJECT and a specific Data Warehouse using ODBC DSN. Remember that a given Project Source can have many PROJECTs. A Database Instance utililizes a Database Connection (DSN and Login).
9.
Define a Server Definition: Represents a connection between the Intelligence Server and the Metadata using ODBC DSN.
10.
Define Project Source connectivity: In a 3-Tier environment, a TCP/IP connection between Desktop and the Intelligence Server. In a 2-Tier Environment, represents the connection between Desktop and the Metadata using an ODBC DSN
11.
Define Web Connectivity: Requires an Intelligence Server and by defintion is 4-Tier. The Web Browser connects to the Web Server via HTTP. The Web Server has MicroStrategy software installed on it and it connects to the IServer via TCP/IP
12.
Document Caches: Displays a list of Document Caches.
13.
Exam: Define the 3 Steps of the Cube Publication Process: 1. SQL generation and query execution.
2. Data Fetch using a memory buffer of 100mb
3. Data conversion and serialization - Analytic Engine.
Post Process State: Saved into IServer memory.
14.
Exam: Distribution Services and History Lists: Enables MicroStrategy WEB users to send reports and documents to: Only Distribution Services give you:
1. Email
2. File
3. Print.
Sign up for these one the Web.
Remember this is different than History List which is available on both Desktop and Web; History List contains messages that point to historical, archived content.
15.
Exam: Distribution Services and History Lists: Enables MicroStrategy WEB users to send reports and documents to:
1. Email
2. File
3. Print.
Sign up for these one the Web.
Remember this is different than History List which is available on both Desktop and Web; History List contains messages that point to historical, archived content.
16.
Exam: To use Cube Advisor, you must enable: Metric Levels Log. The Enterprise Manager file provides more detail but is optional
17.
Exam: What is Metadata Internationalization and what are the 2 ways you can approach it?: Manually go to every single item and tell it on a per object basis.
2. Or have a 3rd party do the work.
Nothing out-of-the-box. There is a wizard - RTW - Repository Translation Wizard. Remember this is not Interface Internationalization - MSTR handles that out-of-the-box.
18.
Exam: What is required to enable the History List Monitor?: Database-based Storage.
19.
Exam: What's the difference between Deactivating it and Deleting Cubes?: 1. Deactivation: Saves to hard disk and unloaded from memory to disable use until re-Activate-d.
2. Delete: Deletes from Memory and Hard Disk (the Cube must be completely re-run). Useful when the data is obsolete such as after an ETL run.
20.
Expect to see questions like:: 1. What is true about Enterprise Manager?
2. What is true about Integrity Manager?
3. What is true about Command Manager?
21.
For a cache to be used it must satisfy what criteria?: No changes, Same prompt answers, Allowed to use Cache, Cache not expired (administrator will set expiration policy - think ETL),
22.
From a standpoint of load balancing, what input is being considered to balance the load?: The number of sessions
23.
From a Working Set standpoint how do estimate the amount of memory required (3 factors) and what do you do if current memory is insufficient?: 1. Max # of intermediate states per user.
2. Average report size
3. Activity - includes concurrent users and users who are simply logged in.
If Working Set memory estimate exceeds current memory - increase the RAM on the IServer.
24.
Governors: 1. Server Level Governors apply to all jobs on the IServer - are across all projects.
2. Project Level Governors apply to project-specific jobs - across all users for the project.
25.
Governors PL: Jobs governors: Control the execution of jobs per user account, user session, and project. Note: this value cannot exceed the SL Max Jobs governor.
26.
Governors PL: Result Sets governors: Max seconds a job can take from submit --> Return.
27.
Governors PL: User Sessions: Limit the number of user sessions for the project and number of project sessions a single user can open at the same time. Note: Jobs submitted by MSTR Scheduler on behalf of the user don't count here.
28.
Governors SL: Describe Memory Request Idle Mode: Enabled by the Contract Manager when a memory request would cause IServer virtual memory or virtual address space to be depleted based on current utilization and contracts. If IServer determines that a new request would cause available virtual memory to be depleted, the request is denied. IServer remains in memory request idle mode until a request is made that would not result in a possible memory depletion situation. A value of -1 indicates the IServer does not shutdown if it goes into Memory Request Idle Mode.
29.
Governors SL: The ____ ____ governors clean up after users who forget to log out.: Idle Time
30.
Governors SL: The max user sessions governor will actually allow one more user than its value? Why?: To enable the Administrator to login.
31.
Governors SL: The Working Set Governor is used to support ____ _____.: Web Users. - Efficient use of Back Button (cached reports to display when user presses it), Manipulation in the Web, Support manually adding reports to HL.
32.
History List Management - 2 ways....: 1. Folder that stores messages that reflect report results data.
2. Created when you schedule reports and documents to run.
3. Because a cache already exists, no execution against DW happens.
4. May be stored in flat files or the database. Default - Flat File. With Version 9, the database is a new option.
33.
History List Messages: Displays a list of all History List Messages for all users. Only available if you use Database-based Storage.
34.
How do users sign up for schedules?: A subscription is created after you create the Schedule. The types are
1. History List.
2. Cache Update
3. Mobile.
4. Cube Refresh
5. Distribution Services - Delivering actual content to something/someone; literally sending something (as opposed to a message) to a file, email, print.
35.
How do we control access to what people can do (i.e., the functionality)?: 1. Object level Security (Access Control Lists - ACLs). Object Permissions: What folders and objects can the user/group access.
2. Privileges/Security Roles: What can the user/group do or perform (Admin, modify reports, execute only, etc.) If you don't have access to a project, you don't even know it's there.
36.
How do you optimize the number of database connections?: This is allocating threads to the DW. Too few threads, you get a backlog, in queue - too many you hit a point of diminishing returns. What to do? Throughput/Database Connections Graph: The Optimal Range of threads corresponds to the - "Zone of Maximum System Throughput".
37.
Idle User Sessions should be disconnect because:: A couple of things you can do.
1. Reduce memory intensive applications that are running on the IServer.
2. Shutdown processes, such as services and applications that are not being used and still get allocated memory by the OS.
38.
Intelligent Cube Caches Monitor: Displays a list of all ICubes in the metadata....
39.
Intelligent Cubes are different from Caches in what ways?: Different than caching in that Cubes are not report specific. Multiple reports can hit the same Cube. Report users AND reports.
40.
Internationalization - data level approaches: 1. Connection Mapping - 1 DW per language; handle via Connection Maps/Database Instances
2. SQL Generation (Column-based, Table-based, Row-based)
41.
Jobs Monitor - what does it do?: This monitor display a list of executing, queued and cancelled jobs. Reports
42.
Lesson 2: Object Manager: 1. Application Lifecycle Management - allows us to migrate objects across related projects (duplicated). Viewing object dependencies (child/parents), comparing objects across projects. Can work with 2 Tier and 3 Tier - no Web.
43.
Lesson 4: Command Manager: What can we do: Scripting interface - same things you can do in a GUI - any Configuration Objects: Trigger Events, Assign Privs, Create users. And Objects -
Argument/components: Token, Pipes, Brackets, Placeholders, Semicolon.
44.
Locking considerations (read/write): Pertain to Object Manager
45.
Memory Utilization stuff: A couple of things you can do.
1. Reduce memory intensive applications that are running on the IServer.
2. Shutdown processes, such as services and applications that are not being used and still get allocated memory by the OS.
46.
Name the 2 types of schedules: Time and Event Based.
47.
Name the 4 types of caches and the implications of each.: 1. Matching: Valid caches hit during report execution
2. History: Expired, Invalid/both, maintained because referenced by unread History List Messages.
3. Matching-History: Matching + at least 1 History List msg.
4. XML - report results and structure for use by Web.
48.
Object Manager is used to migrate a ___ ___ of objects from _____ to ____: small subset; DEV TEST. Searches for dependencies.
49.
Permissions - Name the 7 types of them... Introduces the notion of an ACL: CRUD WEB (Control, Read, Use, Delete, Write, Execute, Browse). ACL - Access Control List. Each Object and Folder in the system contains an ACL. You edit an object's ACL with properties.
50.
PL: Subscriptions: Limit the number of subscriptions per user by subscription type.
51.
Procedures - own JavaScript: Know that you can use Javascript in Command Manager/Procedures
52.
Project Merge is used.....: ....For mass migration of objects from TEST to PROD. Understand the differences between Project Merge and Object Manager: The key difference between Project Merge and Object Manager is that PM is designed to migrate entire projects. Uses the following criteria to migrate objects:
1. Objects that exist identically are not copied.
2. Objects that exist only in the source are copied.
3. Objects with conflict resolution will be copied or not, depending on the conflict resolution rules are pre-set in the wizard.
53.
Report Caches Monitor: Displays a list of report caches.
54.
T/F: Cube Advisor can only suggest what Cubes should possibly be considered, but cannot build them.: False. It can automatically create recommended cubes based on the Metric Levels Log input
55.
T/F: Distribution Services exist on Desktop: False - They exist on Web only.
56.
True/False: Caches can span projects as long as they are on the same IServer or IServer Cluster: False - project-specific.
57.
True/False: Clustered nodes can point to one and only one metadata at a time?: True
58.
Update Packages - describe what they are and how they work?: An Update Package is a file that contains object definitions and conflict resolution rules. Pre-do the Conflict Resolution stuff. Automatic. You import into the destination project. Many things from many folders. run it through a command line later on. Email it to somebody - don't have to be connected. Know the reasons for using an Update Package.
2 types of Packages:
1. Project Update package (Schema
2. Configuration Update Package - stuff under the Administrative Gear Icon.
59.
User Connections Monitor - what does it do?: Displays a list of users currently connected to the IServer.
60.
Users and Contacts: Contacts do not have a MSTR login. Can't do anything except be a passive receipient of content. As a user you can sign yourself up
61.
Web Server Tuning considerations: Heap Size and Garbage Collection Process (minimize its activity), web pool sizes.
62.
What 3 methods do we use to control access to data?: 1. Connection Mapping: Allows you to establish different DB logins against the same DSN to leverage DB security. Or you can use different DSNs to enable you to segregate users to different DBs in the same project.
2. Passthrough Execution: LINK a MSTR user to a DB username.
3. Security Filters: A filter applied to a user.
63.
What are the 3 different types of Command Manager interfaces?: Can do the same thing in all of these:
1. GUI
2. Command Line
3. CLE
64.
What are the 3 ways you can accomplish Single Sign On?: 1. Windows Authentication
2. Integrated Authentication (Kerberos)
3. Web Trusted SSO - Tivoli, SiteMinder - uses tokens
65.
What are the 4 benefits of Clustering?: 1. Performance.
2. Scalability.
3. Load Balancing.
4. Fail-over.
66.
What are the 4 different kinds of tests you can create using the Integrity Manager?: Project to Project. (Live project to live project).
Baseline to Baseline. (Archive to Archive).
Baseline to Live Project.
Simple Project - to create the Baseline in the first place.
67.
What are the caches and where do they reside?: 1. Element: Client Memory/Server Memory.
2. Object: C/S M
3. Report: Server Memory/Server Disk
4. Document S M/S D
68.
What are the components of the Enterprise Manager?: The Statistics Tables, the Fact Tables, the EM Metadata with all of the objects already created in it and the ETL process.
69.
What are the different ways to create users?: Desktop, Web or Command Manager, Import in from an outside source, or a UDF - user definition file.
70.
What are the possible outputs from Integrity Manager?: SQL, PDF, Excel, HTML, Data, Graph.
71.
What are the pre-requisites to use Cube Advisor?: 1. Version 9.0 or higher
2. Enable Dynamic Sourcing
3. Enable Metric Levels Log.
72.
What are the Statuses of a Cache? Page 378.: 1. Ready: Ready to be used
2. Processing: Currently being updated
3. Invalid: Invalid and will be deleted by Iserver
4. Expired: Expired and will be deleted
5. Loaded: In Memory
6. Updated: Up to Date Cache
7. Dirty - In Memory more current than Filed
8. Filed: Created on Disk
73.
What are the types of caches: Report caches, Element Caches, Browse Caches, Document Caches. Report and Document Caches (RAM and Disk - Server only). Object and Element Caches - RAM only - Server and Client.
74.
What are the types of reports you can run in Enterprise Manager?: Statistics, Number of users, Fact table usage, minutes running the report, etc. We'll know the bogus answer.
75.
What happens with prompted reports when Integrity Manager goes to run them?: Order Prompt Resolution - Required Prompts order:
1. Personal Answers
2. Default object answers
3. For user-defined - text, numeric or big decimal , date, number of elements for the hierarchy. You
4. Integrity Manager internal answer.
Optional Prompt - depends on if you checked the optional prompt checkbox.
76.
What is "Computational Distance"?: Time between original submission and final return/rendering of the data.
77.
What is change journaling?: Recording when you add, delete modify objects, touch a folder, even enable it. Remember the 2 levels - Server level (configuration object change journaling), Project level (schema and application object).
78.
What is dynamic sourcing?: Enables reports to automatically detect an ICube to satisfy reporting requirements. Project-wide can enable/disable Dynamic sourcing.
79.
What is Internationalization and what are the 5 types?: The process of adapting software to support different languages. Can occur in different places in MSTR.
1. Interface language: File Menu, messages from the system, Wizards, etc.
2. Metadata Language: Saved objects name (Folders, templates, reports, etc.).
3. Data Language: What language is the data coming back? The Attribute Elements....
4. Number and Date formatting.
5. Intelligence Server Language preferences.
80.
What is the Enterprise Manager?: It is a product that allows you to collect STATISTICS on the other MicroStrategy Projects.and then analyze those statistics in the MicroStrategy reporting environment running reports and documents against those raw statistics. The projects are the Source System, it has its own ETL, Schema Objects and Application Objects.
81.
What is the Integrity Manager Used For?: Check the integrity of your data before and after something has happened - upgrades, change to a schema, etc.
Another interesting usage: Pre-loading Cubes in a clustered environment.
82.
What kind of analysis can you do in the EM?: Anything about statistics: One question about EM - what kind of reports can you run - something about Statistics - it should be obvious.
83.
What kinds of things can you do with the Integrity Manager?: 1. Pre-Load Intelligent Cubes on Clustered IServer nodes.
2. Check the integrity of your data before and after something has happened - upgrades, change to a schema, etc.
3. What can you see to check out the integrity? SQL, PDF, Excel, HTML, Data, Graph. Set up order for prompt answering. Questions like - What is true about Integrity Manager?
84.
When thinking about failover support, when a project is on the failed machine and it is not on any of the other nodes, what happens?: project recovery.
85.
Where does the IServer look for Metadata connectivity Information?: In the Registry.
